UEN DMS (Utah Education Network Digital Media Service)
& UMAP (Utah Metadata Application Profile)

Context
PBCore Integration
Contacts

Other Case Examples

The Utah Metadata Application Profile, otherwise known as UMAP, is a collection of metadata descriptors used to identify and depict media items. These metadata files and their associated media assets are made available for search, review, and download from the Utah Education Network Digital Media Service (http://www.uen.org/dms). Assets in the UEN DMS collections include video, audio, text (pdf), and image files. The service provides digital media assets for three audiences...

eMedia
eMedia offers educational media to Utah’s K-12 schools. It includes videos and other media from the Utah Instructional Media Consortium, local documentaries and current affairs programs from KUED-7, national PBS programs, and additional media from UEN and other trusted education partners. This service is only available to K-12 teachers and students in Utah through the Pioneer Library.

CollegeMedia
CollegeMedia offers media appropriate for college students. Videos and other media include college telecourses, local documentaries and current affairs programs from KUED-7, national PBS programs, and additional media from UEN and other trusted education partners. Because of licensing restrictions, CollegeMedia is only available to faculty and students affiliated with schools in the Utah System of Higher Education.

MediaHub
UEN offers general public access to local current affairs programs from KUED-7, media from special community events and additional media from UEN and other trusted education partners. This media is for non-profit private use only.

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.

There are currently a total of 115 metadata fields in UMAP. Most of the fields are used exclusively by catalogers in order to create very granular descriptions and rights management data ("cataloging fields"). Only 28 metadata fields are actually published to end users as they search and review media items ("published fields").

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 Extensions

In building the final metadata dictionary, the UMAP "application profile" (currently in version 2), almost twenty metadata schemas were consulted, evaluated, and harvested.

• ARIADNE
  ARIADNE is a European Association open to the World, for Knowledge Sharing and Reuse, E-Learning for all, International Cooperation in Teaching, Serving the Learning Citizen. Metadata Schema used extensively in Higher Education venues.
• DCMI -- Dublin Core Metadata Initiative
  The Dublin Core Metadata Initiative is an open forum engaged in the development of interoperable online metadata standards that support a broad range of purposes and business models. DCMI's activities include consensus-driven working groups, global conferences and workshops, standards liaison, and educational efforts to promote widespread acceptance of metadata standards and practices
• DC-Ed: DCMI Education Working Group
  A Proposal from the Dublin Core Education Working Group [DCEd] to the Dublin Core Usage Committee of the Dublin Core Metadata Initiative [DCMI]. While the objectives of the Working Group in 2003-2004 will include continuing discussion and development of proposals for the use of Dublin Core metadata in the description of educational resources, particular emphasis will be placed on developing strong, ongoing (formal and informal) working relationships among existing metadata standards initiatives for resource description in learning, education and training with the aim of advancing the goal of metadata interoperability within the domain.
• GEMCat: Gateway to Education Media Cataloguing Module & Tools
  The cataloging module, GEMCat, is a stand-alone program for cataloging Internet resources using the GEM element set, profile, and controlled vocabularies.
• HEAL: Health Education Assets Library
  The Health Education Assets Library (HEAL) is a digital library that provides freely accessible digital teaching resources of the highest quality that meet the needs of today's health sciences educators and learners. The HEAL metadata schema is the foundation on which the HEAL distributed system is built; the schema is based on international standards and includes extensions specific to the health sciences. Users may implement the HEAL metadata schema on their local systems or may further extend the schema to meet local needs. The metadata schema provides an important mechanism for HEAL to share metadata with affiliate partner collections located on remote servers.
• IEEE-LTSC LOM (Learning Technology Standards Committee Learning Object Metadata)
  This standard will specify the syntax and semantics of Learning Object Metadata, defined as the attributes required to fully/adequately describe a Learning Object. Learning Objects are defined here as any entity, digital or non-digital, which can be used, re-used or referenced during technology supported learning. Examples of technology supported learning include computer-based training systems, interactive learning environments, intelligent computer-aided instruction systems, distance learning systems, and collaborative learning environments. Examples of Learning Objects include multimedia content,instructional content, learning objectives, instructional software and software tools, and persons, organizations, or events referenced during technology supported learning. The Learning Object Metadata standards will focus on the minimal set of attributes needed to allow these Learning Objects to be managed, located, and evaluated. The standards will accommodate the ability for locally extending the basic fields and entity types, and the fields can have a status of obligatory (must be present) or optional (maybe absent).
• IMS: Accessiblity
  The AccessForAll Meta-data specification is intended to make it possible to identify resources that match a user's stated preferences or needs. These preferences or needs would be declared using the IMS Learner Information Package Accessibility for LIP specification. The needs and preferences addressed include the need or preference for alternative presentations of resources, alternative methods of controlling resources, alternative equivalents to the resources themselves and enhancements or supports required by the user. The specification provides a common language for identifying and describing the primary or default resource and equivalent alternatives for that resource. This work represents open collaboration between working group members from IMS, Dublin Core, IEEE, CEN-ISSS, Eduspecs as well as other groups. The AccessForAll Meta-data specification is a proposed unified approach to matching user needs and preferences with the resources that address those needs and preferences across the participating specifications bodies.
• MARC
  A MARC record is a MA chine-Readable Cataloging record. And what is a machine-readable cataloging record? Machine-readable: "Machine-readable" means that one particular type of machine, a computer, can read and interpret the data in the cataloging record. The following pages will explain why this is important and how it is made possible. Cataloging record: "Cataloging record" means a bibliographic record, or the information traditionally shown on a catalog card. The record includes (not necessarily in this order): 1) a description of the item, 2) main entry and added entries, 3) subject headings, and 4) the classification or call number. (MARC records often contain much additional information.)
