Hello.
We have a number of GeoNetwork implementations that are requesting things related to thesurus management that GeoNetwork doesn’t seem to provide.
There are three main enhancement we would like to support -
1 - Editors can be given permission to manage and edit certain thesauri - at least locally created ones
2 - Access to a thesaurus can be limited to certain groups. Different groups would have different list of available thesuri
3 - External thesuri can be resferenced directly - no requirement to upload the thesaurus to GN
Do these ideas resonate? Any thoughts about the difficulty of implementing these? Anyone want to play with creating these functionalities?
Cheers,
Byron
Hi Byron, for point 2 and for organizations with similar requirements, we usually end up with custom editor views which only provides the thesaurus to be used in the context of a group/project. See screenshots https://geonetwork-opensource.org/manuals/4.0.x/en/customizing-application/editor-ui/custom-editor-examples.html#custom-editor-examples.
You could also limit thesaurus list in the editor using
https://github.com/geonetwork/core-geonetwork/blob/main/schemas/iso19139/src/main/plugin/iso19139/layout/config-editor.xml#L266-L285
Editor can still move to full view in some cases, so you could also restrict access to the full view by profile (see displayIfRecord in https://geonetwork-opensource.org/manuals/4.0.x/en/customizing-application/editor-ui/creating-custom-editor.html#defining-a-view) to not be able to access all thesaurus list.
In project like Ifremer - Sextant, we have 108 thesaurus, and ~10 editing forms which focus on projects and use particular thesaurus (and then portals have facets configured on those thesaurus).
But adding management of thesaurus by group could be relevant too.
Also quite some organization are using third party apps to manage vocabularies (eg. re3gistry, LD registry).
“Long” time ago, we (mainly Simon) also investigated using ISO19135 to describe thesaurus as a metadata record (https://geonetwork-opensource.org/manuals/4.0.x/en/administrator-guide/managing-classification-systems/managing-thesaurus.html#iso19135-register-format) so it was a metadata in itself so you had the capability to limit editing by groups - but I don’t think anyone is using that?
Cheers.
Francois
Le mer. 15 févr. 2023 à 22:32, Byron Cochrane via GeoNetwork-devel <geonetwork-devel@lists.sourceforge.net> a écrit :
Hello.
We have a number of GeoNetwork implementations that are requesting things related to thesurus management that GeoNetwork doesn’t seem to provide.
There are three main enhancement we would like to support -
1 - Editors can be given permission to manage and edit certain thesauri - at least locally created ones
2 - Access to a thesaurus can be limited to certain groups. Different groups would have different list of available thesuri
3 - External thesuri can be resferenced directly - no requirement to upload the thesaurus to GN
Do these ideas resonate? Any thoughts about the difficulty of implementing these? Anyone want to play with creating these functionalities?
Cheers,
Byron
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Hi François,
This is interesting. How do you choose which editing form to use by default depending on the group/project ?
Thanks,
Jean
···
Jean Pommier – pi-Geosolutions
Ingénieur, consultant indépendant
Tél. : (+33) 6 09 23 21 36
E-mail : jp@anonymised.com
Web : www.pi-geosolutions.fr
linkedin : jean-pommier
Le 16/02/2023 à 10:37, Francois Prunayre via GeoNetwork-devel a écrit :
Hi Byron, for point 2 and for organizations with similar requirements, we usually end up with custom editor views which only provides the thesaurus to be used in the context of a group/project. See screenshots https://geonetwork-opensource.org/manuals/4.0.x/en/customizing-application/editor-ui/custom-editor-examples.html#custom-editor-examples.
You could also limit thesaurus list in the editor using
https://github.com/geonetwork/core-geonetwork/blob/main/schemas/iso19139/src/main/plugin/iso19139/layout/config-editor.xml#L266-L285
Editor can still move to full view in some cases, so you could also restrict access to the full view by profile (see displayIfRecord in https://geonetwork-opensource.org/manuals/4.0.x/en/customizing-application/editor-ui/creating-custom-editor.html#defining-a-view) to not be able to access all thesaurus list.
In project like Ifremer - Sextant, we have 108 thesaurus, and ~10 editing forms which focus on projects and use particular thesaurus (and then portals have facets configured on those thesaurus).
But adding management of thesaurus by group could be relevant too.
Also quite some organization are using third party apps to manage vocabularies (eg. re3gistry, LD registry).
“Long” time ago, we (mainly Simon) also investigated using ISO19135 to describe thesaurus as a metadata record (https://geonetwork-opensource.org/manuals/4.0.x/en/administrator-guide/managing-classification-systems/managing-thesaurus.html#iso19135-register-format) so it was a metadata in itself so you had the capability to limit editing by groups - but I don’t think anyone is using that?
Cheers.
Francois
Le mer. 15 févr. 2023 à 22:32, Byron Cochrane via GeoNetwork-devel <geonetwork-devel@lists.sourceforge.net> a écrit :
Hello.
We have a number of GeoNetwork implementations that are requesting things related to thesurus management that GeoNetwork doesn’t seem to provide.
There are three main enhancement we would like to support -
1 - Editors can be given permission to manage and edit certain thesauri - at least locally created ones
2 - Access to a thesaurus can be limited to certain groups. Different groups would have different list of available thesuri
3 - External thesuri can be resferenced directly - no requirement to upload the thesaurus to GN
Do these ideas resonate? Any thoughts about the difficulty of implementing these? Anyone want to play with creating these functionalities?
Cheers,
Byron
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
_______________________________________________
GeoNetwork-devel mailing list
[GeoNetwork-devel@lists.sourceforge.net](mailto:GeoNetwork-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geonetwork-devel](https://lists.sourceforge.net/lists/listinfo/geonetwork-devel)
GeoNetwork OpenSource is maintained at [http://sourceforge.net/projects/geonetwork](http://sourceforge.net/projects/geonetwork)
Hi Jean, there is no direct configuration but you can customize it when the editor initialize https://github.com/geonetwork/core-geonetwork/blob/main/web-ui/src/main/resources/catalog/js/edit/EditorController.js#L265-L283
Cheers
Francois
Le mer. 22 févr. 2023 à 22:56, Jean Pommier via GeoNetwork-devel <geonetwork-devel@lists.sourceforge.net> a écrit :
Hi François,
This is interesting. How do you choose which editing form to use by default depending on the group/project ?
Thanks,
Jean
Jean Pommier – pi-Geosolutions
Ingénieur, consultant indépendant
Tél. : (+33) 6 09 23 21 36
E-mail : jp@…1001…
Web : www.pi-geosolutions.fr
linkedin : jean-pommier
Le 16/02/2023 à 10:37, Francois Prunayre via GeoNetwork-devel a écrit :
Hi Byron, for point 2 and for organizations with similar requirements, we usually end up with custom editor views which only provides the thesaurus to be used in the context of a group/project. See screenshots https://geonetwork-opensource.org/manuals/4.0.x/en/customizing-application/editor-ui/custom-editor-examples.html#custom-editor-examples.
You could also limit thesaurus list in the editor using
https://github.com/geonetwork/core-geonetwork/blob/main/schemas/iso19139/src/main/plugin/iso19139/layout/config-editor.xml#L266-L285
Editor can still move to full view in some cases, so you could also restrict access to the full view by profile (see displayIfRecord in https://geonetwork-opensource.org/manuals/4.0.x/en/customizing-application/editor-ui/creating-custom-editor.html#defining-a-view) to not be able to access all thesaurus list.
In project like Ifremer - Sextant, we have 108 thesaurus, and ~10 editing forms which focus on projects and use particular thesaurus (and then portals have facets configured on those thesaurus).
But adding management of thesaurus by group could be relevant too.
Also quite some organization are using third party apps to manage vocabularies (eg. re3gistry, LD registry).
“Long” time ago, we (mainly Simon) also investigated using ISO19135 to describe thesaurus as a metadata record (https://geonetwork-opensource.org/manuals/4.0.x/en/administrator-guide/managing-classification-systems/managing-thesaurus.html#iso19135-register-format) so it was a metadata in itself so you had the capability to limit editing by groups - but I don’t think anyone is using that?
Cheers.
Francois
Le mer. 15 févr. 2023 à 22:32, Byron Cochrane via GeoNetwork-devel <geonetwork-devel@lists.sourceforge.net> a écrit :
Hello.
We have a number of GeoNetwork implementations that are requesting things related to thesurus management that GeoNetwork doesn’t seem to provide.
There are three main enhancement we would like to support -
1 - Editors can be given permission to manage and edit certain thesauri - at least locally created ones
2 - Access to a thesaurus can be limited to certain groups. Different groups would have different list of available thesuri
3 - External thesuri can be resferenced directly - no requirement to upload the thesaurus to GN
Do these ideas resonate? Any thoughts about the difficulty of implementing these? Anyone want to play with creating these functionalities?
Cheers,
Byron
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
_______________________________________________
GeoNetwork-devel mailing list
[GeoNetwork-devel@lists.sourceforge.net](mailto:GeoNetwork-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geonetwork-devel](https://lists.sourceforge.net/lists/listinfo/geonetwork-devel)
GeoNetwork OpenSource is maintained at [http://sourceforge.net/projects/geonetwork](http://sourceforge.net/projects/geonetwork)
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork