What file metadata is for
File metadata describes the uploaded file rather than the catalogue record. It helps users identify file type, size, dimensions, technical properties and, for time-based media, event or segment information.
- Use item details and descriptions for catalogue meaning.
- Use file metadata for technical review and troubleshooting.
- Use embedded metadata carefully: it can speed up cataloguing, but imported values may need mapping, priority rules and human review.
- Use audio/video event data only where the local workflow supports time-based media annotation.
- Use preservation or maintenance actions according to local policy.
- File Metadata and Audio/Video Events appear as item-page tabs or panels where available.
- Full File Metadata appears in the item action area for detailed technical metadata.
- Result-list maintenance actions include Extract Asset Metadata and Check Integrity where permissions and context allow them.
Review file metadata
The item page can show file name, file type, category, extension, size, dimensions, orientation, capture date, capture device and colour space. These values describe the uploaded file rather than the catalogue record.
- Open the item page.
- Open the File Metadata tab or area.
- Review the visible technical values.
- Compare the values with the expected file where an upload, conversion or delivery issue is being investigated.
- Escalate unexpected file values before changing descriptive metadata to compensate for a technical issue.
Use full file metadata
Full File Metadata opens a detailed File Metadata view. In the reviewed Sprint item, this view included General and EXIF sections, with values such as width, height, extension, file type, colour space, orientation, category, file size and capture date.
- Use it when the summary file metadata is not enough.
- Look for embedded date, camera, dimension, colour or format information where relevant.
- Do not assume every embedded value is authoritative; files can contain missing, stale or misleading technical metadata.
- When duplicate detection or integrity checks are enabled, use file metadata alongside digest/check results rather than as the only evidence.
- Keep catalogue fields clear and human-readable even when technical metadata is complex.
Review audio/video events
Audio/Video Events opens a dedicated event view where an iBase system is configured for AV workflows. Event fields and editing permissions can vary, and some item types may show the action without useful event data.
- Open the item for the audio or video asset.
- Open Audio/Video Events where available.
- Review event labels, timings and descriptions if events are present.
- Check that event timings match the media and local editorial rules.
- Save or cancel according to the controls shown by your site.
Use extraction and integrity actions carefully
Some result lists or selected sets expose maintenance actions that work with technical metadata and files. Sprint result-list actions include Extract Asset Metadata and Check Integrity.
- Use Extract Asset Metadata when metadata extraction is available and appropriate for the selected assets.
- Use Check Integrity when a preservation or file-health check is needed.
- Review the selected item count before running technical actions on a group.
- Ask a System Manager before using maintenance actions on a large or sensitive set.
