Duplicating the metadata structure

[joergfunger]

@gdmiron We have no two different repos that have exactly the same information (metadata schema for sensor data). What would be the plan? Why do we need two? We should either have one or have the one that references the other one (e.g. using submodules or making pip packages that are then included in the other one).

[gdmiron]

Other colleagues wanted to work on metadata and schemas for packages and sensors to be used for developing the database and storing data for sensors.

At the task 7.5 meeting it became clear that it would be better to separate this from the digital twin.

On the digital twin side we would still be responsible for the model output and model run metadata.

I think that using a git submodule for metadata folder should work.

[joergfunger]

OK, would you then remove the double part in the demotwin repo. For the integrating, we could install in the conda environment in the pip part not only the local repo, but also the external one (requiring the other one to be a package installable via pip - though it is not required to upload that to pypi, could directly be a git-repo). This way, we would not need to use submodules (from my experience that comes often with merge conflicts)

dependencies:
   - all_the_real conda dependencies
   - pip:
     - "--editable=git+https://github.com/mypredisprojectgit@8c0d34291aaafec00e02eaa71cc2a242790a0fcc"