Editing File Naming Conventions (section)

===Creative Layout Files===
When developing creative files, designers will name files
using the rules below without a presentation date. Dates
are only attached to client presentation files.

====Tracking Code====
Concepts are separated into individual files with a
numerical concept code (e.g. c1, c2, c3) and appended with an alphabetical version (c1a, c1b, c1c, etc). Each concept file should be
a single concept (that may have multiple pages) and not multiple concepts in a single file.

Each time a change is made to a project, the name is iterated forward and the old version moved to Old Layouts. 

For internal changes, the tracking code advances alphabetically.

For example '''c1a'''-XXXXX-v1 becomes '''c1b'''-XXXXX-v1

For client changes, the version number advances numerically and the tracking code resets to a

For example '''c1k'''-XXXXX-'''v1''' becomes '''c1a'''-XXXXX-'''v2'''

For any change to a file after it has been reviewed internally or by the client, you will always save a new version. It is each designer's responsibility to retire older versions to the Old Layouts folder so that the creative folder has only the most recent files.

Multiple concepts are combined in to project files, either as an Indesign file that places individual concepts, or as combined PDFs. Presentation files use a tracking code that starts with p1, p2, p3 and the same alphabetical versioning as concept files.

For example '''p1a'''-XXXXX-v1 could be an Indesign shell that displays all concepts and helpful descriptions or it could be created simply by combining all concept PDFs into a single PDF.

The preferred method for sharing new concepts is to create an Indesign presentation template, a sample of which can be found on the server in /creative/MEG/PRESENTATION TEMPLATES  

Template jobs that don’t require internal creative review can forego this tracking code.

====Job Title====
Usually, this matches the name provided in Project Seeker, but can include an optional description at end to differentiate multiple components of a project. Always put these descriptors at the end.

For example: c1a-XXXXX-v1 Seno Web Updates '''- Landing Page'''