Homeroom Photography · homeroom.photography
Team and action photography that knows who was in the frame
Athletics has its own rosters, its own seasons and its own publication habits, and it is the collection most likely to be handled by a volunteer. Holding an image against the activity roster means it carries a real participant list rather than a caption typed from memory in April.
Four collections, and they are not one problem
A posed team photograph, four hundred frames from a fixture, a cast list that changes between the dress rehearsal and the night, and the assembly nobody was formally covering. These fail differently, and a system that treats them as one bucket handles the easiest one well.
Team photographs
A posed team image is a participant list with faces on it
The formal team photograph is the one most likely to end up in a publication and the one most likely to be captioned from memory months later. Held against the activity roster for that season, it carries the participant list it was actually taken of, so the names under it are not a reconstruction.
Attached to the season roster at capture, not to a filename.
Action photography
Hundreds of frames, most of them of somebody
A single fixture produces more images than the rest of the year’s activities put together, and almost all of them contain identifiable students. This is the volume problem: a permission model that requires a per-image human decision does not survive contact with four hundred frames from a Tuesday.
Resolved against the participants on the roster for that fixture.
Performance and the arts
Cast lists that change between the dress and the night
A production has a cast, understudies, a crew and a pit, and the list is different on different nights. Treating a performance as its own activity with its own roster is what keeps “who is in this photograph” answerable when the answer differs between two images taken twelve hours apart.
Each performance is its own roster instance under the production.
Events and the ordinary day
Where a school’s photo library usually fragments
Assemblies, fundraisers, field days, the last week of term. Event imagery is where a library normally scatters into staff phones and a shared drive nobody audits, because no single person owns it. Held as a collection, an event carries the same per-student state as everything else, so the question of whether an image can be posted has an answer the system can give.
Held as a collection with per-student state, even where there is no formal roster.
Why activities are harder than picture day
Picture day is one operation against one roster on one day. Activities are the opposite: several participant lists are live at once for most of the year, they overlap, and their membership moves. A student joins in October, leaves in February, and appears in images taken in both months.
That is the whole difficulty, and it is a records problem rather than a photography one. An image attached to a season’s roster resolves against the membership as it was, which is why the chart below is about overlap rather than about fixtures.
The caption problem, which is really a records problem
Ask anyone who has produced a sport page: the photographs are the easy part. What consumes the time is establishing who is in them, and the usual method is somebody scrolling through images in May trying to remember a Tuesday in November.
An image held against the activity roster for that season already has the answer. Not because anything recognised a face — because the school wrote down who was on the team, and the image was attached to that list at the point it was filed rather than at the point it was needed.
The same fact does two jobs. It supplies the names for a publication, and it supplies the participant list that per-student permission resolves against. One is a convenience and the other is the reason this matters.
Counted from this page’s own lists
These bars are computed at render time from the same arrays that generate the chart and the panels above, so they cannot drift from the prose. They describe structure, not customers: there is no adoption figure and no outcome number anywhere on this site.
Questions an athletic department asks first
Who is meant to be using this -- a photographer or a school?
The school. This is the side of activities photography that is about the record: which activity, which season, which participants, and what may be done with the image afterwards. Who holds the camera is a separate question, and it is very often a parent or a member of staff rather than anybody professional.
Does an image have to be tagged student by student?
No, and a design that required it would not survive a single fixture. An image is attached to an activity and a session; the participants for that activity and season are already a list, and the per-student state resolves against that list. Individual attribution exists where it is useful, but it is not the thing holding the model up.
Is facial recognition used to work out who is in a photograph?
Not by default and not unless a parent opts in. The everyday association is to the activity roster -- the school's own participant list -- rather than to a face scan. The full mechanism, including what happens where a parent does opt in and the one part of it not yet proven end to end, is set out on homeroom.pics.
What about video of a game or a concert?
Out of scope for this site, deliberately. There is an unresolved question in the estate about what video capability may honestly be described, and rather than write a page across it, this site covers still photography and says so. That is a smaller claim than we could make and a more reliable one.
How the rosters themselves work is on activity rosters. The person most likely to be holding the camera is the subject of volunteers. What may actually be published is on what may be posted.