DB / Replacing unused CswCapabilitiesInfo by Translations #4756
Conversation
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.
|
Some questions about the API:
|
No. I expect to work on that on version 4 mainly for the facet config.
Remove all before. So you can make a partial update, only one language, or replace everything |
|
Will only applied to v4. |
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.