All events
Each card shows the upload code, photo counts by photographer, and index coverage stats.
Event Report
Overview of every event — photographers, photo counts, and physical storage used by uploaded images.
| Event | Date | Status | Assigned photographers | Photos | Storage | Face indexed | Bib tagged |
|---|
Site analytics
Page views, searches, and photo downloads. Counts start from when this feature is deployed.
Traffic
Downloads & searches
Top downloaded photos
Select an event above to see per-photo download counts.
| Photo | Filename | Photographer | Downloads |
|---|
Add photographer
Maintain photographer master data used for event assignment and upload attribution.
Add registered user
Create accounts, maintain user profiles, control access, and reset passwords.
Registered users
Search by username, name, email, phone, location, or account status.
Create event
A unique 8-digit event code is generated automatically for photographer uploads.
Upload event photos
Select a folder to upload all images inside it. Photos are stored immediately; bib and face indexing runs later in Maintenance (unless INDEX_ON_UPLOAD=true).
Delete photos by photographer
Remove all photos uploaded by a specific photographer — or by Admin — from the selected event.
Delete selected photos
Select one or more photos for an event and permanently delete them from Cosmos and Blob Storage (original, thumbnail, index image, and face index links).
Event maintenance
With the async pipeline, maintenance buttons enqueue work to the indexing worker (scale-to-zero queue) — they do not run OCR/face on the API itself. Use them for backfill, retries, and full rebuilds. New uploads already enqueue automatically.
Full regenerate (rebuild everything)
Repair only — photos missing face/bib tags
User photo Automatch
Persist My Photos matches from each user’s saved selfie against existing event face indexes. Does not re-index event photos. For large full face/bib rebuilds, prefer Admin Desktop.
Uses Settings → Number of Days to generate Automatch. Selects recent face-indexed events and users who have not had Automatch yet.
Data backfill
One-time / repair jobs across all events. Safe to re-run; use after upgrades or if report/search data looks incomplete.
App settings
Runtime switches for the whole site. Changes apply immediately (no redeploy). Mail provider secrets stay in Azure; this only turns product features on or off.
When on, newly assigned photographers get an email with the event code and upload links. Requires outbound mail to be configured on the server.
When off (recommended for large events), upload stays fast and you index later from Maintenance or the desktop admin tool.
Used by Admin web and Desktop New User Automatch for all Events: include events created on or after (today minus this many days), and match users who have not had Automatch run yet.
Used by the indexing queue worker and Maintenance bib jobs. Azure Vision is recommended for large events; EasyOCR avoids per-photo Vision API charges.
Applies to the public portal and Admin pages for everyone. Save, then refresh other open tabs to pick up the new look.
Status
Read-only values from the current deployment (change via Azure / deploy scripts).
- Outbound mail configured
- —
- Public site URL
- —
- Prefer Blob SAS for downloads
- —
- Last saved
- —