DB / Replacing unused CswCapabilitiesInfo by Translations #4823
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
Relates to geonetwork#4390 which makes the CSW GetCapabilities configuration now done in a service metadata record. The CswCapabilitiesInfo was unused. So removing it. Replace that table by a translations table which can contains a list of translations that can be manage through the API. In a number of situation, catalogue administrator wants to update client application translation. This will be even more true in version 4 where you can for example configure facet from the admin. When adding a facet, corresponding labels will have to be added for the client side to render properly labels. Those translations can be stored in this table and the client side will load them. It could also be used to overrides some default translation if this is something to support.
…anup script for test.
34 tasks
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.
Relates to #4390 which
makes the CSW GetCapabilities configuration now done in a service
metadata record. The CswCapabilitiesInfo was unused. So removing it.
Replace that table by a translations table which can contains a list of
translations that can be manage through the API.
In a number of
situation, catalogue administrator wants to update client application
translation. This will be even more true in version 4 where you can for
example configure facet from the admin. When adding a facet,
corresponding labels will have to be added for the client side to render
properly labels. Those translations can be stored in this table and the
client side will load them. It could also be used to overrides some
default translation if this is something to support.
Replace #4756