Prepare contest or agency metadata
Contest Metadata Prep and Bulk Metadata Injector are optional preparation tools. You need the current recipient's rules, local images, and accurate captions/rights information. A readiness score or profile does not mean a contest or agency accepted the photographs.
Use Contest Metadata Prep
- Enable/open the included Contest Metadata Prep workflow.
- Create/select the intended preparation project and load the candidate images.
- Review the relevant contest fields, captions, and readiness findings. Check the current entry rules outside the app before relying on any preset.
- Correct missing or questionable information and rerun the available checks.
- Inspect the final selected images and export through the offered preparation/delivery workflow.
- Open the output and confirm its metadata and names before submitting through the recipient's actual entry system.
Use Bulk Metadata Injector
- Enable Bulk Metadata Injector and open Metadata Prep.
- Add the intended selected or dropped images. Choose Getty Images, AP, Newhouse, College Media Wire, or Syracuse University Athletics as appropriate to the preparation task.
- Load/create the reusable contributor template and review the profile's defaults and validation requirements.
- Edit each image's caption and keyword set. Confirm copyright, location, credit, and facts; shared defaults can still be wrong for an individual photograph.
- Run validation, resolve issues, and apply the intended metadata through the injector.
- Reopen representative files in the normal metadata editor and inspect readback. The injector changes metadata, not image pixels, and does not itself upload the submission.
Saved data and boundaries
Preparation projects and templates retain reusable work through their existing stores. File injection reuses the core registered-file metadata writer. Organizer/judge prototypes are not the same product as entrant-side Contest Metadata Prep and are not ordinary enabled tools here.
Verify and troubleshoot
Try a disposable batch before a deadline, including files with pre-existing captions. Confirm that unrelated fields and pixels remain as expected. If writeback fails, check permissions/source availability and keep the draft. If a field passes locally but the recipient rejects it, use the recipient's current requirements and record the mismatch; do not repeatedly resubmit unchanged files. See Templates, Metadata, and Export.