The backend should be reconfigured to not inlcude the ontology in its own repository directly.
Instead it should be downloaded as part of the maven build process, configurable via the .pom file of the repo.
It should then be possible to set a specific tag of the ontolgy repo in the backend repo which should be checked out to select a specific ontology version.
The backend repo should then be extended for an ontology folder which should be put on .gitignore and a method provided to load the respective ontology into the backend for development.
Further when building the backend image the necessary ontology files should be updated according to an ontology tag and included in the backend image.
juliangruendner
commented
1 year ago
The ontology will now move to a central repository from which all other repositories should be updated.
the repo: https://github.com/medizininformatik-initiative/fhir-ontology-generator/tree/v2.0.0-RC/example/mii_core_data_set/ontology
will include the newest ontology.
The backend should be reconfigured to not inlcude the ontology in its own repository directly. Instead it should be downloaded as part of the maven build process, configurable via the .pom file of the repo.
It should then be possible to set a specific tag of the ontolgy repo in the backend repo which should be checked out to select a specific ontology version.
The backend repo should then be extended for an ontology folder which should be put on .gitignore and a method provided to load the respective ontology into the backend for development.
Further when building the backend image the necessary ontology files should be updated according to an ontology tag and included in the backend image.