Create a validation file to check if record meets GBL community standards

[rmseifried]

To be done once #24 is completed

Issue

There are JSON schema files in the geoblacklight repo that are used to validate individual metadata records and ensure that the data types are correct. It would be helpful for users to also be able to validate the presence of required fields and community standard fields (as determined based on the review in #24).

Suggested solution

See if the JSON schema offers a way to flag fields as required.

• If yes, update the existing schema files
• If not, create new schema files for the required and community standard lists

[kgjenkins]

Yes, JSON Schema lets you specify which properties are required, and in fact we already have that set up in geoblacklight-schema-aardvark.json:

"required": ["id", "dct_title_s", "gbl_resourceClass_sm", "dct_accessRights_s", "gbl_mdVersion_s"]

[kgjenkins]

To check that an Aardvark record complies with a community-level minimum (beyond the absolute minimum), I think we'll want to set up a 2nd JSON Schema that requires the additional properties, and perhaps also applies further checks on the property values (like dates, etc.)

[rmseifried]

Yes, JSON Schema lets you specify which properties are required, and in fact we already have that set up in geoblacklight-schema-aardvark.json:

"required": ["id", "dct_title_s", "gbl_resourceClass_sm", "dct_accessRights_s", "gbl_mdVersion_s"]

Just noticed the "required" list is missing gbl_mdModified_dt, which is now listed as a required field in the OGM documntation.

[rmseifried]

1. We changed the obligations as part of the summer 2025 sprint, see the current obligations on the OGM Aardvark page
2. Discussion from the sprint: could the validator give a score?