Implementation and support engineers

Reference: Data Model and Storage Notes

High-level operational reference for key collections and upload path expectations.

Prerequisites

- Firestore and Storage access model familiarity

Step-by-step workflow

Core collections to know

- competitions, studios, dancers, routines, assignments, scores

- role/membership docs that grant scoped access

Storage path expectations

- Competition public site media under competition-scoped paths.

- Studio documents and waiver assets under studio-scoped paths.

- Metadata should store storagePath aligned with object location.

Deployment-sensitive checks

- Production project targeting must be explicit.

- Bucket config and service account project must match.

- CORS and rules must be published to production bucket.

Validation checklist

- Collection names used by ops docs match production schema.

- Upload smoke tests pass on all supported paths.

- Unauthorized upload attempts are denied as expected.

Common failure modes and fixes

Signed URL generation fails in production

- Verify service account IAM and bucket alignment with runtime config.

Upload preflight blocked

- Update bucket CORS to include exact production origins.