Photo batches
A batch is one camera deployment. Upload the photos straight off the card — they are checksummed on the way into the project archive — then run the AI pre-pass and assign it to reviewers.
Results & export
Every saved identification, joined to its photo metadata and the model's own guess.
Export options
One row per identification. Leave everything as it is for the full record; narrow it when the file is going to someone who only needs part of it.
for_sharing, so the file stays identifiable later. The terms of use
require this, so the tick is here rather than left to memory.Storage
Where the photos actually live, how much room they take, and whether the archive is reachable.
The archive
Every uploaded photo is written to the project's own object storage under a name that records the organization, site, and the moment the camera fired. This is the copy that outlives the project: it does not depend on anyone's Dropbox folder staying where it is, and the checksum stored beside each photo is what proves the file has not changed since the card came out of the field.
By organization
What each participating group has contributed. This is the figure to use when the running cost of the archive is being shared out.
Server disk
Full-size originals are kept on the server only while a batch is being worked on. Once a photo has been identified, or the AI pass called it blank, the original is removed from the disk and fetched back from the archive whenever something needs it. A permanent review copy stays behind, so every photo can still be looked at and re-identified. No batch is pruned until the portal has fetched one of its photos back and confirmed it matched.
Reviewers
Each participating organization gets named accounts so every identification is attributable.
Organizations
Every account, site and batch is walled by an exact organization name, so the names live here rather than being typed each time. Renaming one is also how two spellings of the same partner are merged: the new name is written through every account, site, batch and sharing list at once.
| Organization | Accounts | Batches | Sites |
|---|
Add a reviewer
Camera-trap sites
The site code is the join key across every batch, filename and export, so it is registered once here and offered as a dropdown at import. Assign each site to the organization that runs it; reviewers see only their own. Codes cannot be edited after photos reference them — retire the site and register a new code instead.
Describe the array. All of it is required — tick Unknown for anything that was never measured.
| Code | Site name | Organization | Location | Set up | Shape & alignment | Cams | Fence | Batches |
|---|
Accounts
Role, organization and sign-in address can be changed in place. Deactivating an account signs it out everywhere and blocks sign-in, while keeping every identification already attributed to it.
| Name | Organization | Role | IDs saved | Last seen | Terms |
|---|