The SAEOSS Portal has been proposed as a system of software components functioning together as the national central earth observation geospatial repository, with a view to metadata and open geospatial API standards compliance as well as user impact maximization
The data curation user requires an automated tool to identify non-compliances in bulk metadata in terms of nature and location, irrespective of metadata underlying file format. This is key to efficient standards conformance and data curation. The metadata compliance advisor should identify, locate and highlight in detailed human-readable formats:
a. Inconsistencies
b. Incompleteness
c. Duplications
d. Incompatibilities
in single metadata documents input in the following well-known file formats:
a. XML
b. JSON
c. YAML
This tool shall allow bulk operation on the results of failed bulk metadata sub-sets from compliance evaluations generated using the Metadata Compliance Evaluator.
All three Metadata Curation Toolset components shall be appropriately integrated with the Data Back End to allow operations on all metadata records already stored therein.
Expectation:
Metadata with known non-compliance, when run through the advisor, results in the identification of the correct type of non-compliance at the correct location/field in a human readable report.
The data curation user requires an automated tool to identify non-compliances in bulk metadata in terms of nature and location, irrespective of metadata underlying file format. This is key to efficient standards conformance and data curation. The metadata compliance advisor should identify, locate and highlight in detailed human-readable formats: a. Inconsistencies b. Incompleteness c. Duplications d. Incompatibilities in single metadata documents input in the following well-known file formats: a. XML b. JSON c. YAML This tool shall allow bulk operation on the results of failed bulk metadata sub-sets from compliance evaluations generated using the Metadata Compliance Evaluator. All three Metadata Curation Toolset components shall be appropriately integrated with the Data Back End to allow operations on all metadata records already stored therein.
Expectation: Metadata with known non-compliance, when run through the advisor, results in the identification of the correct type of non-compliance at the correct location/field in a human readable report.