Some Information about Hierarchical Relationships Between Metadata Elements

Similar documents
Utilizing PBCore as a Foundation for Archiving and Workflow Management

DCMI Abstract Model - DRAFT Update

A SHORT GUIDE TO IDENTIFIERS FOR THE DIGITAL SUPPLY CHAIN

DevPlan User Guide. Table of Content. DevPlan User Guide. Author: TechExcel co.ltd

IPR Issues (2/2) Standardisation initiatives around Digital Rights Management. IPR Issues. Multimedia content. Representation: Metadata

DevPlan User Guide. Table of Content. Author: TechExcel co.ltd. Date: DevPlan User Guide

Archivists Toolkit: Description Functional Area

Databases The McGraw-Hill Companies, Inc. All rights reserved.

16/06/56. Databases. Databases. Databases The McGraw-Hill Companies, Inc. All rights reserved.

Increazing interactivity in IPTV using MPEG-21 descriptors

SCORM Content Aggregation Model [ CAM ] 4 th Edition

Program Service Data (PSD) and PBCore. Initial Mapping and Recommendations

DATABASE MANAGEMENT SYSTEMS

Vocabulary-Driven Enterprise Architecture Development Guidelines for DoDAF AV-2: Design and Development of the Integrated Dictionary

A Digital Preservation Roadmap for Public Media Institutions

ATTACHED BINARY OBJECT DATA STANDARD


Chapter 13 XML: Extensible Markup Language

Copyright 2010, Oracle. All rights reserved.

Teiid Designer User Guide 7.5.0

3. Technical and administrative metadata standards. Metadata Standards and Applications

Reusability and Adaptability of Interactive Resources in Web-Based Educational Systems. 01/06/2003

Importing Metadata From an XML Source in Test Data Management

Taxonomies and controlled vocabularies best practices for metadata

EIDR SYSTEM VERSION 2.0. Glossary Aug. 12

Generalized Document Data Model for Integrating Autonomous Applications

PeopleTools 8.51 PeopleBook: PeopleSoft Tree Manager

Course Description. Audience. Prerequisites. At Course Completion. : Course 40074A : Microsoft SQL Server 2014 for Oracle DBAs

Work Break Down Structure Template

Its All About The Metadata

The functions performed by a typical DBMS are the following:

A Tool for Managing Domain Metadata in a Webbased Intelligent Tutoring System

Accessibility Features in the SAS Intelligence Platform Products

The Benefits of Component Object- Based SCADA and Supervisory System Application Development

Unit 10 Databases. Computer Concepts Unit Contents. 10 Operational and Analytical Databases. 10 Section A: Database Basics

Enterprise Architect. User Guide Series. Time Aware Models. Author: Sparx Systems. Date: 30/06/2017. Version: 1.0 CREATED WITH

All Adobe Digital Design Vocabulary Absolute Div Tag Allows you to place any page element exactly where you want it Absolute Link Includes the

Future Directions in Simulation Modeling. C. Dennis Pegden

Metadata: The Theory Behind the Practice

Enterprise Application Integration (EAI) Chapter 6 The EAI Process Methodology or Madness?

How to Use EIDR to Identify Versions for Distribution Purposes: Edits, Languages, and Regional Releases

Digital object and digital object component records

Web Site Design Principles. Principles of Web Design, Third Edition

LORD PCAA LIONS Mat.Hr.Sec School, Reserve Line, Sivakasi

CONTENT PLANNING JOB AID

Regional Workshop: Cataloging and Metadata 101

Digital Public Space: Publishing Datasets

Space Details. Available Pages

Understanding Taxonomies

ITU-T. FG AVA TR Version 1.0 (10/2013) Part 16: Interworking and digital audiovisual media accessibility

Visual interfaces for a semantic content-based image retrieval system

Setting and Sharing Adaptive Assessment Assets

MPEG-7. Multimedia Content Description Standard

Description Cross Domain - Metadata Schema Registry Presentation to ISO Working Group Sydney, 2 November 2004

SMD149 - Operating Systems - File systems

Chapter 12 (revised by JAS)

ISLE Metadata Initiative (IMDI) PART 1 B. Metadata Elements for Catalogue Descriptions

