Naming Standards
In this document you will find all necessary information regarding the folder structure and naming convention for our projects.
Please read all information at least twice and follow the instructions carefully.
If there are any questions concerning the documentation please contact Paul Dreisen or Stephan Krause for further information.
Overview
[edit]All projects are stored on our centralized network fileshare found under
\\pslsrv10\pslsrv10
(typically mapped to drive X:\ on windows machines)
All projects have their own subfolder in the 'Projects' folder.
Since every machine has writing rights, please pay extra attention so
you don't accidently delete/move the wrong files or even whole projects.
The initial name for a project is created inside the Agentursoftware.
Usually this is done by one of our inhouse producers.
After a project is created a simple script will automatically create the folder structure on the server.
Project Naming
[edit]Our projects names contain the following information:
Customer, year, department, projectnumber, project title
Since this information is too long to be packed into a single folder name, it is shortened.
Consider the following example:
Customer: Parasol Island
Year: 2013
Department: Animation
ProjectNumber: 5
Project Title: Demo Project
This translates to the project name:
PSL13_ANM05_Demo_Project
Project Code
[edit]The project code is a special identifier, which uniquely identifies the project amongst all others. It consists of the customer, year, department and projectnumber. (See Project Naming)
For the above example:
PS13A05
File Naming
[edit]All file names generated during production are prefixed with the project code!
The idea behind this is pretty simple: If a file is accidently moved to another location it can quickly be identified and searched.
Here are some guidelines for naming our files properly.
- All filenames start with the project code.
- All filenames end with the initials of the creator. For example: Leo Quensel -> lQ. First letter is lowercase, second letter uppercase.
- All information for naming a file in the right way can be found within the project folder name.
- There is NO 'Final' file. All versions are incremented one-by-one: v001, v002, v003... - This prevents stuff like 'Final', 'Final2', 'Final2_New', etc...
- Pick a filename and stick to it when you create higher versions of it.
(The next version of 'PS13A05_Bottles_B_FrontLabel_v003_lQ.png' is 'PS13A05_Bottles_B_FrontLabel_v004_lQ.png' and nothing else) - Every filename has to make sense (No 'new_funk_big1.png' please).
- Every filename has to relate to the project it belongs to. It is not enough for the file to be in the right folder since they can accidently be moved. (This is what the project code is for)
- File naming for version files of Maya/Fusion/XSI/AfterEffects is taken care of by Zombie Resurrection, our inhouse pipeline tool
An example of a properly named file:
PS13A05_Bottles_B_FrontLabel_v003_lQ.png
Folder Structure
[edit]The Structure is mangaed by PRISM.
00 -> 04 is Managed b Prism
05 ->10 is Custom
There are a number of default subfolders inside each project:
| Folder | Description |
|---|---|
| 00_Pipeline | Contains mostly config files and presets related to the Pipeline |
| 01_Management | Pipeline related |
| 02_Designs | Pipeline related for WiP |
| 03_Production | all Asset and Shot Files, Projectfiles and RenderOutput |
| 04_Resources | Pipeline related Libraries |
| 05_Incoming | Contains footage and working material from external sources. This is not a working folder. If you need to modify data please copy it to the appropriate location first |
| 06_Edits | Workspace for all Edits not Tracked by PRISM |
| 07_Online | Contains all data from our online systems like Smoke, Flame or Davinci |
| 09_toClient | This is the 'out' folder which contains files sent (or to be sent) to the client. This folder contains a default subfolder named [ProjectCode]_Datum_Inhalt which you can
use as a template for new subfolders. Please name folders inside here the following way:
|
| 10_final_completion_to_archive | Contails files which may still be needed after finishing the project. This folder is usually created when the project is finished |