Load Ontology from ontology generator repo #201
Assignees
Milestone
Comments
|
@alexanderkiel FYI |
michael-82
added a commit
that referenced
this issue
Sep 18, 2023
- remove ui profile migration script an ui profile json files - download those files from github - disable cql translation in ci tests - update blaze in github integration tests - add flare in github integration tests - upload to codecov frequently fails in the last weeks...set fail_ci_if_error to false for now - modify readme to describe the changes in ontology handling - remove env variables from docker-compose.yml in github integration tests
michael-82
added a commit
that referenced
this issue
Sep 18, 2023
…-load-ontology-from-ontology-generator-repo #201 - Load ontology from ontology generator repo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The text was updated successfully, but these errors were encountered: