juliangruendner
commented
3 weeks ago @geloro94 , @michael-82 in a first version i would leave the ontology generator as is and base the elastic search ontology generation on the ui_trees. In the future it should be discussed whether generating the ui_tree is still necessary or whether the elastic search ontology could be generated instead, as we will most likely only use the elastic search ontology derived from it
Add Elastic Search ontology generation (see: https://github.com/medizininformatik-initiative/feasibility-ontology-elasticsearch) to the ontology generator so that the input file used to initialise the elastic search of the new backend for the dataportal ui is automatically generated based on the ui tree and made available as part of the release and added to the backend.zip ontology folder, so that it can be read in and used in future deployments of the datenportal backend.
https://github.com/medizininformatik-initiative/feasibility-backend