With dashboards showing many different plots, it should be possible to switch e.g. wells in order to quickly update the plots (e.g. browse through all interesting wells).
Also with the current implementation of the Intersection module, it takes a long time to switch a well, rendering it difficult to compare/quality check different wells.
Possible solutions
Batching
Consider the possibility to let the user define the data they are interested in and then pre-load/batch-load it.
Requirements:
Mechanism frontend/backend for sending batch requests, pulling status, and eventually updating module (good candidate for a spike)
Questions:
How should batching be made available in the respective modules (new modules vs batch option in existing modules)
Challenges:
Sharing of long-running data would require caching for a smooth UX
Updating data/states from batch result instead of sending query
Caching questions:
Cache long-running data backend per user for a short period of time (e.g. 1 h) and extend caching time whenever data is accessed?
Example use cases:
With dashboards showing many different plots, it should be possible to switch e.g. wells in order to quickly update the plots (e.g. browse through all interesting wells).
Also with the current implementation of the
Intersection
module, it takes a long time to switch a well, rendering it difficult to compare/quality check different wells.Possible solutions
Batching
Consider the possibility to let the user define the data they are interested in and then pre-load/batch-load it.
Requirements:
Questions:
Challenges:
Caching questions:
Pagination
Already load data for the next X entities when browsing (https://tanstack.com/table/v8/docs/guide/pagination).
Challenges:
Conclusion