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
The Provenance Section on portal-ui's individual entity page displays the sequence of events and actions that led to the creation of a given entity, which uses the /entities/<id>/provenance call essentially. Based on feedback from Harvard team, they'll only need the following fields:
hubmap:creation_action
hubmap:uuid
hubmap:status (code indicates this exists, but haven’t been able to inspect live data with this field included)
hubmap:created_timestamp
wasGeneratedBy
prov:activity
prov:entity
Previously we did performance tuning with using Neo4j query to return the results, without going through the schema yaml. This exclusion operation should be handled in the Neo4j cypher as well if possible.
The Provenance Section on portal-ui's individual entity page displays the sequence of events and actions that led to the creation of a given entity, which uses the
/entities/<id>/provenance
call essentially. Based on feedback from Harvard team, they'll only need the following fields:entity
activity
Previously we did performance tuning with using Neo4j query to return the results, without going through the schema yaml. This exclusion operation should be handled in the Neo4j cypher as well if possible.
entity-api/src/app_neo4j_queries.py
Line 572 in a70dd1f
The text was updated successfully, but these errors were encountered: