Metadata and Tagging Module: What Students Practise in the New Term
A look at how the Metadata and Tagging module runs this autumn: the fields students fill in, the sample clips they tag, and what a searchable library looks like by the final session.
Daniel Whitfield · · 6 minutes to read
Why the module is getting attention this autumn
Early autumn is when many production teams close out summer shoots and start looking at the pile of clips that arrived faster than anyone could describe them. That is the moment the Metadata and Tagging module was built for, and it has drawn more interest from our students in these weeks than at any point since the programme began in 2016.
The idea behind it is simple. A file name can tell you the date and the shoot, but it cannot tell you who is speaking, which location was used, whether the clip was approved or whether a release form exists. Metadata carries that information with the clip itself, so the answer travels wherever the file goes.
Students arrive with different habits. Some keep everything in a spreadsheet that only one person understands. Others rely on memory and a long scroll through a bin. The module replaces both with a short, agreed set of fields that anyone on the team can read and fill in the same way.
What students actually do in the sessions
The module is hands-on from the first session. Each student works with a sample project drive, a mixed set of camera clips, audio files and a few exported cuts, and the task is to make that material findable without opening every file.
We begin by looking at what the footage already contains: embedded camera data, timecode, frame rate and file dates. Students learn which of those details are worth keeping and which are noise. Then they decide what must be added by a person, because no camera records it.
Practice comes in short rounds. Tag twenty clips, then swap drives with a partner and try to find a specific shot using only the tags. When the partner cannot find it, the group looks at why, and the field list is adjusted. That loop teaches more than any lecture on the subject.
- Reading the metadata a camera already writes
- Adding fields a person must supply
- Swapping drives to test whether tags really work
Choosing fields that stay useful
The most common mistake we see is a field list that is far too long. Teams invent thirty fields, fill in five of them for a week, and then stop. A smaller set that gets filled in every time is worth far more than a thorough one that gets abandoned.
In the module we work toward a core list that fits a single screen: subject, location, people on screen, usage status, and a short free-text note. Students then add one or two fields that match their own kind of work, such as interview topic for documentary teams or product name for commercial crews.
We also spend time on vocabulary. If one editor writes interior and another writes indoors, a search will miss half the clips. Students draft a controlled list of terms, agree who may add to it, and write down how a new term gets approved.
- Keep the core list short enough to finish for every clip
- Add only fields your own work genuinely needs
- Use a controlled vocabulary with one owner
Tagging exports as well as raw footage
Raw clips get most of the attention, but final exports are where confusion costs the most. Months later, someone needs the approved version with captions burned in, and the folder holds five files with similar names.
We show students how to describe an export so that it answers the obvious questions without being opened: which cut it is, which platform or purpose it was made for, who approved it, and which source project produced it. Those few fields connect an export back to its origin.
This pairs naturally with the version tracking module taught by colleagues, but here the focus is narrower. The question is not how the revisions were numbered, only how a finished file describes itself once it leaves the edit suite and goes into storage.
Realistic outcomes for students
We are careful about what the module promises. By the end, a student should be able to define a field list for their own work, apply it consistently to a sample library, and write short instructions so a colleague can do the same without asking questions.
They will not leave with an automatic system that tags footage for them, and the module does not claim that metadata alone solves a disorganised drive. Tags work best on top of a sensible folder structure and clear naming, which other modules cover.
What students do take away is a working template, a tested vocabulary and the habit of tagging at ingest rather than months afterward. For most teams, that habit is the difference between a library they trust and one they avoid opening.
- A field list written for your own kind of shoots
- A tested vocabulary and approval routine
- A short guide a colleague can follow on their own
Prerequisites and who it suits
The module assumes you can open a project drive and move files around in your editing software or file browser. You do not need prior experience with metadata. A sample drive is provided for the exercises, and students are welcome to bring a small folder of their own material to practise on.
It suits editors, assistant editors, producers and production managers who handle footage at some stage and are tired of searching for it. Instructors with a media library background help with the more detailed questions about fields and vocabularies.
If you are unsure whether the module fits your team's level, the contact page is the best place to describe your situation, and we will say plainly whether it is the right starting point.
The Metadata and Tagging module is practical rather than theoretical: short field lists, tested vocabularies and exports that describe themselves. If your footage has outgrown memory and good intentions, this term is a sensible time to start. Describe your library through the contact page and we will tell you honestly what the module can and cannot do for your team.
Send us a message
- Call us
- (505) 214-0873
- By email
- [email protected]