Steps To Digital Asset Management Metadata Success: A Guide To Getting It Right
Steps To Digital Asset Management Metadata Success: A Guide To Getting It Right
Steps To Digital Asset Management Metadata Success: A Guide To Getting It Right
Sponsored by
A DCG TOOL
DigitalClarityGroup.com | @Just_Clarity
DIGITAL ASSET MANAGEMENT METADATA SUCCESS
AND Here are just some benefits of even a simple metadata schema: provides context and information
about your digital assets like
WHY SHOULD Increased findability: Tagging digital assets with even just a few basic
metadata fields such as title, keywords, and licensing information can
images, videos, sales collateral,
etc.
I CARE? mean the difference between looking for a needle in a haystack and
finding the asset and picking it up off a library shelf. A defined metadata schema may
include standards and models,
Brand consistency: Metadata helps enforce brand standards by making as well as tactical elements such
the most relevant and recent brand assets easily accessible. as controlled vocabularies and
taxonomies.
Reduced risk: Maintaining administrative metadata enables the tracking
and enforcement of assets’ rights management and lets people know how
and where the file can be used.
Combined, these benefits can add up to large financial savings through gained
efficiencies and fewer licensing infractions (read: litigation and financial
penalties).
© 2017 | [email protected] 2
TYPES OF METADATA
There are many types of metadata that can be tracked. Examples of metadata fields by metadata type
Here are some examples:
Administrative metadata typically tracks assets’ usage and rights Subject ... Date created Publication status
restrictions of the intellectual property such as licensing details,
expiration dates, geographic parameters, etc. Title ... File type ...
Technical metadata tracks the internal contents Description ... Review date ...
Process metadata aligns with the workflow and/or status of the project/
job associated with the development of the asset.
Technical Process
Which of these types to use and how much metadata is managed depends
Database ... Approver Project number
on many factors including available time, resources, and DAM system
capabilities. Starting with a small, focused set of fields and then evolving Glossary referenced ... Status ...
to a more complex schema is a great way to instill best practices and good
metadata habits. Table name ... Project name ...
1 2 3 4 5
Determine your Understand Identify DAM Understand the What metadata do
DAM business goals your DAM users’ stakeholders. metadata process. you need?
DAM and then consider information needs,
what metadata you and how they access
METADATA: will need to reach assets.
Who will be involved in
creating and maintaining the
Document the “who, when,
and how” of metadata
Define the necessary fields
and how they should be
STRATEGY FOR strategy will be different partners, channel) resources possible, build on existing
typically find or search for
if your focus is simplifying who contribute to and/or positive behaviors and
the assets they need: File
use the assets. processes.
SUCCESS
access to digital assets name? File type? Creator?
compared with facilitating
collaboration between
teams producing creative
and marketing materials.
Identifying use cases can
help define and articulate
the business goals.
© 2017 | [email protected] 4
METADATA SET-UP CHECKLIST
NAMING CONVENTIONS
Consistency is one of the keys to a successful metadata strategy. Along with DAM business goals align with/
documenting common language, setting a standard for how files are labeled support at least one organizational
and described can exponentially improve the findability and usability of goal.
your digital assets by making them easier to identify and evaluate in search
results. Typically, both File Name and Description metadata field names Consider current and potential
DAM users to be included in the
are free text entry fields, making it even more important that there be
discovery process.
standards for users to follow.
The following is an example of what the naming convention Consider current and potential
for a campaign asset might look like: DAM users to be included in the
discovery process.
Description
DAM metadata processes are as
Naming convention Campaign Name, Creative, Asset Type, Asset Size, Language simple as they can be.
Metadata entered Reach for the Stars and Win, Starburst, Digital Banner, 468x80, US English Metadata requirements are
identified as must-have, good-to-
have, or nice-to-have.
File Name
Naming conventions are defined
Naming convention CampaignNameAbbreviation_Creative_AssetType_Size_Language for file name and description fields.
SOURCING
THE DATA
Embedded standards such Integrate with other Examine the folder Also, consider the types of
as XMP or IPTC can be solutions like content structure in other assets to be managed by
extracted via specialized management systems repositories or network the DAM system, and how
readers or photo editing (CMS), product information drives for insights into how they are used. Different
software systems. management (PIM) digital assets are currently teams may have the
systems, or other DAMs, organized. information, so ask around
to leverage the metadata and gather what you can to
already in use. save time and effort.
© 2017 | [email protected] 6
MORE ON STANDARDS GATHERING DATA CHECKLIST
POPULATING
THE DAM WITH
METADATA Templates Mark-up tools Extraction tools
are structured forms that allow users structure the metadata attributes automatically create metadata from
to enter the metadata values into and values into the specified schema an analysis of the digital asset. These
pre-set fields that match the element language. Most of these tools tools are generally limited to textual
set being used within the DAM generate XML or SGML Document resources.
system. The template then generates Type Definitions (DTD).
a formatted set of the element
attributes and their corresponding
values.
© 2017 | [email protected] 8
It is important to keep in mind that the quality of the metadata extracted from ENTERING METADATA
other systems can vary significantly based on the tools used, as well as the CHECKLIST
content and structure of the source text. Any metadata automatically entered
via a tool should reviewed and edited for accuracy and compliance defined Determine which fields can/will
metadata standards. be automatically populated vs.
manually entered.
Title
THE DATA Description / Abstract
Keywords
Recommended use
Run time
Copyright
Format
© 2017 | [email protected] 10
Look to existing standards such as Dublin Core and other A WORD OR TWO ON LANGUAGE SETTING UP DATA CHECKLIST
industry or topic related standards for guidance and
Common language: Not everyone using the DAM system Review existing metadata.
suggestions on which fields to choose for your metadata
will speak the same language, literally or figuratively.
schema.
Where a Publisher might refer to an asset shot with a Identify fields by file type.
Your metadata schema will outline whether fields camera an “image” a marketer might call it a “photo”.
are mandatory, recommended, or optional. Have To overcome these potential conflicts, a corporate Identify common fields across
the information populated automatically – file type, lexicon should be developed that identifies the formal file types (rename where it
creation date, etc. – when the file is added to the DAM term, as well as lists commonly used slang, acronyms, makes sense to align values).
system. Then, define fields with controlled vocabulary departmental terms, and abbreviations. These should
via checkboxes or dropdown menu pick lists whenever then be captured in a glossary that is shared and Develop a corporate lexicon.
possible. This will facilitate the process for users as well as accessible to all users.
ensure consistency in the data being entered.
Description
GeoLocation
© 2017 | [email protected] 12
Not all metadata fields will be applicable to all digital asset types. Ensure that DEFINING DATA CHECKLIST
the required and optional fields are relevant for the asset type they represent.
Controlled vocabulary within required fields will significantly improve asset Categorized metadata
findability. fields as either Required,
Recommended, or Optional.
Once the schema is defined, the values for the fields can be defined using a
taxonomy (pre-determined terms) or hybrid vocabulary (blend of pre-determined Define values for
terms and open text). Fields can also be open to user entry, but this should Required fields.
be restricted to optional elements where consistency has less impact on the
integrity of the metadata. Create a metadata schema.
Describing a digital asset with Having interoperable metadata Having a defined organizational
metadata allows it to be understood based on accepted standards, such lexicon, such as a dictionary,
MAKING by all users – human and machine. As as the XMP framework, allows glossary, and/or thesauri help in
BEST keep all that hard work paying off. Consult with current and potential
DAM system stakeholders,
13. Relation: How the content relates to other resources; for instance, Global Information Locator
if it is a chapter in a book. Services (GILS)
Field Name Description Entry Type Priority Single/Multiple Vocabulary Values Field Name: The name of the area/field within
the DAM system where the information will be
Example: Widget1 Sales Sheet NA-English
Text Required Single Open entered.
File Name (Product Name – Asset Type – Language)
Description: Leverages the same information
Optional
Recommended
Required Multiple
Single Open
Controlled in the file name but presents it in plain English
in accordance with the predetermined naming
Optional
Recommended
Required Multiple
Single Open
Controlled
convention.
Optional
Recommended
Required Multiple
Single Open
Controlled
Entry Type: Describes how the data will be
Optional
Recommended
Required Multiple
Single Open
Controlled
entered (text, numbers, text block, imported,
Optional
Recommended
Required Multiple
Single Open
Controlled etc.)
Optional
Recommended
Required Multiple
Single Open
Controlled Priority: Identifies whether the field will be
Optional
Recommended
Required Multiple
Single Open
Controlled required for the asset to be catalogued into the
DAM system, or if it is recommended or options
Optional
Recommended
Required Multiple
Single Open
Controlled (not required for the asset to be saved).
Optional
Recommended
Required Multiple
Single Open
Controlled
Single/Multiple: Indicates whether only one
Optional
Recommended
Required Multiple
Single Open
Controlled value or multiple values can be entered. This can
also include details of any character limitations.
Optional
Recommended
Required Multiple
Single Open
Controlled
Optional
Recommended
Required Multiple
Single Open
Controlled Vocabulary: Dictates if the fields will be open
entry or if users will select from a controlled
Optional
Recommended
Required Multiple
Single Open
Controlled vocabulary via pre-defined options presented via
Optional
Recommended
Required Multiple
Single Open
Controlled a drop-down menu, pick lists, etc.
Optional
Recommended
Required Multiple
Single Open
Controlled Values: This field details the options that will be
presented when a controlled vocabulary is being
Optional
Recommended
Required Multiple
Single Open
Controlled
used.
© 2017 | [email protected] 19