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
We are using STA 1.1., to represent a series of neuroscience experiments. These experiments generate many datastreams with observations, but they also generate information which is not about the properties we want to measure, but about the actual measurements. They could be, for instance flags that tell us that a particular observation is important.
Does it make sense to represent these streams of metadata as datastreams?
Looking at the data model, it seems datastreams require properties such as UnitofMeasurement which don't really apply to these more abstract properties. Are there alternative ways in which this information could be captured?
Thanks in advance for your guidance.
The text was updated successfully, but these errors were encountered:
If the metadata is about each observation individually, the parameters attribute within the Observation entity can be used to store such information. You can also just use the properties attribute within the Datastream to store metadata for the whole collection of Observations
We are using STA 1.1., to represent a series of neuroscience experiments. These experiments generate many datastreams with observations, but they also generate information which is not about the properties we want to measure, but about the actual measurements. They could be, for instance flags that tell us that a particular observation is important.
Does it make sense to represent these streams of metadata as
datastreams
?Looking at the data model, it seems datastreams require properties such as UnitofMeasurement which don't really apply to these more abstract properties. Are there alternative ways in which this information could be captured?
Thanks in advance for your guidance.
The text was updated successfully, but these errors were encountered: