Designing a custom taxonomy for your digital asset library (or DAM) system is one of the biggest milestones when implementing and launching a DAM initiative in your organization. In most implementations, this is a major time investment and crucial for optimized DAM findability.
Taxonomy is the scheme of classification used to categorize and organize digital assets. It is the data structure on which a DAM must be built to make assets findable through searching and filtering. Therefore, taxonomy design is the first priority in the implementation of a DAM system.
Taxonomy consists of descriptive terms used to label assets to make them findable. These descriptive terms constitute a controlled vocabulary, or consistent naming system used to tag, index, and retrieve assets.
The controlled vocabulary of a taxonomy as well as description, date, and usage information, are considered metadata—defined as data used to describe other data.
|Flat Taxonomy||Nested Taxonomy|
|+ Used in some DAMs and Google image search||+ Used in e-Commerce platforms, folder structures, and legacy DAMs|
|+ Does not require prior knowledge of the pathway to a file for a quick find||+ Structure is familiar to end-users|
|+ Search experience is productive even without prior knowledge||- Requires prior knowledge of the pathway to a file for a quick find|
|+ Browsability is enhanced because all categories are visible||- Search experience is unproductive without prior knowledge|
|- Structure is unfamiliar to end-users||- Browsability is limited because folders are hidden within others|
1. How do users currently search for assets in your current organizational system? (i.e. Click through folders on shared drive, “I ask the designer to email assets to me.”)
2. What are the pain-points your organization experiences when searching in your current organizational system? How would users in the organization like to find assets?
3. What high-level categories of information would be useful for your organization to search or filter on? (i.e. department, product, project, region, season)
4. Does your organization use a file naming convention? If so, what does it signify?
5. What types of assets will be stored in the DAM?
a. Please describe the content of the assets, when applicable. (i.e. Contains product shot, brand guidelines for the marketing team, historical/inactive)
b. Please describe how users will use the assets, when applicable. (i.e. On social media, in a marketing campaign, to share with others in the organization)
1. List the high-level categories (fields) you listed in response to questions three and five. If applicable, add the categories required by your organization’s file naming convention to this list.
2. Organize these fields in a spreadsheet tool such as Microsoft Excel or Google Sheets, or mapping tool such as XMind.
3. Use the data structure you created in step two to configure your DAM system and tag your assets during import.
Examples of taxonomy approaches and exercises that you can use to start planning your digital asset management taxonomy today. Have questions or need some eyes on something? We want to chat! Message us on Slack now!
For further information…
Check out a taxonomy in action in the Open Assetbank Fruit Portal.
Already have your taxonomy ready to go? Read 3 Steps to DAM Migration.
Or are you ready to compare vendors? Fill in the form below to get the DAM Comparison Guide!