A useful file name helps a person recognize an asset, but it should not be the asset’s only identity. Automation needs a stable ID that survives renames, campaign changes, and new derivatives. Treat the file name as a readable label and the ID as the durable reference.
What belongs in a file name?
Use a short pattern that people can apply consistently: project, subject, purpose, and version if version is not already managed elsewhere. Avoid spaces or punctuation that creates trouble in URLs and scripts. Do not encode approval, license, or locale solely in the name; those facts can change and deserve explicit metadata fields.
Separate source and derivative names
Keep the source ID in every derivative record. A web crop might add a transformation label such as hero-16x9, while the original retains its own immutable record. If the rendering service changes, you can regenerate derivatives without changing the editorial reference to the source.
Make collisions predictable
Two files can arrive with the same human-readable name. Do not silently overwrite either. Assign distinct IDs at intake, record a checksum where appropriate, and flag likely duplicates for review. A collision policy is especially important when several teams upload to a shared library.
Test the convention
Try the pattern on assets with long titles, multiple locales, revised creative, and several aspect ratios. Ask a designer and a developer to find the approved source without opening every file. If the name grows into a sentence or becomes an encoded database, simplify it and move the detail into structured fields.
A concrete example
A file called spring-launch-final2.jpg is reused for a summer page. The campaign label becomes misleading, while old links still need to work. Give the source a permanent asset ID, retain a readable title in metadata, and name derivatives by placement. The publication record then points to the ID and approved version.
Related reading
- Media Workflow Automation: A Practical Starting Guide
- How to Audit a Media Workflow Before Automating It
- Design a Media Metadata Schema Teams Will Actually Use
Primary reference
The W3C data identifier guidance provides the underlying technical reference for this workflow.
Related field note
Continue with How to document asset naming automation for the next operator.