INTEGRATED WORKFLOW DEVELOPMENT EDITOR

Metadata Workshop 3 March 2006 Part 1

SOFTWARE ANALYSIS & DESIGN TOOLS

Enterprise Architect. User Guide Series. Model Navigation

SCORM Sequencing and Navigation [ SN ] 4 th Edition

HYPERION SYSTEM 9 PERFORMANCE SCORECARD

A methodology for Sharing Archival Descriptive Metadata in a Distributed Environment

To complete this tutorial you will need to install the following software and files:

Managing Information Resources

National Training and Education Resource. Authoring Course. Participant Guide

Infrastructure for Spatial Information in Europe. Proposed action for update of MIWP: Alternative encodings for INSPIRE data

Copyright 2007 Ramez Elmasri and Shamkant B. Navathe. Slide 27-1

Chapter 1: Introduction

Data Express 4.0. Data Subset Extraction

3) Develop a user interface to facilitate discovery, delivery and rights management of media content

Software Testing and Maintenance 1. Introduction Product & Version Space Interplay of Product and Version Space Intensional Versioning Conclusion

Digital File and Asset Exchange Systems

ACCESSIBLE DESIGN THEMES

COGNOS (R) 8 GUIDELINES FOR MODELING METADATA FRAMEWORK MANAGER. Cognos(R) 8 Business Intelligence Readme Guidelines for Modeling Metadata

5-1McGraw-Hill/Irwin. Copyright 2007 by The McGraw-Hill Companies, Inc. All rights reserved.

Layers. External Level Conceptual Level Internal Level

Introduction to the EIDR Data Model. Mysteries Revealed

Embarcadero DB Optimizer 1.0 Evaluation Guide. Published: July 14, 2008

Guide Users along Information Pathways and Surf through the Data

Workflow option for getting an existing CONTENTdm collection ready for IM DPLA harvest

Multidimensional Aggregation for DNS monitoring

Oracle User Productivity Kit Reports Management. E July 2012

TEXAS A&M AGRILIFE EXTENSION SERVICE PROCEDURES

Course 40045A: Microsoft SQL Server for Oracle DBAs

CMDB. Configuration and Use of the CMDB of Xpert.NET

Rights management through Digital Objects. Norman Paskin The International DOI Foundation

Content Sharing and Reuse in PTC Integrity Lifecycle Manager

SKOS and the Ontogenesis of Vocabularies

A Dublin Core Application Profile for Scholarly Works (eprints)

Fundamentals of Information Systems, Seventh Edition

Getting Started Guide

Software-Architecture, Design Patterns and Refactoring An Overview

Casablanca (1943) and Gone with the Wind (1939). After logging into the site, the search

Lecture 5: Foundation of Network Management

ISO/IEC Information technology Multimedia framework (MPEG-21) Part 3: Digital Item Identification

Getting started with AEM

Adobe Experience Manager (AEM) 6.2 Forms Designer Voluntary Product Accessibility Template

