Database / Default content / Remove categories. #8063
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fxprunayre
added
db change
fxprunayre
force-pushed
the
44-categoriescleanup
branch
2 times, most recently
from
0981f5c
to
e1b2f72
Compare
The default categories provided in GeoNetwork since the early beginning are quite overlapping hierarchy level in ISO (eg. dataset, application, map) and in practice they are never used with the default values. It was making sense at the start to have a common grouping systems for the initial standards available in GeoNetwork like dublin core, FGDC, iso19115. Nowadays it is not recommended to use this default category list. Here we propose to not populate the default database with any category (and we do not alter databases which may be using them). This will also keep the UI simple. eg. If there is no category, no menu available in the editor (so users are not tempted to use the non recommended default values provided). We should highlight that the main (only) benefit of using category mechanism is to group records without adding the information in the metadata document.
fxprunayre
force-pushed
the
44-categoriescleanup
branch
from
e1b2f72
to
e3bd56d
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The default categories provided in GeoNetwork since the early beginning are quite overlapping hierarchy level in ISO (eg. dataset, application, map) and in practice they are never used with the default values. It was making sense at the start to have a common grouping systems for the initial standards available in GeoNetwork like dublin core, FGDC, iso19115. Nowadays it is not recommended to use this default category list.
Here we propose to not populate the default database with any category (and we do not alter databases which may be using them).
This will also keep the UI simple. eg. If there is no category, no menu available in the editor (so users are not tempted to use the non recommended default values provided).
We should highlight that the main (only) benefit of using category mechanism is to group records without adding the information in the metadata document. The documentation was updated.
Checklist
mainbranch, backports managed with labelREADME.mdfilespom.xmldependency management. Update build documentation with intended library use and library tutorials or documentation