Repository navigation
Use CMR For Validation Type Checks #269
Description
The CMR Team would like to recommend that pyQuARC use the CMR API for basic validation checks (metadata schema, controlled vocabularies) rather than have a separate validation in pyQuARC. If there are changes to CMR validation, we want to ensure that users are not using outdated validation in pyQuARC. We also want to verify consistency between what results are provided to users in pyQuARC vs CMR.
Collection metadata can be validated at ingest or without having to ingest it. The validation performed is schema validation, UMM validation, and inventory specific validations. Keyword validation can be enabled with the keyword validation header. It returns status code 200 with a list of any warnings on successful validation, status code 400 with a list of validation errors on failed validation. Warnings would be returned if the ingested record passes native XML schema validation, but not UMM-C validation.
The validation API is documented at https://cmr.earthdata.nasa.gov/ingest/site/docs/ingest/api.html#collection.
Activity
tbs1979 commentedon Feb 1, 2024
https://cmr.earthdata.nasa.gov/ingest/site/docs/ingest/api.html#collection documents the CMR validation API. The wiki page UMM-C Validation in CMR lists the current collection validations done in CMR. The type of validation, whether its an error or warning, and message is documented. This is also documented in CMR Clojure code in more extensive detail.
FBayat021 commentedon Apr 29, 2025
This ticket needs to be reviewed before it's pushed to the master branch.
FBayat021 commentedon Apr 29, 2025
We need @slesaad to review the PR (#307) associated with this ticket, and if it's good to go, merge it to the master branch.
lavanya3k commentedon Jun 10, 2025
Tested on the records C1422070882-CDDIS (format umm-c), the following is the output. The cmr validation errors are in addition to the recommendation provided by the PyQuARC.
lavanya3k commentedon Oct 17, 2025
See the PR #307 and #359