File Naming Conventions Recommended Practice Collection ID Express the Collection ID in such a way that it reflects the original collection name used by the organization, keeping brevity and disambiguity in mind. E.g.: · Lombard Postcard Collection = LCC or LomPC or LomPost File Creation Date Including the file creation date in its name is useful for identifying file versions and invaluable during implementation of storage renewal practices. For multipart objects, use the first date of creation throughout the object (i.e. for every page, even if they are digitized on different dates). This is particularly important when uploading multipart objects to VITA when file name stripping requires consistent file name components. Be consistent in the dating convention used in the organization for easy sorting and finding, e.g. a file created on January 3, 2010 could be identified as: · 20100103 · 2010-01-03 Remember: do not use slashes! File Number Identify an approximate number for each collection at the beginning of the project or program in order to ensure the file name convention is expansible enough to accommodate the whole collection once it is digitized. E.g. If the Lombard postcard collection contains approximately1000 objects, allow at least 5 zeros for the file name Putting it all together: Example 1. The Hazelwood Community Museum & Archives is digitizing 40 of its collections. The collections tend to contain anywhere from 50-600 objects each. The date of the first digital file is January 3rd, 2010 and is an object from the Lombard Postcard Collection. The archival copy (master) is saved in TIFF format. The first file name is: LomPost_2010-01-03_0001.tif Example 2. Two Museums, the Hazelwood and the Halliday, are digitizing their collections in a collaborative project. The digital files will be stored separately but displayed Jess Posgate NamingConventions v.4 June 2012