entity rule change

[stansmith907]

New elements for entity:

• entityReference [{citation}]: "reference to a standard or external schema which describes the entity"
• fieldSeparatorCharacter {character}: "the character which indicates the end of the data field contents"
• numberOfHeaderLines {integer}: "the number of lines at the beginning of the file before the data content actually begins"
• quoteCharacter {string}: "Character used to quote fields in the data representation so that the field delimiter can be used as part of the field value. This character is typically a single quote mark or double quote mark."

Rules:

• [x] entityReference array, optional
• [x] fieldSeparatorCharacter optional
• [x] numberOfHeaderLines optional
• [x] quoteCharacter optional

mdJson:

{
   "entity": [
      {
         "entityId": "",
         "commonName": "",
         "codeName": "",
         "alias": [],
         "definition": "",
         "entityReference": [],
         "primaryKeyAttributeCodeName": [],
         "index": [],
         "attribute": [],
         "foreignKey": [],
         "fieldSeparatorCharacter": ["x" , "tab"],
         "numberOfHeaderLines": 9,
         "quoteCharacter": ""
      }
   ]
}

FGDC mapping to distribution section The items cannot be mapped from FGDC to mdTranslator because the Bio extension defines the entity structure inside distribution transfer option, outside of the FGDC entity section. I cannot reliably merge the two entity descriptions. However, I have added the Bio extension elements to mdTranslator and mdJson entity object. Further, the fieldSeparatorCharacter cannot be mapped from FGDC since it is associated at the attribute level rather than the entity.

<metadata>
  <distinfo>
    <stdorder>
      <nondig>option for obtaining non-digital data 1</nondig>
      <digform>
        <digtinfo>
          <asciistr>
            <recdel>\n</recdel>
            <numheadl>1</numheadl>
            <deschead>column names</deschead>
            <orienta>columnmajor</orienta>
            <casesens>N</casesens>
            <authent>12ad155ee845d5c4</authent>
            <quotech>"'"</quotech>
            <datafiel>
              <dfieldnm>field1</dfieldnm>
              <missingv>-1</missingv>
              <dfwidth>12</dfwidth>
              <dfwidthd>tab</dfwidthd>
            </datafiel>
            <datafiel>
              <dfieldnm>field2</dfieldnm>
              <missingv>-1</missingv>
              <dfwidthd>;</dfwidthd>
            </datafiel>
          </asciistr>
        </digtinfo>
      </digform>
    </stdorder>
  </distinfo>
</metadata>

FGDC mapping to entity attribute information section - entity overview entityReference is mapped to/from 'entity-attribute detail citation eadetcit.

<metadata>
  <eainfo>
    <overview>
      <eaover>entity and attribute overview 1</eaover>
      <eadetcit>entity and attribute citation 1</eadetcit>
      <eadetcit>entity and attribute citation 2</eadetcit>
    </overview>
  </eainfo>
</metadata>

ISO 19110-2 mapping: The entityReference will be placed in an entity section (featureType) as follows:

<gfc:featureType>
  <gfc:FC_FeatureType id="entity_001">
    <gfc:typeName>
      <gco:LocalName>agency</gco:LocalName>
    </gfc:typeName>
    <gfc:definition>
      <gco:CharacterString>Organizations providing...</gco:CharacterString>
    </gfc:definition>
    <gfc:code>
      <gco:CharacterString>AGENCY</gco:CharacterString>
    </gfc:code>
    <gfc:isAbstract>
      <gco:Boolean>false</gco:Boolean>
    </gfc:isAbstract>
    <gfc:definitionReference>
      <gfc:FC_DefinitionReference>
        <gfc:definitionSource>
          <gfc:FC_DefinitionSource>
            <gfc:source>
              <gmd:CI_Citation>
                <gmd:title>title</gmd:title>
                <gmd:date></gmd:date>
              </gmd:CI_Citation>
            </gfc:source>
          </gfc:FC_DefinitionSource>
        </gfc:definitionSource>
      </gfc:FC_DefinitionReference>
    </gfc:definitionReference>
  </gfc:FC_FeatureType>
</gfc:featureType>