• MPEG-7
  MPEG-7 is an ISO/IEC standard developed by MPEG (Moving Picture Experts Group), the committee that also developed the Emmy Award winning standards known as MPEG-1 and MPEG-2, and the MPEG-4 standard. MPEG-1 and MPEG-2 standards made interactive video on CD-ROM and Digital Television possible. MPEG-4 is the multimedia standard for the fixed and mobile web enabling integration of multiple paradigms. MPEG-7, formally named "Multimedia Content Description Interface", is a standard for describing the multimedia content data that supports some degree of interpretation of the information meaning, which can be passed onto, or accessed by, a device or a computer code. MPEG-7 is not aimed at any one application in particular; rather, the elements that MPEG-7 standardizes support as broad a range of applications as possible.
• OAI: Open Archives Initiative
  The Open Archives Initiative Protocol for Metadata Harvesting (referred to as the OAI-PMH) provides an application-independent interoperability framework based on metadata harvesting. There are two classes of participants in the OAI-PMH framework:
• Data Providers administer systems that support the OAI-PMH as a means of exposing metadata; and
  Service Providers use metadata harvested via the OAI-PMH as a basis for building value-added services.
• ODRL: Open Digital Rights Language model for DRM
  The Open Digital Rights Language (ODRL) is a proposed language for the Digital Rights Management (DRM) community for the standardisation of expressing rights information over content. The ODRL is intended to provide flexible and interoperable mechanisms to support transparent and innovative use of digital resources in publishing, distributing and consuming of electronic publications, digital images, audio and movies, learning objects, computer software and other creations in digital form. The ODRL has no license requirements and is available in the spirit of "open source" software.
• PBCore: Public Broadcasting Metadata Dictionary Project
  The PBCore (Public Broadcasting Metadata Dictionary) was created by the public broadcasting community in the United States of America for use by public broadcasters and related communities. Initial development funding for PBCore was provided by the Corporation for Public Broadcasting. The PBCore is built on the foundation of the Dublin Core (ISO 15836), an international standard for resource discovery (dublincore.org), and has been reviewed by the Dublin Core Metadata Initiative Usage Board.
• SMPTE DMS-1: Descriptive Metadata Scheme
  From the Society of Motion Picture and Television Engineers, this descriptive metadata scheme, now known as DMS-1, started life as a short list of metadata items that were needed to replicate roughly the equivalent of a tape label. Inevitably, this list grew rapidly in an attempt to create a common initial framework of metadata items that might be implemented by manufacturers in order to achieve interoperability.
• UCME: Utah Collections Multimedia Encyclopedia
  The Utah Collections Multimedia Encyclopedia is an ever-expanding world wide web site whose contributors include many institutions, organizations and agencies throughout Utah. Utah Collections serves as a storehouse of multimedia items which educators, professors and students can freely use in lesson plans, reports and projects without fear of copyright infringement. UCME developed a comprehensive metadata schema in 1995 in order to describe its assets and to increase their findability over the web.
• USOE Core Curriculum: Utah State Office of Education
  The Utah State Office of Education maintains a set of core curriculum standards and objectives against which all teaching must comply in the state of Utah for K-12.
• vCard
  vCard is the electronic business card. It is a powerful means of Personal Data Interchange (PDI) that is automating the traditional business card. Whether it's a computer (hand held organizer, Personal Information Manager (PIM), electronic eail application, Web Browser) or telephone, the vCard revolutionizes personal communications.

Where possible and logical, UMAP parallels PBCore. The semantics or meaning behind the common data elements are the same. As well, the structure or syntax for data entry are drawn from PBCore, as are pre-established picklists of terms and vocabularies. Some of the fields in UMAP use variations on the actual names used in PBCore. It was determined that it did not matter what a field was called, so long as the underlying descriptions matched PBCore. The names were altered in order to offer a more informal language style for catalogers and educators browsing the UEN Digital Media Service. Similarities between PBCore and the UMAP are unavoidable, since the data dictionary design was accomplished by a 6-year veteran of the PBCore Team.

There is always a gap between the granularity of metadata fields that catalogers prefer to use to capture a full-flavored and accurate description of a media item and the simplicity of "Google-like" search interfaces and the associated listing of results. Using the functionality of the North Plains "Telescope" DAM system, rules were written that concatenate multiple data fields painstakingly vetted by catalogers into a single, collated field. Thus, catalogers are able to capture well-formed descriptions and end-users are only exposed to a smaller, limited number of descriptions upon which they can make evaluations for media items of interest. An example is in order...

In UMAP and in PBCore, as borrowed from Dublin Core, there is a data entry field known as "Spatial Coverage." Keywords or specific geographic coordinates are employed in entering the descriptors for Spatial Coverage. As a cataloger, one must be well-trained in order to recall all the necessary attributes that would be used to create a description about a media item that summarizes its geographical locations. An alternative is to actually create multiple metadata fields, each specific to a component of a geographical description; multiple fields act as reminders to catalogers of all expertise levels.

In UMAP, the multiple fields used to capture very granular data about a media item's geographical locations are...

• Collective formation or place (e.g., Arches National Park)
• Specific formation or place (e.g., Delicate Arch)
• Municipality-city, town, village (e.g., Moab)
• County or township (e.g., Grand County)
• State, province, or territory (e.g., Utah)
• Country or nation (e.g., United States of American)
• Continent (e.g., North America, or even Oceania, Pangaea, or Gondwana)
• Body of water (e.g., The Colorado River, or even The Great Salt Lake)
• Off world location (e.g., Uranus, Deimos, Circinus, Algebar, M86, Trifid Nebula, Blackeye Galaxy)

A rule is written that concatenates these 9 fields into a statement that becomes a single "Spatial Coverage" descriptor. It is this statement that is presented to end-users as a combined collection of geographical keywords.

Anyone is invited to review the UMAP metadata application profile. The UMAP User Guides are published as HTML documents and present the 115 elements through six different filters or views...

The UMAP User Guides are located at this URL-- http://www.uen.org/dms/UMAP/.

CONTACTS:

Other Case Examples