CSW / Configuration of the capabilities is now done using a service metadata record #4390

fxprunayre · 2020-01-23T09:06:22Z

Main goal here is to :

give possibility to user to configure in more details the GetCapabilities document.
make a valid INSPIRE CSW service
simplify the config which was dispatched in user properties, settings table, csw capabilities info + 2 templates XML files.

This will encourage users to make a service metadata record describing the CSW endpoint (which is a good practice and is mandatory from an INSPIRE point of view).

Documentation: https://github.com/geonetwork/doc/blob/5b3743117d74856f4a8f7ab2b4f39048603b4a13/source/administrator-guide/configuring-the-catalog/csw-configuration.rst

If CSW is disabled, hide related options

If a custom capabilities has to be created, point to a service metadata record

If the config use a private record or there is an error while building the capabilities document, a WARNING is reported using a comment and the default capabilities is used

Add the possibility to customize a portal CSW

…etadata record.

…etadata record / Add warning in case of error. Language config is made in the record, not from the db.

…etadata record / Add warning in case of error. Multilingual support.

…etadata record / Add warning in case of error. ISO19139 support and language.

…etadata record / Add warning in case of error. Displaye service title.

fxprunayre · 2020-01-27T15:54:00Z

@jahow we discussed (not sure when & where but not so long ago) the need to display a description of the catalogue in the home page and I think one of the option was to use the cswservercapabilitiesinfo that I'm about to drop in that PR. If we don't use (or plan to use it), I'll remove it. Any objection ?

…etadata record / Add warning in case of error. Portal CSW.

core/src/main/java/org/fao/geonet/kernel/setting/Settings.java

web/src/main/webapp/xml/csw/capabilities.xml

josegar74 · 2020-01-28T06:27:57Z

web/src/main/webapp/WEB-INF/classes/setup/sql/migrate/v3101/migrate-default.sql

@@ -1,2 +1,6 @@
+DELETE FROM cswservercapabilitiesinfo;


Should be dropped the table and removed the related domain/persistence objects?

Waiting for @jahow to see if that table is used somewhere or not.

josegar74

Tested and works fine.

Let's wait 1-2 days for @jahow feedback about the CswCapabilitiesInfo, otherwise can be merged and manage the removal of CswCapabilitiesInfo in another PR:

jahow · 2020-01-30T15:54:30Z

Sorry for not giving feedback sooner, you were right to get rid of this! we ended up not using it. Thanks

