Elements are objects that define a metadata field and its values, semantics, attributes, and properties (for a list of the attributes defined for UMAP elements, see our web page UMAP Element Attributes). An Element is the actual "thing" that carries the descriptive metadata about a media item, such as a title, a date, keywords, rights information, mime types, media types, etc. The metadata elements are what a cataloger interacts with (creating descriptions) within a cataloging tool or asset management system.

An element may be standalone. If several metadata fields are thematically related to each other, then they are governed by a larger theme, and shoud be bound together when data is shared. When bound, these related elements become part of what is called an Element Container.

An example of related Elements bound within an Element Container are four associated elements named *Copyright status*, *Copyright notice*, *Copyright date* and *Copyright held by*. They are bound together by the Element Container called the *Copyright Group*.

An advantage to using the Element Container approach is that, unlike the basically flat arrangement of elements found in Dublin Core (http://www.dublincore.org), UMAP is able to bind together the data found in related elements and keep them that way, like a family traveling together in a bunch; whether they take a plane, a bus, or a train for transportation, they always move together as a unit.

Within the hierarchical structure of a metadata scheme, a Container may house Sub-Containers, which themselves bind together related Elements. The structure begins to look very similar to the way that folders and sub-folders contain files within the directory structure of one's computer hard drive.

Element Containers enhance the ability to understand the hierarchical structure of a data dictionary and its associated data models. This hierarchical structure is easily viewed by observing a Graphical Illustration of the UMAP Elements, their interdependencies within Element Containers, housed within Content Classes. To view a graphical interpretation of UMAP metadata elements, click on the link directly below...

GRAPHICAL VIEW
OF UMAP METADATA ELEMENTS

To see a table of the elements organized by Element Containers within Content Classes, link to our web page UMAP Elements Viewed by Content Classes (and associated Containers).

For an expanded discussion, link to our web page on Hierarchical Relationships and Element Interdependencies.

To read about other components in hierarchies, link to our web page on Content Classes .