Return to Listing of Content Classes
CONTENT CLASS 05: RELATIONSHIPS
(definitions and guidelines for individual elements listed
by logical groupings--"Content Classes")
ADMIN & EMEDIA LABELS |
METADATA DESCRIPTORS |
METADATA ATTRIBUTES |
|
|
|
|
The metadata elements clustered under Relationships identify media items of similar intellectual content to the asset management record currently being browsed. Related media items fall into four groups: 1. Suggested Related Media 2. Is part of (parent relationship) 3. Is related to these parts (sibling relationship) 4. Has these parts (child relationship) In each case, the four related groups exist as "Container" fields in Telescope. Only items and records internal to Telescope can be added to a Container Field. A related media item that is physically held external to Telescope cannot be added to a Container Field...but the record describing the external, physical media item could be. If it cannot, then the search that is conducted by the end user in order to discover media items on a certain subject will result in a list of externally held, physical media items. If a media item is simply a different file format of exactly the same content as another media item, then, according to Telescope protocols, the assets are considered "renditions" of the same metadata record. For example, a transcript in PDF form is another rendition of a video clip. |
|
Similar media items [eMedia] Similar media items |
|
[for publication] |
|
|
SUGGESTED RELATED MEDIA identifies media items of similar intellectual content to the asset management record currently being browsed. Specifically, SUGGESTED RELATED MEDIA refers to other media types or items that do not exhibit parental, sibling, or child relationships to the main media item being viewed. For example, an image of an art work may be related to a completely independent manuscript about the artist (if the catalogers deem the relationship to be overwhelmingly informative). |
|
Think of SUGGESTED RELATED MEDIA as additional title recommendations that Amazon.com or Barnes & Noble.com offer when you select a particular book or title to investigate. Because this is a "Telescope container field," only digital assets internal to the DAM system can be referenced here. Physical assets cannot be included, except for their metadata records. NOTE: The umap_title_contextual metadata field (based on a functional rule that harvests its contents from other contextual title fields) may contains similar references. However, the contextual title field only names the related assets; it does not provide any sort of hyper-linking that allows previewing or review of metadata information. |
|
|
container |
|
NA |
|
NA |
|
NA |
|
If a media item is simply a different file format of exactly the same content as another media item, then, according to Telescope protocols, the assets are considered "renditions" of the same metadata record. For example, a transcript in PDF form is another rendition of a video clip. For this example, the PDF rendition would NOT be entereed as SUGGESTED RELATED MEDIA. Because this is a "Telescope container field," only digital assets internal to the DAM system can be referenced here. Physical assets cannot be included, except for their metadata records. NOTE: The umap_title_contextual metadata field (based on a functional rule that harvests its contents from other contextual title fields) may contains similar references. However, the contextual title field only names the related assets; it does not provide any sort of hyper-linking that allows previewing or review of metadata information. |
|
NA |
|
NA |
|
NA |
|
|
Being a "Container" field, it is not possible to provide textual examples. |
|
|
Suggested related media |
|
Suggested related media |
|
|
|
|
|
|
|
|
No equivalent, although the "title relationships" of a media item to its parent media (collections, projects, packages, series, etc.) are named in the umap_title_contextual metadata field. Its functional rule tests for data and combines into a single statement these subfields: umap_title_context_collection umap_title_context_project umap_title_context_package umap_title_context_series umap_title_context_program umap_title_context_episode umap_title_context_segment umap_title_context_periodical umap_title_context_book umap_title_context_issue umap_title_context_chapter umap_title_context_article umap_title_context_selection umap_title_context_excerpt umap_title_context_URL umap_title |
|
|
|
|
|
|
|
|
The Admin override was "Int Any and All Related Assets" and is changed to "Suggested related media" The original database field name could be retained, although it is a bit awkward in UMAP2's definitions. It is a container field. Change the column name to rel_suggested_related_media |
|
Is part of [eMedia] Is part of |
|
[for publication] |
|
|
IS PART OF identifies the parent media item from which the record currently being browsed was drawn or harvested. For example, this metadata field would identify the full video program from which a segment or excerpt was taken. Likewise, this metadata field would identify the full digital manuscript from which a chapter or section was taken. |
|
Because this is a "Telescope container field," only digital assets internal to the DAM system can be referenced here. Physical assets cannot be included, except for their metadata records. NOTE: The umap_title_contextual metadata field (based on a functional rule that harvests its contents from other contextual title fields) may contains similar references. However, the contextual title field only names the related assets; it does not provide any sort of hyper-linking that allows previewing or review of metadata information. |
|
|
container |
|
NA |
|
NA |
|
NA |
|
Because this is a "Telescope container field," only digital assets internal to the DAM system can be referenced here. Physical assets cannot be included, except for their metadata records. NOTE: The umap_title_contextual metadata field (based on a functional rule that harvests its contents from other contextual title fields) may contains similar references. However, the contextual title field only names the related assets; it does not provide any sort of hyper-linking that allows previewing or review of metadata information. |
|
NA |
|
NA |
|
NA |
|
|
Being a "Container" field, it is not possible to provide textual examples. |
|
|
Is part of |
|
Is part of |
|
|
|
|
|
|
|
|
No equivalent, although the "title relationships" of a media item to its parent media (collections, projects, packages, series, etc.) are named in the umap_title_contextual metadata field. Its functional rule tests for data and combines into a single statement these subfields: umap_title_context_collection umap_title_context_project umap_title_context_package umap_title_context_series umap_title_context_program umap_title_context_episode umap_title_context_segment umap_title_context_periodical umap_title_context_book umap_title_context_issue umap_title_context_chapter umap_title_context_article umap_title_context_selection umap_title_context_excerpt umap_title_context_URL umap_title |
|
|
|
|
|
|
|
|
The Admin override was "Internal Parent Related Assets" and is changed to "Is part of". The eMedia override was "Part of" and is changed to "Is part of" Remove cascade visibility to UMAP1: related_asset_int_defined. It is a container field. Change the column name to rel_related_asset_parent. |
|
Is related to these parts [eMedia] Is related to these parts |
|
[for publication] |
|
|
IS RELATED TO THESE PARTS identifies the sibling media items for the record currently being browsed. If multiple segments were taken from a full video program, then the companion, related segments would be listed here. Likewise, if a collection of images was drawn from a unified set of images, then the companion, related images would be listed here. |
|
Because this is a "Telescope container field," only digital assets internal to the DAM system can be referenced here. Physical assets cannot be included, except for their metadata records. NOTE: The umap_title_contextual metadata field (based on a functional rule that harvests its contents from other contextual title fields) may contains similar references. However, the contextual title field only names the related assets; it does not provide any sort of hyper-linking that allows previewing or review of metadata information. |
|
|
container |
|
NA |
|
NA |
|
NA |
|
Because this is a "Telescope container field," only digital assets internal to the DAM system can be referenced here. Physical assets cannot be included, except for their metadata records. NOTE: The umap_title_contextual metadata field (based on a functional rule that harvests its contents from other contextual title fields) may contains similar references. However, the contextual title field only names the related assets; it does not provide any sort of hyper-linking that allows previewing or review of metadata information. |
|
NA |
|
NA |
|
NA |
|
|
Being a "Container" field, it is not possible to provide textual examples. |
|
|
Is related to these parts |
|
Is related to these parts |
|
|
|
|
|
|
|
|
No equivalent, although the "title relationships" of a media item to its parent media (collections, projects, packages, series, etc.) are named in the umap_title_contextual metadata field. Its functional rule tests for data and combines into a single statement these subfields: umap_title_context_collection umap_title_context_project umap_title_context_package umap_title_context_series umap_title_context_program umap_title_context_episode umap_title_context_segment umap_title_context_periodical umap_title_context_book umap_title_context_issue umap_title_context_chapter umap_title_context_article umap_title_context_selection umap_title_context_excerpt umap_title_context_URL umap_title |
|
|
|
|
|
|
|
|
The Admin override was "Internal Sibling Related Asset" and is changed to "Is related to these parts". The eMedia override was "Related Segments(s)" and is changed to "Is related to these parts" Remove cascade visibility to UMAP1: related_asset_int_defined. It is a container field. Change the column name to rel_related_asset_sibling. |
|
Has these parts [eMedia] Has these parts |
|
[for publication] |
|
|
HAS THESE PARTS identifies the child media items for the record currently being browsed. If a full length video program was broken up into individual, self-contained segments, then those shorter video segments would be listed here. Likewise, if a group of images were extracted from a complete photo set, then the individual, self-contained images would be listed here. |
|
Because this is a "Telescope container field," only digital assets internal to the DAM system can be referenced here. Physical assets cannot be included, except for their metadata records. NOTE: The umap_title_contextual metadata field (based on a functional rule that harvests its contents from other contextual title fields) may contains similar references. However, the contextual title field only names the related assets; it does not provide any sort of hyper-linking that allows previewing or review of metadata information. |
|
|
container |
|
NA |
|
NA |
|
NA |
|
Because this is a "Telescope container field," only digital assets internal to the DAM system can be referenced here. Physical assets cannot be included, except for their metadata records. NOTE: The umap_title_contextual metadata field (based on a functional rule that harvests its contents from other contextual title fields) may contains similar references. However, the contextual title field only names the related assets; it does not provide any sort of hyper-linking that allows previewing or review of metadata information. |
|
NA |
|
NA |
|
NA |
|
|
Being a "Container" field, it is not possible to provide textual examples. |
|
|
Has these parts |
|
Has these parts |
|
|
|
|
|
|
|
|
No equivalent, although the "title relationships" of a media item to its parent media (collections, projects, packages, series, etc.) are named in the umap_title_contextual metadata field. Its functional rule tests for data and combines into a single statement these subfields: umap_title_context_collection umap_title_context_project umap_title_context_package umap_title_context_series umap_title_context_program umap_title_context_episode umap_title_context_segment umap_title_context_periodical umap_title_context_book umap_title_context_issue umap_title_context_chapter umap_title_context_article umap_title_context_selection umap_title_context_excerpt umap_title_context_URL umap_title |
|
|
|
|
|
|
|
|
The Admin override was "Internal Child Related Assets" and is changed to "Has these parts". The eMedia override was "Segment(s)" and is changed to "Has these parts" Remove cascade visibility to UMAP1: related_asset_int_defined. It is a container field. Change the column name to rel_related_asset_child. |
