Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation on Glider DAC Compliance Checker workflow #224

Open
kerfoot opened this issue May 5, 2023 · 3 comments
Open

Documentation on Glider DAC Compliance Checker workflow #224

kerfoot opened this issue May 5, 2023 · 3 comments

Comments

@kerfoot
Copy link
Contributor

kerfoot commented May 5, 2023

Documentation of how and when the compliance checks run and make the results of the compliance check available via an API. This will allow administrators and data providers to receive feedback on the status of data sets and why they may not be available for NCEI archive.

@benjwadams
Copy link
Contributor

How would we like to have the Compliance Check results appear? Similar to what's in compliance checker web?

@DonaldMoretti DonaldMoretti transferred this issue from ioos/ioosngdac Aug 15, 2023
@benjwadams
Copy link
Contributor

benjwadams commented May 9, 2024

As I recall, compliance checks are run upon marking deployments as complete and ready for archival, provided there are actual files present.
I will verify this.

EDIT: Compliance check runs can be queued any time a deployment is saved (e.g. detected with watchdog script), not just on completion and marked ready for archival.

Compliance check results are stored in a JSON field within the database.

@benjwadams
Copy link
Contributor

We also have logic for sending emails for the compliance check reports. It's currently unused, but could be easily reactivated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants