|
|
|
WHAT IS UMAP?
The Utah Metadata Application Profile, otherwise known as UMAP, is a collection of descriptors used to identify and depict media items (often referred to as a metadata dictionary). The media items are made available for search, review, and download from the Utah Education Network Digital Media Service. Assets in the UEN DMS collections include video, audio, text (pdf), images, "interactives," and Flash files. The DMS Service (http://www.uen.org/dms) provides digital media assets for three primary audiences...
- eMedia: for Utah's K-12 educators and students
- CollegeMedia: for Utah's institutions of higher education
- MediaHub: for the general public
Other collections are also served from the UEN DMS, including...
- UCME, the Utah Collections Multimedia Encyclopedia with over 7000 videos, audio files, images and articles about Utah's geography, history, and culture.
- KUED-TV, the University of Utah's public broadcasting television station, offering numerous media assets in its media on demand program distribution.
The asset management system underlying the UEN DMS service is a product known as "Telescope" from North Plains Systems. The system prescribes which assets and which metadata descriptions are published to different users and groups as determined by the rights and privileges assigned to those users and groups ("entitlement management").
Twelve metadata schemas played a primary role in building the final UMAP "application profile" (currently in version 2). The application profile, by best practices, harvests pre-defined metadata elements from established metadata dictionaries and schemas.
An Application Profile is a set of metadata elements, policies, and guidelines defined for a particular application or situation. The elements may be harvested from one or more element sets, thus allowing a given application or profile to use pre-established, well-formed, standardized metadata in addition to other medadata descriptors that are created and defined locally (custom metadata). For example, a given application might choose a subset of the Dublin Core that meets its needs, or may select elements from the Dublin Core, another element set, and several locally defined elements, all combined in a single schema. An Application Profile is not complete without documentation that defines the policies and best practices appropriate to its use and application.
http://library.csun.edu/mwoodley/dublincoreglossary.htmlUMAP contains a total of 115 metadata fields. Most of the data fields are used exclusively by catalogers in order to create very granular descriptions and rights management data (what we call "cataloging fields"). Only 28 metadata fields are actually published to end users as they search and review media items (what we call "published fields"). Some of these 28 fields are actually concatenations of multiple entries made in the "cataloging fields." To learn more about the candidate metadata dictionaries and schemas used to construct UMAP, go to our web page Candidate Schemas.
The final UMAP Application Profile is structured in a specific hierarchy and conforms to the following...
UMAP conforms to the
IMS Global Learning Consortium Learning Resource Meta-data
Best Practice and Implementation Guide
for the IEEE 1484.12.1-2002, Learning Object Metadata Standard:
LOMV1.0 Base Schema plus Utah Localized ExtensionsThe final UMAP Application Profile and its metadata elements can be viewed by using the link UMAP USER GUIDES or by selecting from the "Select a QuickLink" menu found at the top of most of the pages within this website. The User Guides organize the UMAP metadata elements into six different lists, depending on how one wishes to interact with the metadata fields and their definitions.
METADATA...A BRIEF PRIMER
We've generated quick reviews for understanding what metadata is and the context in which the UMAP Metadata Elements were created. This Primer is in a Question & Answer format and can be found through this link: A PRIMER TO UNDERSTANDING METADATA . Other references are also included.
Disclaimer
author: Paul E Burrows
Media Solutions
University of Utah
pburrows@media.utah.edu
