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

Endpoint to output exact metadata contents as Published metadata.json files #766

Open
shirey opened this issue Nov 25, 2024 · 0 comments
Open
Assignees

Comments

@shirey
Copy link
Member

shirey commented Nov 25, 2024

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

3 participants