Effective taxonomy is the backbone of your Bynder DAM. In the bustling digital landscape, where the volume of assets can grow exponentially, a robust taxonomy ensures that every file is easily accessible and manageable. Bynder's taxonomy capabilities empower users to categorize, tag, and retrieve assets swiftly. By following these tips and asking the right questions, you can develop a robust and efficient taxonomy, making it easier for your users to navigate digital assets.
Helpful Resources
Take a look at our Taxonomy Webinar, which provides a detailed review of Bynder's taxonomy management's main features and functionality.
Discovery Questions
- What kinds of assets are you creating? Do they fit in the current asset type/asset subtype list?
- How do you search for your assets?
- If other people ask you for assets, what do they ask for?
- What terms do they use?
- Tell me about a time someone couldn't find an asset they were looking for.
- What did they do? Can you learn anything from those results?
- If you have advanced analytics, What terms did users search that led to 0 results?
- Do you have rights management/licensing issues for your assets?
- What information do you need to track in this regard?
- Rightsholder name and contact information, license term/expiration date, rights granted by medium/platform, etc)
Don't Reinvent the Wheel!
You chose Bynder over your old DAM or folder structure for a reason. There's no need to replicate your previous system exactly. Take what works and leave the rest behind.
Use Automations Wisely
Automations are valuable for streamlining asset organization and ensuring accurate categorization, especially when working with large groups of assets. However, overusing automations can lead to an overly complex structure, making it challenging for users uploading assets to mark the correct metadata. A well-balanced approach ensures assets are easily discoverable without overwhelming contributors with unnecessary complexity.
Avoid Duplicate Terms
Having the same option in multiple metaproperty categories can confuse. Strive to use unique terms across categories.
Build a Common Vocabulary
Standardize your terms whenever possible to ensure clarity and consistency across your DAM.
Consider Integrations
Your DAM should serve as the content engine and the source of truth for digital assets across your tech stack. Determine what information needs to be exchanged between your systems and what metaproperty fields will be required for those API calls.
Consider including metaproperties that facilitate connections with other systems, such as a PIM or CMS, using properties such as Product Category, Product Name, and Product ID.
For more information, check out our Integration Marketplace, Bynder's API Documentation and Developers Portal