…etadata record (#4390) * CSW / Configuration of the capabilities is now done using a service metadata record. * CSW / Configuration of the capabilities is now done using a service metadata record. * CSW / Configuration of the capabilities is now done using a service metadata record / Add warning in case of error. Language config is made in the record, not from the db. * CSW / Configuration of the capabilities is now done using a service metadata record / Add warning in case of error. Multilingual support. * CSW / Configuration of the capabilities is now done using a service metadata record / Add warning in case of error. ISO19139 support and language. * CSW / Configuration of the capabilities is now done using a service metadata record / Add warning in case of error. Displaye service title. * Cleaning. * CSW / Configuration of the capabilities is now done using a service metadata record / Add warning in case of error. Portal CSW. * Replace id by uuid.

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.

* DB / Replacing unused CswCapabilitiesInfo by Translations 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. * DB / Replacing unused CswCapabilitiesInfo by Translations. Update cleanup script for test. * DB / Replacing unused CswCapabilitiesInfo by Translations. Test. * DB / Replacing unused CswCapabilitiesInfo by Translations. OpenApi.

…etadata record (geonetwork#4390) * CSW / Configuration of the capabilities is now done using a service metadata record. * CSW / Configuration of the capabilities is now done using a service metadata record. * CSW / Configuration of the capabilities is now done using a service metadata record / Add warning in case of error. Language config is made in the record, not from the db. * CSW / Configuration of the capabilities is now done using a service metadata record / Add warning in case of error. Multilingual support. * CSW / Configuration of the capabilities is now done using a service metadata record / Add warning in case of error. ISO19139 support and language. * CSW / Configuration of the capabilities is now done using a service metadata record / Add warning in case of error. Displaye service title. * Cleaning. * CSW / Configuration of the capabilities is now done using a service metadata record / Add warning in case of error. Portal CSW. * Replace id by uuid.

RobertGlowacki · 2021-01-22T13:06:49Z

I've created such a file I attached below.

When I'm in Contribute -> Manage directory -> Entry types I see Organization and Contacts I see this template with data I typed in.
Then I move to Admin console -> CSW -> Record to use for getCapabilities. However I
don't know any UUID number to type here, when I type name of this nothing changes in my request:
http://localhost:8080/geonetwork/srv/eng/csw?request=GetCapabilities&service=CSW&acceptVersions=2.0.2&acceptFormats=application%2Fxml

fxprunayre · 2021-01-22T13:11:40Z

When I'm in Contribute -> Manage directory -> Entry types I see Organization and Contacts I see this template with data I typed in.

You've to create a service metadata record (https://geonetwork-opensource.org/manuals/trunk/en/administrator-guide/configuring-the-catalog/csw-configuration.html?#service-metadata-record) not a contact.

RobertGlowacki · 2021-01-22T13:21:00Z

Now I'm able to create metadata standard from Admin console -> Metadata and templates and fill some of fileds of point of contact and get proper response from this request http://localhost:8080/geonetwork/srv/eng/csw?request=GetCapabilities&service=CSW&acceptVersions=2.0.2&acceptFormats=application%2Fxml
Some fields including phone number and address are still empty
Hoverwer I still don't know where I have to put this xml -> https://github.com/geonetwork/core-geonetwork/blob/master/web/src/main/webapp/xml/csw/capabilities.xml

RobertGlowacki · 2021-01-25T15:50:01Z

Is it possible to make a request from http://localhost:8080/geonetwork/doc/api/index.html and fullfill point of contact fields via cURL?

fxprunayre · 2021-02-02T06:03:58Z

"Choose the record to be used to build custom GetCapabilities document. If none exist, create a service metadata record (using ISO19139 or 19115-3 standards). To have a capabilities document with the main information required, set title, abstract, point of contact, keywords, constraints. If you need INSPIRE support also set properly the record main language and additional languages, INSPIRE themes and INSPIRE conformity."

eg.
https://apps.titellus.net/geonetwork/srv/eng/catalog.search#/metadata/2218e8cf-3203-46a5-8df7-e9effe610f1a
produce
https://apps.titellus.net/geonetwork/srv/eng/csw?SERVICE=CSW&REQUEST=GetCapabilities

You don't have to change anything in the source code.

CSW / Configuration of the capabilities is now done using a service m…

68b828d

…etadata record.

fxprunayre added this to the 3.10.1 milestone Jan 23, 2020

fxprunayre mentioned this pull request Jan 23, 2020

INSPIRE / CSW - Conformité du getcapabilities SPW-DIG/metawal-core-geonetwork#501

Closed

fxprunayre added 4 commits January 23, 2020 11:56

CSW / Configuration of the capabilities is now done using a service m…

016dcfa

…etadata record.

CSW / Configuration of the capabilities is now done using a service m…

c5e6cbe

…etadata record / Add warning in case of error. Language config is made in the record, not from the db.

CSW / Configuration of the capabilities is now done using a service m…

ed9a960

…etadata record / Add warning in case of error. Multilingual support.

CSW / Configuration of the capabilities is now done using a service m…

c4e7c78

…etadata record / Add warning in case of error. ISO19139 support and language.

fxprunayre mentioned this pull request Jan 27, 2020

Update CSW configuration. geonetwork/doc#119

Merged

fxprunayre added the enhancement label Jan 27, 2020

CSW / Configuration of the capabilities is now done using a service m…

9bc2afa

…etadata record / Add warning in case of error. Displaye service title.

fxprunayre marked this pull request as ready for review January 27, 2020 15:52

fxprunayre requested review from josegar74 and pvgenuchten January 27, 2020 15:54

fxprunayre added 2 commits January 27, 2020 16:58

Cleaning.

631fe50

CSW / Configuration of the capabilities is now done using a service m…

2be3c13

…etadata record / Add warning in case of error. Portal CSW.

josegar74 reviewed Jan 28, 2020

View reviewed changes

Replace id by uuid.

77ddf71

fxprunayre mentioned this pull request Jan 28, 2020

Samples / Add service record for CSW GetCapabilities config. metadata101/iso19115-3.2018#29

Merged

josegar74 approved these changes Jan 28, 2020

View reviewed changes

fxprunayre merged commit 62590c3 into geonetwork:master Jan 28, 2020

fxprunayre mentioned this pull request Feb 21, 2020

INSPIRE CSW GetCapabilities conformity specification title should use the request language #2769

Closed

fxprunayre mentioned this pull request Jun 12, 2020

DB / Replacing unused CswCapabilitiesInfo by Translations #4756

Closed

fxprunayre mentioned this pull request Jul 3, 2020

DB / Replacing unused CswCapabilitiesInfo by Translations #4823

Merged

fxprunayre mentioned this pull request Jan 21, 2021

Missing data for Service Contact, GetCapabilities CSW in Geonetwork 3.2 #2097

Open

fxprunayre mentioned this pull request Dec 23, 2021

CSW / Portal capabilities should not use the default titellus/core-geonetwork#91

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

CSW / Configuration of the capabilities is now done using a service metadata record #4390

CSW / Configuration of the capabilities is now done using a service metadata record #4390

fxprunayre commented Jan 23, 2020 •

edited

Loading

fxprunayre commented Jan 27, 2020

josegar74 Jan 28, 2020

fxprunayre Jan 28, 2020

josegar74 left a comment

jahow commented Jan 30, 2020

RobertGlowacki commented Jan 22, 2021

fxprunayre commented Jan 22, 2021

RobertGlowacki commented Jan 22, 2021 •

edited

Loading

RobertGlowacki commented Jan 25, 2021 •

edited

Loading

fxprunayre commented Feb 2, 2021

CSW / Configuration of the capabilities is now done using a service metadata record #4390

CSW / Configuration of the capabilities is now done using a service metadata record #4390

Conversation

fxprunayre commented Jan 23, 2020 • edited Loading

fxprunayre commented Jan 27, 2020

josegar74 Jan 28, 2020

Choose a reason for hiding this comment

fxprunayre Jan 28, 2020

Choose a reason for hiding this comment

josegar74 left a comment

Choose a reason for hiding this comment

jahow commented Jan 30, 2020

RobertGlowacki commented Jan 22, 2021

fxprunayre commented Jan 22, 2021

RobertGlowacki commented Jan 22, 2021 • edited Loading

RobertGlowacki commented Jan 25, 2021 • edited Loading

fxprunayre commented Feb 2, 2021

fxprunayre commented Jan 23, 2020 •

edited

Loading

RobertGlowacki commented Jan 22, 2021 •

edited

Loading

RobertGlowacki commented Jan 25, 2021 •

edited

Loading