Oracle Fusion Product Requirements and Ideation Management Using Product Requirements and Ideation Management. 11g Release 8 (11.1.

Transcription:

Some Information about Hierarchical Relationships Between Metadata Elements What are Hierarchies? Possible Hierarchical Relationships in PBCore What are Hierarchies? The Public Broadcasting Metadata Dictionary (PBCore) is: a core set of terms and descriptors (elements)... used to create information (metadata)... that categorizes or describes... media items (sometimes called assets or resources). As a simple dictionary of elements, there is no "hierarchy" implied. They are presented in a "flat" arrangement as a listing of 48 descriptors from which you can pick and choose. Some metadata models or schemas are based on a logical, hierarchical arrangement of their metadata elements, not only in the way they are conceptually presented, but also in how they are applied in actual metadata and asset management systems. For example, the IEEE 1484.12.1-2002 Standard for Learning Object Metadata is hierarchical. At the base of their hierarchy is a "root" element. The root element contains many subelements. If a sub-element itself contains additional sub-elements it is called a "branch." Sub-elements that do not contain any sub-elements are called "leaves." This entire hierarchical model is called a "tree structure." The relationship between the root, branches, and leaves is depicted in the figure below (taken from IEEE LOM and the IMS Global Learning Consortium), using sample elements from the IEEE LOM metadata standard.

The IEEE LOM metadata standard can be represented textually using an outline form with tabs and indented sub-tabs. Likewise, when the IEEE LOM metadata standard is expressed graphically, the following categories, branches and leaves appear as they do in this illustration: This hierarchy is honored throughout the application of the metadata elements in any profile or management situation. The PBMD Project has spent over two years comparing and contrasting various metadata descriptors, dictionaries, and schemes in order to arrive at the smallest set of elements that could adequately describe the media items produced by Public Broadcasting radio and television stations that may be shared between stations, regional and national distributors, independent producers, and even vendors of Digital Asset Management systems. The PBCore is a "core" because it can actually be considered a foundation of descriptors used to categorize media items adequately enough so other interested parties can successfully search for and review desired media items. The objective is to be able to share media items and give users complete, well-though-out, descriptions. Good descriptions help end users know what to expect when they decide to review, play or download a media file. As a dictionary, the PBCore implies no hierarchical relationships (root, branches, leaves). However, in the realtor application of the PBCore metadata elements in any profile or management situation, hierarchical relationships can be applied to related and companion elements.

Possible Hierarchical Relationships in PBCore Currently we have 48 main Elements and Sub-Elements. A sub-element is a companion descriptor closely associated with a main element, e.g., publisher is a main element and publisherrole is a companion or associated sub-element. title is a main element and titletype is a companion or associated sub-element. We have gathered the PBCore Elements into three categories. Each category houses elements of a similar nature... CONTENT... 13 elements describing the actual intellectual content of a media asset or resource. INTELLECTUAL PROPERTY... 7 elements related to the creation, creators and usage of a media asset or resource. INSTANTIATION... 28 elements that identify the technical nature of the media asset as it exists in some form or format. The Dublin Core Metadata Initiative (DCMI) has generated a metadata scheme with 15 simple, core, unqualified elements or descriptors. They are presented in a "flat" form without hierarchical layers. Additional elements have been spawned in DCMI. These sub-elements follow a strict set of guidelines in how they are created and how they are to be used, e.g., a sub-element should further define the description for a media item in a more granular manner, but not change, extend, or stray from the underlying meaning of the parent element. After much debate, PBCore has evolved to include DCMI-like structure to its metadata elements. However, at the same time (in the interest of simplification and reducing the number of core elements) some metadata elements can and probably should be applied in real-world management situations in a hierarchical or tree structure. For example, from the Instantiation-related elements in PBCore, there are a handful of elements that begin with the word "format." Some of these elements are relevant only to audio media items, some to image and moving image media items. The "format" elements, if crafted in a flat manner, would have existed, redundantly, as in the following chart: A FLAT ARRANGEMENT OF PBCORE ELEMENTS audio media types formataudiogenerations formataudiostandard formataudioencoding formataudiofilesize formataudiotimestart formataudioduration formataudiodatarate formataudiobitdepth formataudiosamplingrate video media types formatvideogenerations formatvideostandard formatvideoencoding formatvideofilesize formatvideotimestart formatvideoduration formatvideodatarate formatvideobitdepth formatvideoframesize

formatvideoaspectratio formatvideocolors still image media types formatimagegenerations formatimagestandard formatimageencoding formatimagefilesize formatimagebitdepth formatimageframesize formatimagecolors In contrast, if the "format" elements are collapsed (as they currently are in the PBCore v1.0) to express basic format concepts, and are then applied selectively and intelligently to various media types, hierarchical relationships emerge. These relationships can be expressed in the actual application of the PBCore, depending on the databases, systems, and manner in which the PBCore elements are exploited. Below is an example of a hierarchy using a textual, tabular format. A HIERARCHICAL ARRANGEMENT OF PBCORE ELEMENTS formatmediatype > Audio - formatencoding - formattimestart - formatduration - formatdatarate - formatsamplingrate > Moving Image - formatencoding - formattimestart - formatduration - formatdatarate - formatframesize - formataspectratio - formatcolors > Static Image

- formatencoding - formatframesize - formatcolors 2005 Corporation for Public Broadcasting