adiwg / mdJson-schemas

JSON schemas, examples, and templates for ADIwg metadata standards
http://www.adiwg.org/projects/
GNU Lesser General Public License v3.0
18 stars 15 forks source link

source rule change #174

Closed stansmith907 closed 6 years ago

stansmith907 commented 6 years ago

New element for source: This is needed to link FGDC's normalized array of data sources with their respective process steps. Similar to ADIwg contactId.

Rules:

mdJson:

{
   "source": [
      {
         "sourceId": "",
         "description": "",
         "sourceCitation": {},
         "metadataCitation": [],
         "spatialResolution": {},
         "referenceSystem": {},
         "sourceProcessStep": [],
         "scope": {}
      }
   ]
}

ISO 19115 mapping: Does not map to ISO 19115.

FGDC mapping:

<metadata>
  <dataqual>
    <lineage>
      <srcinfo>
        <srccitea>sourceId</srccitea>
      </srcinfo>
    </lineage>
  </dataqual>
</metadata>
jlblcc commented 6 years ago

Can you confirm that description is required?

stansmith907 commented 6 years ago

Tricky. The rule is that description is required if scope is not present; and scope is required if description is not present. We have never made much use of scope so I made description required to avoid validation errors. If you want, we can adjust the schema to require one or the other (both are good OK too).

jlblcc commented 6 years ago

:ok: Working on improving lineage support in mdEditor right now, which is why this came up...

jlblcc commented 6 years ago

The rule is that description is required if scope is not present; and scope is required if description is not present.

This is already implemented, see: https://mdtools.adiwg.org/#viewer-page?v=2-2-0-4-0-7-0

jlblcc commented 6 years ago

BTW, I indicate that description is required in the editor.

stansmith907 commented 6 years ago

That works. Patched now.