pbcorePart is an element that may be used to split up a single asset so as to enable the use of all available elements at the pbcoreDescriptionDocument level to describe the intellectual content of individual segments of an asset.

Best practice: Splitting up an asset in this way allows for defining and describing segments, stories, episodes or other divisions within the asset, such as individual films in a compilation reel, or distinct segments of a news show when each may have their own titles, creators, publishers, or other specific intellectual content information that does not apply across the whole asset.

pbcorePart can be contained by the elements pbcoreDescriptionDocument or pbcorePart.

Usage: optional, repeatable.

Attributes

• partType– optional. The partType attribute is used to indicate the nature of the part into which the asset has been divided. Can be used as an attribute of the pbcorePart element.
• partTypeSource – optional. The partTypeSource provides the name of the authority used to declare data value of the attribute partType. Best practice: This might be the name of a controlled vocabulary, namespace or authority list, such as the official PBCore recommended vocabulary. Can be used as an attribute of the pbcorePart element.
• partTypeRef – optional. The partTypeRef attribute is used to supply a source’s URI for the value of the attribute partType. Best practice: Attribute partTypeRef can be used to point to a term in a controlled vocabulary, or a URI associated with a source. Can be used as an attribute of the pbcorePart element.
• partTypeVersion – optional. The partTypeAnnotation attribute includes narrative information intended to clarify the nature of data used in the attribute partType. Best practice: This attribute can be used as a notes field to include any additional information about the element or associated attributes. Can be used as an attribute of the pbcorePart element.
• partTypeAnnotation – optional. The partTypeVersion attribute is used to identify any version information about the authority or convention used to express data of the attribute partType. Can be used as an attribute of the pbcorePart element.
• startTime – optional. The startTime attribute combines with the endTime attribute to define a specific media segment within a broader timeline of an asset and/or instantiation. Used to talk generally about the start/end time of a segment (e.g. “30 minutes”), or by providing a timestamp to a specific point in an instantiation. If you’re doing that for element at the asset level, we suggest referencing the instantiation ID you are referring to in timeAnnotation. One example would be if a six-hour long tape was broken into multiple programs, and each instantiation might have its start time labeled as when the instantiation began in the timeline of the broader tape. Another example for this usage might be a digital file created from a VHS tape that contains multiple segments. In the digital copy, color bars are removed from the beginning, and black from the end of the digital instantiation. Time references referring to the segments on the physical VHS are no longer relevant; therefore it’s important to tie start and end time references to a specific instantiation, e.g. use the asset ID and timestamp.
• endTime – optional. The endTime attribute combines with a similar value in the startTime attribute to define a specific media segment within a broader timeline of an asset and/or instantiation.
• timeAnnotation – optional. The timeAnnotation attribute includes narrative information intended to clarify information about the value of the startTime and endTime attributes.

Subelements

• pbcoreAssetType – optional. A broad definition of the type of intellectual content being described. Asset types might include those without associated instantiations (a collection or series), or those with instantiations (programs, episodes, clips, etc.)
• pbcoreAssetDate – optional. The pbcoreAssetDate is intended to reflect dates associated with the Intellectual Content.
• pbcoreIdentifier – required. An identifier that can apply to the asset. This identifier should not be limited to a specific instantiation, but rather all instantiations of an asset. It can also hold a URL or URI that points to the asset.
• pbcoreTitle – required. The pbcoreTitle is a name or label relevant to the asset.
• pbcoreSubject – optional. The pbcoreSubject is used to assign topic headings or keywords that portray the intellectual content of the asset. A subject is expressed by keywords, key phrases, or even specific classification codes. Controlled vocabularies, authorities, formal classification codes, as well as folksonomies and user-generated tags, may be employed when assigning descriptive subject terms.
• pbcoreDescription – required. The pbcoreDescription element uses free-form text or a narrative to report general notes, abstracts, or summaries about the intellectual content of an asset. The information may be in the form of an individual program description, anecdotal interpretations, or brief content reviews. The description may also consist of outlines, lists, bullet points, rundowns, edit decision lists, indexes, or tables of content.
• pbcoreGenre – optional. This element describes the Genre of the asset, which can be defined as a categorical description informed by the topical nature or a particular style or form of the content.
• pbcoreRelation – optional. This element contains the pbcoreRelationType and pbcoreRelationIdentifier elements. In order to properly use these two elements they must be nested with the pbcoreRelation element, and pbcoreRelation must contain both pbcoreRelationType and pbcoreRelationIdentifier if it is included.
• pbcoreCoverage – optional. The pbcoreCoverage element is a container for subelements coverage and coverageType.
• pbcoreAudienceLevel – optional. The element pbcoreAudienceLevel identifies a type of audience, viewer, or listener for whom the media item is primarily designed or educationally useful.
• pbcoreAudienceRating – optional. The element pbcoreAudienceRating designates the type of users for whom the intellectual content of a media item is intended or judged appropriate. This element differs from the element pbcoreAudienceLevel in that it utilizes standard ratings that have been crafted by the broadcast television and film industries and that are used as flags for audience or age-appropriate materials.
• pbcoreCreator – optional. The pbcoreCreator element is a container for sub-elements creator and creatorRole.
• pbcoreContributor – optional. The pbcoreContributor element is a container for sub-elements contributor and contributorRole.
• pbcorePublisher – optional. The pbcorePublisher element is a container for sub-elements publisher and publisherRole.
• pbcoreRightsSummary – optional. The element pbcoreRightsSummary is a container for sub-elements ‘rightsSummary’, ‘rightsLink’ and ‘rightsEmbedded’ used to describe Rights for the asset.
• pbcoreInstantiation – optional. This element contains subelements that describe a single instantiation of an asset. The definition is malleable but it should be thought of as any discreet and tangible unit that typically (though not always) comprises a whole representation of the asset. For example, an original master videotape, a preservation master video file, and a low-bitrate access copy would all be considered Instantiations of a single video program. All of the sub-elements held by this element are used to describe the intantiation specifically, not necessarily the asset as a whole.
• pbcoreAnnotation – optional. The element pbcoreAnnotation allows the addition of any supplementary information about the metadata used to describe the PBCore record. pbcoreAnnotation clarifies element values, terms, descriptors, and vocabularies that may not be otherwise sufficiently understood.
• pbcorePart – optional. The pbcorePart element may be used to split up a single asset so as to enable the use of all available elements at the pbcoreDescriptionDocument level to describe the intellectual content of individual segments of an asset.
• pbcoreExtension – optional. Extensions are either a wrapper containing a specific element from another standard OR embedded xml containing the extension.

Examples

Submit any issues or suggested changes for future schema iterations by creating a ticket in our Github repository.