Growth Series BLOG

Its a Premium BLOG template and it contains Instagram Feed, Twitter Feed, Subscription Form, Blog Search, Image CTA, Topic filter and Recent Post.

All Posts

Naming Conventions for Digital Assets: How much is too much?

Digital assets come in a seemingly limitless variety of flavors. Some intrinsic metadata comes along for the ride with particular formats, but without a robust metadata system and workflow in place, many assets will be “left behind” in any digital asset management (DAM) system. Use a systematic approach to naming: reduce the burden on users who need to open assets to determine contents, get those assets appearing in search results, and prevent misplaced files and data extinction down the road.

We’ve consulted with many clients who were in the process of migrating to a new DAM system or refreshing outdated practices with their current one (or two…or five). Regardless of where you are at in your DAM project, establishing a nomenclature for assets must be considered (and the sooner the better, to prevent costly cleanup work after the fact). The following provides some tips when brainstorming conventions:

  1. Brevity, relevance, and consistency Keep names short and sweet; easy to read, logical, and indicative of what is contained within. As you will find, in some contexts brevity loses out to more important factors, but the ultimate goal is to keep it consistent.
  2. Human intervention People will be creating and reading asset names. Creating complicated titles can be time consuming; if your users need to refer to a manual just to name an asset, there’s a good chance the convention will not be adopted. Also keep in mind that local acronyms and abbreviations may not make sense to all users that access the system.
  3. Ordering of elements Do users need the ability to view assets sorted in a list? Certain name elements such as a unique identifier, date, or version numbers should be placed at the front or back of the name.
  4. Refer to standards No need to reinvent the wheel; the same international standards we use to control such values as date or country in a taxonomy can and should be applied to asset naming.
  5. Interoperability Make sure your asset names play well with different operating systems. For example, Windows allows 256 characters while Macs support up to 31 (although you shouldn’t need that much). Other characters to avoid include < > & $ / \ [ ] * :
  6. Separation anxiety Use _ (underscore) in between elements. Avoid using spaces or CamelCase. On the web spaces are treated as “%20”, and a search query for “Press Release” may not unearth the file you named “PressRelease” if the system treats it as one word.
  7. Leverage that taxonomy! A great taxonomy will contain vocabularies that can be reused for controlling values of name elements, for example asset type and subject. Subject analysis is a costly and time consuming endeavor best performed by trained experts, especially in the case of images or video where automatic indexing is rarely an option. To describe the “aboutness” of a digital asset in a file name for aiding user selection, fall back on your taxonomy’s subject vocabulary whenever possible.
  8. How does your metadata measure up? Lastly, one of the most important considerations is system-specific. What asset metadata is revealed in the user interface? For example, there’s no reason to ask a user to key in language code “fr” into a name for an asset in French if this metadata is already captured and made explicit. Evaluating the current technology environment will help indicate how many and what kind of elements to include in your naming conventions.
     
Earley Information Science Team
Earley Information Science Team
We're passionate about enterprise data and love discussing industry knowledge, best practices, and insights. We look forward to hearing from you! Comment below to join the conversation.

Recent Posts

Harness the power of AI to drive competitive advantage - CCW Nashville

In this presentation Seth Earley discusses:

How to Design Omni-Channel IVAs That Humans Love To Use

During our webinar, "Omni-channel Virtual Assistants - The Next Frontier in Voice and Text for Customer Service guest speaker Chris Featherstone, who leads business development for AI and speech recognition services at Amazon Web Services (AWS) and Seth Earley, CEO of Earley Information Systems (EIS) discussed ways to design omni-channel virtual assistants to optimize their use across voice and text. When supported by an appropriate information architecture and designed with a deep understanding of the customer, virtual assistants can access enterprise knowledge efficiently, saving time and money. The key to success is to structure the underlying information so it can be retrieved and used by any channel, including humans, to deliver the responses that customers need. Here's a recap of the conversation.