3

As a graphic designer you're likely to amount a huge number of digital assets, whether they're mockup examples to show clients, icons, or assets used throughout a number of your projects.

How do you store these assets, I already have built up a number of components I often forget where I stored them or forget I even had them. Should I create a digital database of all my assets so I can search for? Should I just create a better folder structure on dropbox?

How do you manage a huge array of digital assets used for work?

  • This is a perfect question for Library Science. Ask a librarian. They specialize in exactly this issue. – Stan Apr 2 '18 at 15:39
5

I'll offer some strategies rather than specific apps to use:

Define which assets will be re-used

Files that are only used for a particular project can/should be stored separately from files that will get re-used frequently. For us, we only access project-based files occasionally, so the ability to tag and browse them isn't vital, but security is.

Conversely, assets that get reused - mostly fonts and stock photography - benefit from being within a system that allows fast and easy browsing with support for tags and metadata. As Lauren points out, Bridge is well suited for this, and can be set up to access networked media.

Have a sensible filing structure

Every project should have a unique number; in all my years working for various studios and print shops, it's the only sane method. This really pays off when you work on a project which is a re-visiting of a previous one: catalogues, newsletters, event-related materials etc.

We keep our file system as narrow as possible; this means keeping the levels of hierarchy as low as we can, usually only a few levels deep:

- Projects
    - 0001 Client Name: Project Name
        - Supplied
        - WIP
        - Admin
        - Final
        - Proofs
            - 2016.05.26
            - 2016.05.27
    - 0002 Client Name: Project Name
    - 0003 Client Name: Project Name
- Assets

We keep it to 4 levels deep, and each project gets the same 5x folders each time. Supplied content and proofs always go in dated folders, as they always multiple quickly, and filing them by date is the easiest way to keep tabs on thing and refer to them in correspondance. I've seen some studios use separate folders for each client, but I've never found a need myself.

Let the computer do the heavy lifting

Computers are great at performing simple searches really fast, so take advantage of that. Keeping our file system as narrow and predictable as possible makes searching for something really easy, even with thousands of jobs. We also keep a simple text file that lists the project numbers, client and project name; we can search this in under a second, get the relevant project numbers and retrieve the files in a minute or less, even jobs that are 6 years old. I've known some studio managers with really arcane filing systems that rely on them actually remembering where files are located; which is just bananas.

Pick your storage media wisely

Hard drives are the most sensible choice here; they're now cheap and fast enough. Tape-based media seems to still be used in larger/older studios, so they still get some weird kudos for being the 'professional' choice, but really they are as slow as sin. Don't be tempted to use DVD-Rs; I've seen it done and that way lies madness. Avoid splitting content across multiple drives; it may seem the cheaper option, but it introduces complexity and reduces search-ability.

Everything breaks eventually

Backup frequently. Backup your backups. Keep backups separate, preferably offsite. Don't rely just on cloud services; you don't control them and they can also break. Make sure you can actually access the data on your backups.

There's never a final version

Final.pdf. Finalv2.pdf. FINALfinalv2.pdf. HonestlyThatsTheLastChangeFINAL.pdf. Use a date, or a version number. Even version 1 should get a version number. We only move files into the finals folder on our projects once the job is complete, paid for and ready for archiving.

Be the hero no-one expected

Ensure that your contract specifies that you are not liable for the long term storage of assets for the client. However, if a client does request something that's 4 years old, you can of course pull their fat out of the fire with your superior skills. And bill them.

1

Sounds like a perfect case for Adobe Bridge.

How Should Adobe Bridge Be Used?

The entire point of Bridge is to create an easily searchable, tagable database of all your assets.

Additionally, you should make sure you have a file storage system which is easy to understand and well organized. Whether that's by client, by date, or some other method is up to you, but if someone asks you for "that postcard for SmithCo we did in March 2014, the one with the house on it," you should be able to drill down manually into your files and locate it in a minute or two, or at least have a good idea of where it might be.

-1

Good question indeed. We ran into the problem of storing all the design assets a few years ago.
There are a lot of stuff to store besides the design files(PSD/AI/Sketch/etc). We figured out that to keep the design library consistent we need to hold a lot of different things like:
- versioned designs;
- briefs for the designs;
- stock photos;
- product photos;
- different versions of the same design, i.g. the same banner for AdWords in different sizes;
- videos that eats a lot of space;
- history of discussions, i.e. who changed what and why;
- references to all the external materials;
- structure of the assets;
- metadata, like keywords, expiration dates, etc.
As well we figured out that we need to keep all the team updated about the changes in the library. Mainly because programmers tend to implement outdated designs or pick old photos for landings all the time and that's takes a lot of effort to track that they use right things in right places. Actually that is nothing new, just regular assets management and changes management. A lot of industries are using this approach.

Initially we've tried to put everything into GitHub that we're using for code. That was kind of disaster, we almost lost all our designers. They never got to use that, instead we got everyday complains about complexity, usability and all that stuff. Then we took Google Drive and put all the our stuff there and shared to the team. In a few weeks it became total mess because this is the same like share a folder into office network. No rules, total anarchy that one can't beat.

We ended up with our own digital asset management solution built on top of Google Drive. That allows us to manage all the library consistent, search through that, send updates to the team, keep/track versions, add comments/marks/ratings etc. That works for us and a number of our users on scale.

-2

You shouldn't store them if you always have internet connection. I'm usually removing them after usage. If I need to re use them, I just store related file(s). In internet millions of mockups there and they always updating. So you don't need to store.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.