Asset Logs
Components of an Asset Log
An asset log is usually laid out as a table. Each row records one asset, such as an image, audio clip, video clip or piece of text, and each column holds one separate piece of information about it. The log records details about assets rather than storing the files themselves, so the team can identify, find and check everything the product uses.
Typical columns
| Component | What it records |
|---|---|
| Asset ID | A short reference such as AUD-03. It lets the team identify and refer to an asset easily, even if its filename changes. |
| Filename | The exact digital file name, such as opening_jingle.mp3, so the correct file can be located. |
| Description | What the asset is and what it shows or contains, not just a repeat of the filename or its format. |
| Source | Enough detail to trace the asset again, such as a website page, photographer, archive reference, publisher, collection name or commission reference. A vague note cannot be traced back. |
| Properties | Clear, measurable details: image width and height in pixels, resolution in ppi, file type, audio length or text word count. |
| Legal issues | Whether a licence must be bought, permission is needed, a model release form has been signed, and whether payment has been made. |
| Use | Where and how the asset appears in the finished product, such as the title screen or the closing credits. |
Worked example
Imagine you are making a school podcast about a local museum. One row has the asset ID AUD-02 and the filename museum_gallery.mp3. The description explains that it is an interview with the museum curator about the fossil gallery, rather than simply saying 'audio file'. The source gives the recording date, the interviewer and the museum, so anyone could trace it again. The properties record MP3 audio lasting 2 minutes 15 seconds. The legal issues show a signed permission form from the curator and no payment needed. The use column says the clip plays from 00:45 in episode 1.
Practise this
OCR Creative iMedia · Asset Logs