chrwm

I ran into the same problem of a missing `discharging` process. Your discussion seems leaning towards electrical charging and discharging processes and is already deep-diving into the axioms. Taking one...

Hi El-Don-Quijote, thanks for your input. We agree with you but due to limited resources we're currently unable to realise new features. Are you interested in contributing on that matter?

For the guidelines of how to contribute to the repo, see [here](https://github.com/OpenEnergyPlatform/open-MaStR/blob/production/CONTRIBUTING.md). We have collected post-processing relevant code [here](https://github.com/OpenEnergyPlatform/open-MaStR/tree/production/postprocessing). See this [issue ](https://github.com/OpenEnergyPlatform/open-MaStR/issues/411)for a collection of post-processing features that open-mastr...

This issue may need further discussion to find a convenient solution. Hence, it will not yet be considered in oemetadata release v1.5 The proposed workaround seems to work well for...

FYI @srhbrnds @henhuy **Problem scope:** data & metadata = datapackage - maintain data & metdata user-friendly **Requirements on data & metadata (please add/edit):** - identify data sources for each data...

There is no designated bibfile field for licences. bibfile field `note` is shown per default in bibliography and could be used for licence information.

> One objection for me would be that we would require all users to use the Bibtex format if they want to cite sources and link them efficiently in the...

From today's meeting: A link to `bibSources` seems to be accepted as an extra OEM-key. The question of whether one should be able to see the licences of the individual...

To pick things up again - I propose to implemtent the following solution: 1. add a `link` field that links to a file containing the sources, e.g. a bibfile. 2....

> We should link to the context file that is related to the current release. For the released versions this could be changed. For future releases, the link should be...