Update Schema Version

[smk0033]

pyQuARC's most recent UMM schema version is 1.18.1. Update to the most recent, which is currently 1.18.4 (automation has not been completed yet, so manually update).

[smk0033]

PR: #316

[abbottry]

Does pyQuARC assume that all records would be up to date? I'm trying to better understand the impact/expectation of updating a schema -- it seems like it should look at the defined version in the record (MetadataSpecification) and validate against that version.

[smk0033]

@abbottry correct - we manually upload the new schema version, and pyQuARC validates records against that specific version. We had a meeting a couple weeks ago and I believe @lavanya3k brought up the capability of validating against the specific version of the schema in the record, even if it isn't the most recent. The team can certainly explore that further! cc: @fb0023

[FBayat021]

@abbottry @smk0033 I think the question should be: do we want to validate the schema version against each record’s current version, or do we expect all records to conform to the most recent version? If it’s the latter, we can continue manually updating to the latest available version. Otherwise, we should ensure the library is capable of cross-checking based on each record’s current schema version.

[abbottry]

I would recommend specifying a version to CMR when pulling a record for validation, if you look https://cmr.earthdata.nasa.gov/search/site/docs/search/api.html#umm-json here in the documentation you can see that you are able to specify the version. This will ensure that every record you request will be the version you are validating against, additionally it will help prevent the time period between when CMR updates their versions and this library updates to that version.

[FBayat021]

Action items:
Discussed with @smk0033 and @lavanya3k. The goal is to have both short-term and long-term solutions planned.

• Short-term solution: Ensure checks relevant to versions 1.18.2, 1.18.3, and 1.18.4 are added so the library can cross-validate records against the schema.
• Long-term solution: Ensure the library has no dependencies and can auto-validate against future schema updates.

[lavanya3k]

Updated PR #328

[FBayat021]

@lavanya3k I created a new ticket for the change in API call here: #329
You are welcome to still implement the changes you made here and close this ticket once its testing is complete.

[lavanya3k]

Also refer to the PR #355