Dictionary Review Team
PBCore Metadata Provisional Recommendations
Second Meeting
Metadata Working Group

September 12 & 13, 2002
Arlington, Virginia

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Dictionary Review Team’s Tasks
–	Identify existing metadata dictionaries
–	Harvest
•	“Take the best and leave the rest”
•	Compare and consolidate
–	Map to existing metadata element sets
•	…or…

How to have a Dublin Coronary
Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Sources of the PBCore Metadata
•	The “Hands-on-Five” and their specific metadata-related projects & experiences

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Merging of the Metadata Fields using Dublin Core elements and qualifiers

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Migration of the Metadata Fields from spreadsheet to database

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Creation of a Grouping Tool for the Metadata Fields
•	Enables the “Hands-on-Five” to indicate which metadata fields should be combined and collapsed.
Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Features of the Grouping Tool
–	Metadata Fields Grouped by Dublin Core Elements and Extensions
Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Features of the Grouping Tool
–	Grouping Numbers Facilitate Groupings
–	Serial Numbers Provide a Unique Metadata Field Identifier
–	Individual Conducting the Groupings is Noted
–	(see next screen)

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Grouping Tool results in five sets of recommendations for combining the harvested metadata fields.

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Recommendations are used to collapse numerous fields into single fields.
•	A separate reporting tool is used to record and report the condensations.
Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Features of the Reporting Tool
–	Newly generated Element Names
–	Collective Comments
–	Collective Notes
–	Encoding Schemes where Identified
–	Serial Numbers of Metadata Fields from which PBCore Metadata Fields were harvested
–	(see next screen)

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	The result is 249 suggested metadata fields for the PBCore as found in the Report.

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Engaged in Data Wrangling…it’s a start, but not a polished PBCore Metadata Dictionary
•	Somewhat undisciplined use of the dot.syntax
•	Free use of compliant and non-compliant Qualifiers
–	Protects the intention and meaning behind the harvested metadata fields for the Provisional PBCore Metadata Report
Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Varied interpretations of metadata mappings under Dublin Core
–	The PBCore must set usage rules
•	When describing a resource, a struggle to differentiate between the physical instantiations of the resource and its intellectual content
Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	We have generated 249 provisional metadata fields…but just what do we anticipate being the focus of the priority core?
–	For intellectual content mark up and searching?
–	For Public Broadcasting video and audio needs as exist today?
–	For facilitating distribution and network/interconnection processes?
–	Discounting other application communities (e.g., educators)?

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Which resource descriptions can be auto-generated by D.A.M. systems?
•	Which demand a manual, subjective, intellectual evaluation?

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	How to account for different instantiations of a single resource?
–	Create one record for every physical format (one-to-one relationship between a resource and its metadata record…as in Dublin Core)?
–	Site related resources in a single metadata record?
–	For example:
•	Title hierarchies (excerpt, program, series, collection, project)
•	Format variations (analog source vs digital master vs digital use copy or copies)

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Granularity vs Simplicity
–	In terms of our 249 provisional metadata fields
–	Compared to our Use Case reported needs
–	Cont’d
Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Granularity vs Simplicity
–	How to impose a granular distinctiveness to metadata elements and qualifiers when Dublin Core is geared to a more simple approach…
•	DC uses repeating elements without regard to a hierarchy
•	Should granular descriptions be placed in the “value” for a metadata field, following specific syntax rules, rather than burdening core Elements and their compliant Qualifiers?
–	For example:
–	DC.Title = National Parks of Utah
–	DC.Title.Alternative = Social Studies of Utah. Geography of Utah Series, No. 16

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Follow-up task:
Syntax-Patrol of the 249 Provisional PBCore Metadata Fields
ü	COMPLIANT: Check for compliancy with Dublin Core Elements, Qualifiers and Extensions
•	Dumb-down Principle (refining, not extending meaning by use of Qualifiers)
ü	CONSISTENT: Check for consistency in usage and assignments
ü	CONCISE: Check for conciseness and eliminate redundancies

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Follow-up task:
Construct Definitions for each Metadata Field
ü	For the Elements
ü	For the Qualifiers
ü	For the Extensions

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Follow-up task:
Develop Usage Guidelines
ü	Instructions for proper use
ü	e.g., how to construct grammatically correct “values” for a metadata field 
•	<period space> to separate value descriptors
•	<semi-colons> to separate value descriptors
ü	Comments and suggestions
ü	Examples and Samples

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Follow-up task:
Specify Element Refinements
•	Qualifiers
•	Encoding Schemes
•	Controlled Vocabularies
•	Authority Control through Authority Files
•	Standard nomenclatures
•	Use existing standards where possible
•	Embellish if absolutely needed

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Follow-up task:
Populate the fields for…
•	Data Type (alphanumeric/string, numeric, date)
•	Optional/Mandatory (necessary metadata descriptor)
•	Repeatable Field (as found in Dublin Core Scheme)

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Follow-up task:
Incorporate the Use Case Scenarios
ü	Match the needs and requirements from the Use Cases to the Metadata Fields
ü	Determine the priority Metadata Fields
ü	Target the Application Communities most likely to embrace the PBCore
ü	Apply Appropriate Schemas
•	Systematic, orderly combinations of elements using rules for encoding information that support a specific community of users

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Follow-up task:
Mark Up Tools vs Search Mechanisms
•	Differentiate between the Data Model used to accommodate Mark Up by a user with a particular indexing or D.A.M. system and the Resource Description Frameworks demanded by Dublin Core

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Follow-up task:
Determine how best to introduce the PBCore to the Public Broadcasting Application Communities
ü	What info should be shared
ü	In what form shall the info be shared (e.g., PDF, Word Processing, Spreadsheet, Database)
ü	Accommodate or discourage the “digital tourist”

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Follow-up task:
Explore Solutions to Information Exchanges: Interoperability / Crosswalks
ü	Mapping relationships and equivalencies between two or more metadata formats

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Follow-up task:
Explore Solutions to Information Exchanges: Interoperability / Crosswalks
ü	Construct the PBCore however it needs to be built, with whatever granularity is required
ü	But be sure it shares common semantic, structural and syntactic conventions for seamless exchanges of resource descriptive information

Dictionary Review Team
PBCore Metadata Provisional Recommendations
•	Follow-up task:
Engage in behavioral modification to avoid having Dublin Coronaries
ü	Reduce stress
ü	Reduce cholesterol
ü	Reduce saturated fats
ü	Reduce metadata
ü	Avoid over-qualifying
ü	K.I.S.S. without losing
meaning or intellectual
integrity