HAPI to SPASE mapping

[rweigel]

Draft table developed by Rebecca, Zach, and Andriy.

Draft code and its configuration that implements a subset of the mapping.

[rebeccaringuette]

This comment details all the fields checked and the changes needed in the produced SPASE on the HAPI TestData servers.
Note: The https://hapi-server.org/meta/infos/TestData3.1/dataset1-A%CE%B1%E2%98%83.json link has a snowman....? Should this be removed?
Also, the directory structure of TestData3.2 is different than the others. May need to be fixed.

TestData2.0/dataset1.json

mapped concepts checked:

• info: parameter name/key, parameter units, parameter description, parameter type, start date, stop date, cadence
• catalog: title
• about: not found
• capabilities: output format
• release date, measurement type,
  problems found:

1. revision history container not created. should be under ResourceHeader:

<RevisionHistory>
  <RevisionEvent>
    <ReleaseDate>2021-04-27T15:38:11Z</ReleaseDate>
    <Note>Only known prior ReleaseDate of the metadata</Note>
  </RevisionEvent>
</RevisionHistory>

where there may be multiple RevisionEvent containers.
2. The AccessURL/Name field is populated but the about link for this server is not found (https://hapi-server.org/servers/TestData2.0/hapi/about). The value makes sense, but where did it come from? Same question for the entry in the Contact container. What is the desired behavior when no information is available?
3. Noting the second AccessInformation container, will this be done for all SPASE records drafted from HAPI?
4. Extra format values compared to the capabilities endpoint in the second AccessInformation container (png, svg, pdf).
5. Why is this link in both the AccessURL and the InformationURL fields? https://hapi-server.org/servers/#server=TestData2.0&dataset=dataset1

TestData2.x

TestData2.0/dataset2.json - same feedback as TestData2.0/dataset1. All other fields look good. No additional mapped concepts noted.
TestData2.0/dataset3.json - same feedback as TestData2.0/dataset1. All other fields look good. No additional mapped concepts noted.
TestData2.1/dataset1.json - same feedback as TestData2.0/dataset1. All other fields look good. No additional mapped concepts noted. The lists of units map correctly.

TestData3.0 - 3.2

TestData3.0/dataset1.json - same feedback as TestData2.0/dataset1, except the about endpoint is working for these and the mapped values look correct. All other fields look good. No additional mapped concepts noted.
TestData3.1/dataset1.json - same feedback as TestData3.0/dataset1. No additional mapped concepts noted.
TestData3.1/dataset2.json - same feedback as TestData3.0/dataset1. No additional mapped concepts noted.
TestData3.2/DE1/PWI/B_H.json - same feedback as TestData3.0/dataset1. No additional mapped concepts noted.

TestData3.3/dataset1.json

mapped concepts checked:

• info: parameter name/key, parameter units, parameter description, parameter type, start date, stop date, cadence, licenseURL, datasetCitation, warning
• catalog: id, title
• about: title, contact, serverCitation, warning, note
• capabilities: outputFormats
• release date, measurement type
  problems found:
• info/location has information, but is not mapped into a SpatialCoverage container in SPASE.
• info/additionalMetadata/contentURL is populated, resulting in "https://hapi-server.org/servers/#server=TestData3.3&dataset=dataset1" being the URL in two InformationURL fields.
• info/datasetCitation is populated, but not mapped to NumericalData/ResourceHeader/DOI

TestData3.3/datasets 2 and 3

TestData3.3/dataset2.json - same as for TestData3.3/dataset1.json. Additionally:

• https://hapi-server.org/servers/#server=TestData3.3&dataset=dataset1 is incorrectly included in the second InformationURL container.
• info/geolocation has information, but is not mapped into a SpatialCoverage container in SPASE.

TestData3.3/dataset3.json - same as for TestData3.3/dataset1.json. Additionally:

• only one InformationURL container is present, compared to the double approach in all the others.
• info/licenseURL is populated, but not mapped to RightsURI
• info/warning is populated, but not mapped to Caveats
• info/geolocation has information, but is not mapped into a SpatialCoverage container in SPASE.

Fields not available in these servers

• info/resourceURL
• info/additionalMetadata
• info/resourceID
• info/citation
• info/description
• info/additionalMetadata/name
• info/additionalMetadata/content
• info/additionalMetadata/schemaURL
• info/additionalMetadata/aboutURL
• about/id to AccessInformation/RepositoryID
• about/x_SPASE_PersonID