Closed pvgenuchten closed 9 years ago
Created csw endpoint in production. The url is this one: https://dyfi.cobwebproject.eu/geonetwork/private/eng/csw-geoss
List of records currently available: https://dyfi.cobwebproject.eu/geonetwork/private/eng/csw-geoss?service=CSW&request=GetRecords&version=2.0.2
maria, this should be a public endpoint, since geoss is not able to login using saml
Then better if we wait for the single endpoint interface.
I doubt that Andreas want to add a new exception on saml that is only temporary.
In any case, the configuration is done, so it will work immediately on the single endpoint after the upgrade.
GEOSS should be fed with a custom csw-endpoint that only exposes dataset/service records that are supposed to be exposed to GEOSS.
Suggestion is @pvgenuchten will add a metadata category GEOSS and @Delawen will set up a custom csw endpoint with a filter GEOSS=true
An action of the data-publisher will then be to assign GEOSS=true to a metadata record to have it being exposed to GEOSS (that metadata record will point to a post-qa WMS/WFS/SOS, which will expose the data to GEOSS users)
Once available, @BartDeLathouwer can register the custom-csw-uri at GEOSS