In the context of this issue, the phrase "Database roll-up" is being used to refer to the mechanism of being able to traverse the input/output graph of NMDC schema class instance relations (related by way of has_input and has_output slots) given an id of a class instance (any class instance like Biosample id, ProcessedSample id, Extraction id, etc.) we should be able to identify all the related class instances that are upstream of the given class instance, or downstream of the given class instance.
To accomplish this task, we need to come up with a structure of the API endpoint response object that will encode these upstream/downstream class instance relationships.
In the context of this issue, the phrase "Database roll-up" is being used to refer to the mechanism of being able to traverse the input/output graph of NMDC schema class instance relations (related by way of
has_input
andhas_output
slots) given an id of a class instance (any class instance like Biosample id, ProcessedSample id, Extraction id, etc.) we should be able to identify all the related class instances that are upstream of the given class instance, or downstream of the given class instance.To accomplish this task, we need to come up with a structure of the API endpoint response object that will encode these upstream/downstream class instance relationships.