{"id":3151,"date":"2020-06-23T14:34:56","date_gmt":"2020-06-23T12:34:56","guid":{"rendered":"https:\/\/blog.archiware.com\/blog\/?p=3151"},"modified":"2022-04-25T17:57:40","modified_gmt":"2022-04-25T15:57:40","slug":"naming-conventions-for-files-in-media-production","status":"publish","type":"post","link":"https:\/\/blog.archiware.com\/blog\/de\/naming-conventions-for-files-in-media-production\/","title":{"rendered":"Dateinamensschema in der Medienproduktion"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

By Dr. Marc M. Batschkus<\/p>\n\n\n\n

The most robust metadata that you can have is the file name. It can travel through different operating systems and file systems. The file name is the only metadata that is available all the time. It is independent of any database, catalog, MAM system, application, or other mechanism that can keep or read metadata. This way, someone can instantly make sense of a file that gets isolated, left over, misplaced or transferred to another location.

Building a solid and intelligent naming convention for media files is crucial. Consistency is key for metadata. Metadata are a solid foundation for the workflow, searching and sharing files with other parties. The filename is the starting point.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Building a Filename<\/strong><\/h2>\n\n\n\n
<\/div>\n\n\n\n

Elements of a filename should be ordered according to importance. When the date is important in a workflow, it can be put first.<\/p>\n\n\n\n

All other elements should be ordered from the general to the specific:<\/strong><\/p>(date) (general category) (subcategory) (sub subcategory) (numbering) etc. <\/span><\/strong><\/cite><\/blockquote>\n\n\n\n

<\/div>\n\n\n\n

Special Characters<\/strong><\/h4>\n\n\n\n

Not all operating systems and file systems support the same characters. It is wise to avoid those that are not cross-platform compatible. <\/p>\n\n\n\n

This includes spaces (blanks) as well as \/ : * ? \u201c < > | [ ] & $<\/p>\n\n\n\n

Blanks will be replaced by some operating systems for \u201c%20\u201d thus files using blanks become hard to read.<\/p>\n\n\n\n

Blanks should be exchanged for \u201c_\u201d (underscore) and used to separate categories:<\/p>\n\n\n\n

20190623_production_title_customer.mov<\/strong><\/pre>\n\n\n\n
Any other fancy characters will also not be supported on some platforms and should be left out.<\/p>\n\n\n\n
Copyright \u00a9 and trademark TM also need to me avoided.<\/p>\n\n\n\n
Use the hyphen \u201c-\u201c to separate words within a category like here:\u200b<\/p>\n\n\n\n
20190623_production_title_mercedes-benz.mov<\/strong><\/pre>\n\n\n\n
Some operating system are case sensitive. To avoid any conflicts and unwanted sorting, use lower case letters only.<\/p>\n\n\n\n
If you want to use capitalising, there is an approach to this calling for \u201cregular\u201d use of upper and lower case letters. This improves readability of file names. Since consistency is key, if you choose this approach there should be clear rules what to capitalise.<\/p>\n\n\n\n
<\/div>\n\n\n\n
Numbers, dates and sorting<\/h4>\n\n\n\n
If dates are important for production, it makes sense to include them in the filename. For sorting to work as expected, this needs to be done in the most robust and technical savvy format. If the date is at the beginning of the file name, you want to be able to use it for sorting according to date. This means you need to use the YEAR-MONTH-DAY <\/strong>format with the year in four digits:<\/p>\n\n\n\n
2016-06-23<\/pre>\n\n\n\n
or<\/p>\n\n\n\n
20160623<\/pre>\n\n\n\n
for June 23, 2016.<\/p>\n\n\n\n
For the same reason, numbers should always be used with leading zeros to support proper sorting and easier readability. Additionally, this avoids duplicate numbers.<\/p>\n\n\n\n
Be generous with the number of digits for numbering, since this can not be re-done later. Six digits is probably a good choice for all, but the biggest production environments might need seven or even eight digits.<\/p>\n\n\n\n
20160623_000134.jpg<\/pre>\n\n\n\n
<\/div>\n\n\n\n
Unique Filenames<\/strong><\/h2>\n\n\n\n
<\/div>\n\n\n\n
Build unique filenames! Unique filenames have many advantages. Within the workflow, each file can be easily identified. Sent to third parties, they can not confuse them with other files from you that might have identical filenames (like 10.jpg). Synching with other systems, as well as importing or exporting might be only possible with unique filenames.<\/p>\n\n\n\n
Depending on the workflow, the date alone can make the filename unique. An additional time entry might be helpful if there are many files generated on the same day. This makes each filename unique. <\/p>\n\n\n\n
Use HHMMSS in a 24-hour format: \u200b
1320 for 1.20pm<\/p>\n\n\n\n
In multi-user environments, it might make sense to include the person creating the file in the filename like this: <\/p>\n\n\n\n
20190623_ebook_batschkusm_001.jpg<\/pre>\n\n\n\n
Extensions<\/h4>\n\n\n\n
For compatibility reasons, using extension with only three letters is best e.g:<\/p>\n\n\n\n