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 DynaGeo we want to present specific data types to the user, i.e., allow the user to select the data type before selecting the case. It would be very useful if 'SumoExplorer' could filter on cases containing requested data types.
One example is 4D seismic data, which would mean being able to filter out cases containing surfaces where metadata.content == "seismic" and "base" and "monitor" in metadata.date (?).
The text was updated successfully, but these errors were encountered:
This is likely relevant also for others. Not providing this through REST and/or through fmu-sumo will be incentive to write own queries directly against Elasticsearch, which is a pattern we don't want.
Will prioritize this 🚀
Generalized user story:
As a data consumer, I would like to filter cases on their content, so that I can limit available cases exposed to my users to those that have the necessary data and/or are compliant with the function my user is using.
General support for case filtering
Specific support for individual use cases, taking the data model into account. Will possibly spark discussions with fmu-dataio.
In DynaGeo we want to present specific data types to the user, i.e., allow the user to select the data type before selecting the case. It would be very useful if 'SumoExplorer' could filter on cases containing requested data types.
One example is 4D seismic data, which would mean being able to filter out cases containing surfaces where metadata.content == "seismic" and "base" and "monitor" in metadata.date (?).
The text was updated successfully, but these errors were encountered: