Context
List
of Sample PBCore Metadata Records
CONTEXT:
In our PBCore User Guide, the Full Documentation and Cheat Sheet Documentation for the PBCore metadata elements provide numerous examples of descriptions and data entries. These examples are viewed on an element-by-element basis. We are also providing sample metadata as complete metadata descriptions on a record-by-record basis in which all the PBCore elements are populated with descriptive data for a given media item or object.
Accordingly, from the listings below, you can select sample records of descriptions (using PBCore). These sample records are catalog different media types and variations on "repeating elements and containers" (see the FYI below for an explanation).
Admittedly, these Sample Metadata Records simply complete each metadata field with compliant PBCore terms, values, and descriptions. How complete records are actually implemented in traffic, scheduling, archive, DAM, VOD, and other information systems is more about database design and information architecture, e.g., relational tables within databases and XML Stylesheets used for the import and export of data. Obviously, we cannot predict the variations that are occurring across all the users of PBCore. However, we do have summaries of planned and engaged uses of PBCore in real-world venues on our website page PBCore Case Examples, where you will find well over a dozen cases.
Some users have asked about creating Application Specific Profiles for PBCore, in which customized sets of PBCore element definitions, data-entry rules, and terms can be supplied. For example, radio-only users may be more comfortable using specific nomenclatures and asset identification tags that are wildly different than those embraced by their television colleagues (where NOLA codes are still in use to identify individual assets). We suggest that users interested in Application Specific Profiles join the PBCore User Group Community and share their needs and experiences.
FYI ON WHAT YOU WILL SEE IN THE SAMPLE RECORDS...
PBCore structures its Metadata Elements in hierarchies and binds related elements inside of parent Containers. In a few cases, a Container holds Sub-Containers, which themselves hold the Metadata Elements. The name of each Container, Sub-Container, and Metadata Element shown in each of our Sample Metadata Records is an active hyperlink to a web page in the PBCore User Guide that explains and defines the nature of these individual PBCore components.
All PBCore metadata elements are thematically grouped into four classes: Intellectual Content, Intellectual Property, Instantiations, and Extensions. Learn more at our page about Content Classes in PBCore.
For a graphical view of the hierarchical structure of PBCore elements, visit our pages showing an Illustration of the Hierarchies and a discussion on Flat vs Hierarchical Relationships & Interdependencies.
Containers and Sub-Containers can be repeated if there are multiple instances of metadata descriptions. For example, if there are multiple renditions or media formats for a single asset, then the container pbcoreInstantiation (with its metadata elements) is repeated for each rendition; on the other hand, the Intellectual Content for the entire asset is only entered once within a single metadata record for the entire asset and all of its multiple renditions. Likewise, if an asset has descriptions for both Temporal Coverage and Spatial Coverage, then the container pbcoreCoverage is repeated in order to enter the keywords for each type of coverage.
Wherever there is a Container, it can be repeated with different values for the metadata elements it holds. Learn more at our page about repeating Element Containers in PBCore. We provide examples of repeating containers throughout our Sample PBCore Metadata Records.
Each metadata element in our Sample Metadata Records is also marked by its obligation to use: Mandatory, Mandatory if Applicable, Recommended, and Optional. Learn more at our page about PBCore Elements Viewed by Obligation to Use.
Every Sample Metadata Record provides a link to a complete XML version of the descriptions, in accordance with the PBCore XSD (XML Schema Definition).
SAMPLE PBCORE METADATA RECORDS
:
(showing media types and variations on repeating elements within their containers)
|
#01
Moving image--
as a single physical videotape
|
This record is an example of a media asset that has a single physical instantiation, a videotape in the Beta SP format. The container pbcoreCoverage repeats, once for Spatial Coverage and once for Temporal Coverage. |
|
|
|
|
#02
Moving image--
as a physical videotape with two digital movie files |
This record is an example of a media asset that has multiple instantiations, both physical videotape and digital video files for VOD web services. QuickTime and Windows Media renditions are described by repeating the pbcoreInstantiation container with all the format elements and its 3 sub-containers. |
|
|
|
|
#03
Sound--
as a single digital audio file, with an associated transcript
|
This record is an example of a media asset that is a single digital audio instantiation, but with an accompanying transcript in a PDF format. In this metadata record, the PDF is treated as a second instantiation of the same intellectual content. |
|
|
|
|
#04
Static Image--
photograph of a folk artist linked to other records showing his works |
There are three related metadata records. Sample Record #04 describes a photograph of a folk artist. This metadata record uses the pbcoreRelation container to link the artist to photographs of two of his actual works (see Sample Records #05 and #06). Likewise, the records for the actual works use the pbcoreRelation container to link back to the artist's photograph (Sample Record #04) and the related companion art work.
The pbcoreDescription container is repeated in each record in order to distinguish information about an individual art work (abstract) and anecdotal insights made about the work or artist by an art historian (anecdotal).
These records are part of a larger collection. The metadata schema in use by the cataloging institution employs other metadata fields to identify collection-level information. These are found as extensions to PBCore. |
|
#05
Static Image--
photograph of a folk art carving linked to other records showing the artist and additional works |
|
#06
Static Image--
photograph of a folk art carving linked to other records showing the artist and additional works |
|
|
|
|
#07
Moving Image--
digital video with 3 related segments
|
In this group of related metadata records, there is a full-length digital video file posted to an online VOD system. K-12 schools and higher education institutions have access to not only the full-length version, but also any of three shorter length segments derived from the parent asset.
Record #07: Full-length program-Utah Landforms
Record #08: Segment 1-The Colorado Plateau
Record #09: Segment 2-The Rocky Mountains
Record #10: Segment 3-The Great Basin
The three shorter segments have their own unique intellectual content descriptions when compared to the parent asset. Therefore, all four assets (full-length + 3 segments) are captured in 4 separate metadata records in PBCore.
Each is linked to the others (parent and sibling) by repeating the container PBCoreRelation and identifying each file by a unique identifier within the VOD system.
Each asset also exists as two renditions; the container pbcoreInstantiation is repeated in order to capture the format information for both QuickTime and WindowsMedia versions.
Because these digital videos are intended for distribution to K-12 as well as higher education, state core curriculum standards (for Utah) and targeted academic disciplines (higher ed) are captured in extensions to PBCore.
Additional rights management metadata fields are also added as extensions to PBCore, although the discrete fields are concatenated into a (PBCore compliant) combined statement for the pbcoreRightsSummary data field. |
|
#08
Moving Image--segment
drawn from full-length video
|
|
#09
Moving Image--segment
drawn from full-length video
|
|
#10
Moving Image--segment
drawn from full-length video
|
|
|
|
|
#11
(pending submission) |
[comments] |
|
|
|
|
#12
(pending submission)
|
[comments] |
|
|
|
|
#13
(pending submission) |
[comments] |
|
|
|
|
#14
(pending submission) |
[comments] |
|
|
|
|
#15
(pending submission) |
[comments] |
|
|
|
|
#16
(pending submission) |
[comments] |
|
|
|
|
#17
(pending submission) |
[comments] |
|
|
|
|
#18
(pending submission) |
[comments] |
|
|
|
