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
In the simulation i'm working on, for example because of how packing and unpacking is implemented, the same 'medical gown' resource will exist at different times at for different owners (and places) identified under more than one reflow os id in its lifetime.
This is expected behaviour, and i guess it's the task of a tracking identifier to string back together these resources and events in valueflows.
Thinking ahead, if I would want to create a material passport for one physical medical gown that integrates all it's incarnations, i would have to query all economic resources that have this trackingIdentifier attached, and also all the economic events related to these resources in the system.
It's not clear to me how I would go about it efficiently because the 'filter' queries for economic resource and for economic events do not seem to support the trackingIdentifier as an argument.
The text was updated successfully, but these errors were encountered:
In the simulation i'm working on, for example because of how packing and unpacking is implemented, the same 'medical gown' resource will exist at different times at for different owners (and places) identified under more than one reflow os id in its lifetime.
This is expected behaviour, and i guess it's the task of a tracking identifier to string back together these resources and events in valueflows.
Thinking ahead, if I would want to create a material passport for one physical medical gown that integrates all it's incarnations, i would have to query all economic resources that have this trackingIdentifier attached, and also all the economic events related to these resources in the system.
It's not clear to me how I would go about it efficiently because the 'filter' queries for economic resource and for economic events do not seem to support the trackingIdentifier as an argument.
The text was updated successfully, but these errors were encountered: