An Introduction to Metadata and Taxonomies

These terms get thrown around a lot—but what exactly do they mean? Never fear. Let’s clear up definitions and applications of these two content strategy must-haves.

As the structured/adaptive content conversation progresses, metadata and taxonomies will also become more and more important. To participate in the conversation, you don’t need to know everything—but you do need to understand the essential foundations so you can ask the right questions.

The goal of this post is to provide an introduction to the concepts, so you can get a general understanding and feel comfortable digging into more information.

Now, this conversation gets big in a hurry—but don’t be intimidated. These terms have been around much longer than the internet, and can be applied in a wide variety of contexts. In the hopes of making this post a bit more approachable, I’m going to fast-forward through the structured content conversation with the diagram below.

structured-content

Simple enough, right? I’ll be skipping past why and how to break your content up into components, and instead focus on how metadata and taxonomies get applied to content components.

Metadata

The information provided in metadata makes the content findable and understandable to either a human or a computer. There are lots of definitions out there, but when it comes to metadata, I look to Rachel Lovinger, the metadata guru. She defines metadata as “information about the content that provides structure, context, and meaning.”

There are three main types of metadata:

  • Structural: Defines the metadata elements that need to be collected; labels like title, author, date created, subject, purpose, etc. Defining these structural elements is typically based on a mix of organizational and system needs, along with standard schemas like Dublin Core.
  • Administrative: Often created automatically when content is entered into the CMS, these values are used to manage the content. Administrative metadata includes things like date created or author. They can sometimes include sub-elements about rights-management or preservation.
  • Descriptive: These values describe aspects specific to each content component, like title, subject, audience, and/or purpose.

Some of each of the three types of metadata is likely to be used on a typical piece of content, but how and when they get defined is very different. The structural metadata gets identified as part of your system requirements. Administrative and descriptive metadata are identified during the creation or curation of specific content. If you think of it like a form, the structural metadata supports which information needs to be collected (fields on the page), and the descriptive and administrative metadata provide the values for those form fields.

Here’s how they work together:

metadata example

Taxonomy

The term taxonomy gets applied across a range of contexts. In the biology world, it means grouping organisms into hierarchical groups (e.g., kingdom, phylum, class, order, family, genus, and species).

The web/digital world typically applies it to any kind of structure that organizes information. Information science people sometimes say “controlled vocabularies” instead of taxonomies. Regardless of the term, the underlying goals are to create some level of consistency and control over the information used to describe a content component, and clarify relationships between them.

Common types include:

  • Term list: A standardized list of terms created to insure consistent tagging and indexing. Think of it as a list of “preferred language.” Term lists typically provide a series of metadata values to pick from for elements like format or content type.
  • Hierarchies: Often called a “taxonomy,” a hierarchy defines the structural framework used to classify terms into parent/child or broad-to-narrow relationships. Hierarchies are specifically used to support layered groups of information and not simply for the convenience of creating groupings—although each level of a hierarchy is commonly referred to as a “category.”
  • Thesauri: A thesaurus translates conceptual relationships between the content, often made naturally by humans, into something a computer can understand. Thesauri typically address three types of relationships: equivalent (synonyms), hierarchical (broad-to-narrow terms), and/or associative (related terms).

How they work together:

At its simplest, a taxonomy organizes information, and metadata describes it. For the taxonomy to be able to organize the information, terms need to be stored as metadata. It all works together to make the content findable, recognizable, and useful.

An example:

metadata-taxonomy

Not every site needs every one of these things, but this diagram illustrates how these elements can feed into each other and how they help display content to the user.

What’s next?

Admittedly, I’ve over-simplified these concepts to make them easier to understand. If you’re interested in learning more about metadata, taxonomies, and structured content, there’s no end to the list of resources out there.

Here are a few to get you started:

This post was written by Christine Benson and has appeared previously on our blog.

Learn how to get the writing done on your digital products. A new book by Brain Traffic’s Scott Kubie, now available from A Book Apart.
https://www.braintraffic.com/blog/an-introduction-to-metadata-and-taxonomies
www.braintraffic.com
crawl=CC-MAIN-2019-22
24588
application/http; msgtype=response
sha1:YLG5JPX2P65EFB4XNE4WNZ7WUL3IXQWC
<urn:uuid:1e2e44d0-168e-4965-b72e-651f00376a96>
2019-05-23T23:22:37Z
76.223.9.102
text/html
sha1:C5WK3OB2X4DVWB5RGEJFVI6KHJFKXCJ5
<urn:uuid:0fca6043-93d6-4ad3-9f2b-b17d8970b41f>
https://www.braintraffic.com/blog/an-introduction-to-metadata-and-taxonomies
response
<urn:uuid:7c4d13e5-bfb3-43cf-94bf-249a5ac240d8>
isPartOf: CC-MAIN-2019-22
publisher: Common Crawl
description: Wide crawl of the web for May 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-113-197-177.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/