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
Jonathan has requested that the full provenance metadata information be included in the metadata.tsv files that are currently being generated (which only include the actual data metadata that we obtain during dataset ingest).
Both for the endpoint that will generate a metadata.tsv file for a dataset and a publication time change the contents of the metadata.tsv file to include the full json response of the entity-api /entities/<dataset id> endpoint and add to that lists of the full response all associated donors, organs and samples. See example cypher below to obtain the uuids of these associated entities, then make calls to the entity-api /entities/<entity id> endpoint to get the json for inclusion in the list of each type.
Jonathan has requested that the full provenance metadata information be included in the metadata.tsv files that are currently being generated (which only include the actual data metadata that we obtain during dataset ingest).
Both for the endpoint that will generate a metadata.tsv file for a dataset and a publication time change the contents of the metadata.tsv file to include the full json response of the entity-api
/entities/<dataset id>
endpoint and add to that lists of the full response all associated donors, organs and samples. See example cypher below to obtain the uuids of these associated entities, then make calls to the entity-api/entities/<entity id>
endpoint to get the json for inclusion in the list of each type.Related to hubmapconsortium/ingest-api#411
The text was updated successfully, but these errors were encountered: