You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 theRequestReport
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 usinghashstore
to access the information needed to complete the check (similarly to how thedata.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.
The text was updated successfully, but these errors were encountered: