Collect requirements to improve OEDatamodel

[srhbrnds]

In this issue requirements and ideas for improvement of the OEDatamodel are collected and discussed. The improvements should focus on the SEDOS project but are not limited to this context. We already have collected a few requirements within the course of project internal discussions:

• enable versioning
• enable bandwidths of values in scalar and timeseires (discussed in Enable bandwidths for scalars and timeseries #52)
• annotate reference dataset via ontology (OEO)
• enable N:N relation between scenario table and scalar and timeseries tables (discussed in Support reuse of data in multiple scenarios #46)

[jh-RLI]

Hi @srhbrnds, I have already worked on a solution for the m:n. Unfortunately, I have not yet been able to implement any of it. I have described the idea in this issue.

[bereba]

For the SEDOS project an anticipated requirement is to additionally integrate the spatio-sectoral aggregation method into the pipeline to automatically derive Typical Energy Strucutures (TES) when the reference data set is updated on the databus. These TES may be stored in an additional table separately to the reference data set. The scripts for the execution will be written in python. More concrete requirements will be discussed at a later point in time when the method is further developed.