Parent SERF


Definition

The <Parent_SERF> field allows the capability to relate generalized aggregated metadata records (parents) to metadata records with highly specific information (children). Population of the <Parent_SERF> field should be reserved for instances where many metadata records are basically subsets that can be better represented by one parent metadata record, which describes the entire collection. Typically, the parent metadata record will have many children metadata records, which refer to the parent through the <Parent_SERF> field. In some instances, a child may point to more than one parent. The <Parent_SERF> is populated with an <Entry_ID>. 


The <Parent_SERF> is only populated if there are children metadata records that refer to a parent metadata record.  Upon display of results, both parent and children metadata are available with explicit linkages between parent and child records through the <Parent_SERF> field.

 
Syntax

<Parent_SERF> Entry_ID </Parent_SERF>


  • The syntax of the <Parent_SERF> is identical to the <Entry_ID>. The <Parent_SERF> consists of 1 to 80 alphanumeric characters of the UTF-8 set,including underbar (_), hyphen (-) and period (.)
  • The following characters are not allowed in the <Parent_SERF>:
    • Forward Slash (/)
    • Backward Slash (\)
    • Spaces ( )
    • Colon (:)
 
Usage
  • The <Parent_SERF> field is recommended and may be repeated.
  • The <Parent_SERF> field must be populated with the existing <Entry_ID> of the parent metadata record.
  • The field may be repeated in cases where a child metadata record has two different immediate parents, i.e., the child is a member of two distinct aggregations.
 
Examples

<Parent_SERF>Natur_Haz_Center</Parent_SERF>


<Parent_SERF>USGS-GISDATA</Parent_SERF>

 

This document should be cited as:
Service Entry Resource Format (SERF) Writer's Guide, 2014.
Global Change Master Directory.
National Aeronautics and Space Administration.
[http://gcmd.nasa.gov/add/serfguide/].

NASA Logo - nasa.gov
Link to Web Site