Some thesauri, e.g. for the i18n labels, needs to be automatically loaded at boot time.
Unlike the fixtures, thesauri may be loaded over and over, since there's an update mechanism that only loads the deltas.
The thesaurus command (issue , doc) should be used, using the load --action update logic.
This task will also be used in projects, where mandatory custom thesauri are often used.
Also, geonode app may have their own set of thesauri; they should be placed in a thesauri/ dir within the app, e.g. the `geonode-rndt' app
https://github.com/geosolutions-it/geonode-rndt/tree/master/rndt/thesauri
The logic should loop all the declared apps, search for the 1st level dir thesauri/ and look for all the .rdf files in it.
It should be implemented as an autoload action in the existing thesaurus management command.
Then a new task in https://github.com/GeoNode/geonode/blob/master/tasks.py should be added to call such command. This task should be then invoked in the docker entrypoint script.
Some thesauri, e.g. for the i18n labels, needs to be automatically loaded at boot time.
Unlike the fixtures, thesauri may be loaded over and over, since there's an update mechanism that only loads the deltas.
The
thesauruscommand (issue , doc) should be used, using theload --action updatelogic.This task will also be used in projects, where mandatory custom thesauri are often used.
Also, geonode app may have their own set of thesauri; they should be placed in a
thesauri/dir within the app, e.g. the `geonode-rndt' apphttps://github.com/geosolutions-it/geonode-rndt/tree/master/rndt/thesauri
The logic should loop all the declared apps, search for the 1st level dir
thesauri/and look for all the .rdf files in it.It should be implemented as an
autoloadaction in the existingthesaurusmanagement command.Then a new task in https://github.com/GeoNode/geonode/blob/master/tasks.py should be added to call such command. This task should be then invoked in the docker entrypoint script.