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

Metadata quality checks not running for private datasets #456

Open
doulikecookiedough opened this issue Jan 7, 2025 · 0 comments
Open

Comments

@doulikecookiedough
Copy link

When private datasets are uploaded, metadig should be performing the appropriate quality checks associated with the host repository. Currently, metadig attempts to access system metadata through the RequestReport submission process, but fails on private datasets due to insufficient permissions with API calls.

This process to access system metadata or data objects should not be part of the report requesting process with the new hashstore integration. These requirements should be performed by the metadig quality checks themselves which should be using hashstore to access the information needed to complete the check (similarly to how the data.suite checks are executed).

Refactor the metadig-engine and its related classes to remove the requirement of calling the API for system metadata and data objects.

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

No branches or pull requests

1 participant