Let's say you use Blender, Photoshop and Premiere Pro/Davinci and you are making a music video with a little dinosaur.
Where is what kind of file located?
Are the references in the Project Folder inside the Blender Folder or do you use a seperate Reference&Asset Folder?
Blender->Projects->Music Video->References->Dinosaurs
or
Blender->References->Music Video
Blender->References->Dinosaurs
Music Video->References->Dinosaurs
References->Dinosaurs (general folder without a specific link for a project)
Do you keep the final video in the Premiere Pro Project Folder? Do you use an Export Folder inside Premiere Pro Folder or do you put it in the project folder inside the blender folder? or do you have a project folder and inside that folder is a folder for blender, premiere pro and so on?
Premiere Pro->Projects->Music Video
Premiere Pro->Projects->Music Video->Export
Blender->Projects->Music Video->Export
Music Video->Export
Music Video->Premiere Pro->Export
Export is where the fin.mov or fin_final_superfinal_finished_nr156.mov comes into.
Where is the music for the video located?
I know it's a horrible topic but maybe a few of you are interested to share some ideas.
Replies
The basic overriding principle behind organising your shit is to ask yourself whether somebody who's not worked on the project can come along and find the files required to easily recreate the final result after you've quit/been eaten by a horse (it happens, I swear)
IME, I find it best to do as little custom organization as possible. Instead, try to make use of windows built-in organization tools as much as possible.
Reason is because the more nested directories you got - it just translates to wasted time searching and more RSI-inducing hunting and pecking. When it comes to finding things it is easiest just to filter by type and use a naming convention so that like items group together in a text search.
Using the tools like that, you need much fewer directories in total, and more of your work is done with keyboard. Also it is much more efficient to search with text versus your eyes looking for icons or reading list.
Big caveat is that I work mostly alone. However, I still try to organize like its a team. Because when I do some programming for a few days and then have to switch gears to some art stuff, pretty much I forget where things are.
Since I am working in unreal currently, I just follow their guidelines. Example: Assets naming convention - Gamedev Guide (ikrima.dev)
One thing I see people do that I think is a genuinely bad practice: putting the different assets that compose an single cohesive asset into different directories. Like you got a character model, but its textures are all inside a texture directory, it's model file and materials all in separate directories... That becomes a nightmare really fast. I like to put like items with like items, and let the sort/filter tools + naming convention do the work.
one final note, project management is just like anything else i suppose - its fluid, changing process. you go in knowing a few things, and you learn more along the way. so take time occasionally to revaluate and reorganize based on what you've learned, and what you predict to happen in future. dont shoehorn yourself with arbitrary restrictions, keep your work style fast and loose, make a mess and then once you see a clear path forward, then go back and clean up, set yourself up to get the next 100 yards or however far you can see to the next big obstacle.
They're mostly focused around trawling repositories with scripts or auditing content so probably not a concern for small scale working but when you're looking at hundreds of thousands of files the ability to filter by folder name becomes quite valuable.
The file names are based on the project. Since I am not doing a huge production with many people (Just myself), I would say dino is my main name and use that as a base. dino_sculp.ztl, dino_music_vid.prj. This way no need to have apps with their own folders all over the place and trying to gather them when it's time to archive. Just grab the entire project and back it up.
It's not perfect but it makes tracking source data down fairly intuitive and that's vital when you have hundreds of people potentially needing to find it.
@gnoop
We have over 50,000 files in our substance libraries and our worst organisational problem is cross project dependencies.
You just have to stick to a system and its perfectly manageable.