Editing
File Naming Conventions
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Job Folders== Use the Job Folder template to create a new job by copying it to your desktop, renaming renaming to: XXXXX JobName and then copying to the appropriate client folder. No underscores are required. Within each folder, we are using the folders shown at below: ===CREATIVE=== Put layout files loose in this folder using the naming convention outlined below. As the job evolves to a more finalized set of concepts or production files, move the older layout files into Old Layouts. Artwork should be organized in folders that match the concept file, so all art for concept 1 will go into a c1 folder. Feel free to use your own subfolders to separate rights managed or specific photo houses. ===PLANNING=== Will contain the creative brief and any client supplied copy or background. Logos and images used in creative should not be stored here, but moved to either Brand Guidelines, Photos - Logos, or the Art folders. ===PRESENTATION=== Presentation files should be saved into folders named for the date they are made using the MMDDYY format. Files need not be renamed for internal review, but should follow the instructions outlined below for client presentation. ===PRODUCTION=== The Build folder will contain the working files for any job approved by client. Designers will move or package files to this folder when we start finalizing files for release and retire older layouts from Creative to the Old Layout folder. Final folder is for files released to the client or vendor (including build files, links, etc). If only PDF is released, keep build files in the Build folder. Per our QA process, a designer will complete their first round of QA and start a new QA PDF. Upon completion, they will save the QA PDF and let the team know by timestamp that production files are ready for review. The designer will not move files to Final unless asked, but leave build files in Build in case there are changes following the second proof. The proofer will check all items indicated in the QA document, and if passed, move the release files to Final as well as create Client Share links, when necessary. If only a PDF file is being released, no files are moved from Build except the release PDF. If all packaged files are being released, the entire contents of the Build folder will be moved to Final. When creating Client share links on Box, the contents of Final are uploaded to a shared folder without compressing to zip, unless asked.
Summary:
Please note that all contributions to MEG Client Production Guide may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Medge Guide:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
View history
More
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information