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
To enable metadata.json downloads by dataset in the Portal UI we need an endpoint- /prov-metadata/ that will output the json for the full provenance metadata containing the same data and formatted as produced for the metadata.json files generated at publication time (could be used to implement Update metadata generation...
This endpoint should optionally take a token where:
if a token isn't valid return a 401
if there is a valid token, but it isn't a member of the HuBMAP - Read group, only provide data for Published Datasets. Otherwise if not a member of HuBMAP - Read and requested information for a non-published dataset return a 403 or 404 if a dataset doesn't exist.
if there is a valid token and the user is a member of HuBMAP - Read provide access to any dataset but, even though the user has access, still exclude the fields as specified in the prov schema yaml per Exclude fields from public ...-- (we never want to provide these excluded fields in this metadata.json format). If a dataset doesn't exist return a 404
if there is no token only return data for non-published datasets, otherwise 403 if a dataset isn't published or 404 if a dataset doesn't exist
The text was updated successfully, but these errors were encountered:
To enable metadata.json downloads by dataset in the Portal UI we need an endpoint- /prov-metadata/ that will output the json for the full provenance metadata containing the same data and formatted as produced for the metadata.json files generated at publication time (could be used to implement Update metadata generation...
This endpoint should optionally take a token where:
The text was updated successfully, but these errors were encountered: