Menu
We are using SVN very successfully for source code in the traditional way: /branches, /trunk and /tags.
We do not use SVN for our art assets, which in a way are like source, but really don't have the same needs as source code.
I am referring to not only image files (jpeg, png, etc...) but also PhotoShop files and stock artwork that has been purchased (and shouldn't be lost).
What would be the best practice for file structure and procedure, for my graphic artists?
586
“For a museum condition report, typically the notebook travels with the exhibit, and the contents and condition are reported every time the crate is opened,” he reveals. That’s the ideal way to manage your art storage, so you can document any changes in the art or storage space over time.
There are a lot of risks when storing art. Although nerve-wracking, if you know what you’re doing, you can save monthly costs by putting together an at-home storage space. Even if you are working with consultants or a storage unit, it’s good to know what you’re looking for.
We spoke with the President of AXIS Fine Art Installation and art storage expert, Derek Smith. He told us the unfortunate story of a client who Saran-wrapped a painting for storage, inadvertently trapping humidity inside, and allowed mold to damage the painting. There are a lot of risks when storing art.
All of this documentation can be done online in the cloud with Artwork Archive. You can also update the location of your pieces to “Storage Facility,” to keep a record of the date they entered and their updated condition reports. A view of your artwork organized by location is available in your Artwork Archive account.
That's a good question actually. I'm wondering how other people are doing this.
What I usually do is keep track of main PSD files in the SVN repository in a separate folder. Let's say you have a /images containing all your images. In that case I usually set up an /images/source containing the latest PSD files.
It's a bit annoying on the first checkout, but PSD are not updated as often as source code so that's not too bad.
Of course you have to exclude these folders when you deploy your website.
Another way my company handle this is having all that on a network hard drive. We keep track of changes with a file structure like this:
/Project/Assets/Design/
/ Round 1
/ Round 2
/ Round n
The "Round" folder countain a version of the PSD files and the JPG exports associated to it. It is more efficient if you don't have too many rounds of changes, because if you have 100 revisions it's getting hard to manage correctly.
130
For our graphics we organize things into projects (like /graphics/marketing/NAILBA/2009/Banner represents our banner for the NAILBA {life insurance} conference this year). The folders /trunk and /branch are not mandatory, but they offer a clean way to explore ideas before selecting a single version. Since the HEAD is usually the only version that matters we don't use /tags. Now we don't create that much content (we program a suite of web apps, primarily) but this has worked well for our marketing projects (fliers, banners, websites etc).
20
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
