sennetconsortium / entity-api

A set of web service calls to return information about SenNet entities
MIT License
0 stars 0 forks source link

Provenance entity constraints #21

Closed shirey closed 1 year ago

shirey commented 1 year ago

The working set of constraints for provenance hierarchy (this needs to be reviewed by domain experts) are given by the following allowed direct ancestor links:

   Source-->organ
   organ-->block
   block-->section
   section-->suspension
   block-->block
   block-->suspension
   section-->Dataset
   suspension-->Dataset
   Dataset-->Dataset
   block-->Dataset where type of Dataset must be Lightsheet (additional datatypes may be added in future)
   organ-->suspension where type of organ must by blood
maxsibilla commented 1 year ago

@shirey Can a Dataset have another Dataset as an ancestor?

shirey commented 1 year ago

@maxsibilla Yes, absolutely-- I'll add Dataset --> Dataset above..

shirey commented 1 year ago

We will allow block-->Dataset because assays like Lightsheet work directly on a block.

sam-dev789 commented 1 year ago

Refactored duplicate keys

Source-->[organ] organ-->[block] block-->[section, block, suspension, Dataset] section-->[suspension, Dataset] suspension-->[Dataset] Dataset-->[Dataset]

sam-dev789 commented 1 year ago

https://docs.google.com/spreadsheets/d/1nayM4XwSFyO1y_4N0osWhpIr6zSpJrWsARgXHX0si8o/edit?usp=sharing

sam-dev789 commented 1 year ago

Constraints yaml https://github.com/sennetconsortium/portal-ui/commit/bc3bab320f5bf890715d8670295072fe7e1ec593#diff-b28c59b4d0b900fef904226dd34afda24e869e46349de4675173964a40adfb9eR1

shirey commented 1 year ago

After further conversations last week, I added the following to the constraints above-