#1899: INSPIRE Pre-defined ATOM feeds

[etj]

Based on the work of @fgravin (https://github.com/fgravin/core-geonetwork/tree/atomFeed)

[etj]

As commented in #1899:

---

Minimum setup to test the PR:

• in Admin console/settings,
  • enable "INSPIRE" checkbox
  • in "Resource identifier prefix", set "id_" as the prefix (recommended, since the slashes in the default value may cause problems when creating internal links)
• create a metadata for data
  • create a resource id for the resource
  • add a downloadable resource, making sure that
    • "Function" is set to "download" (it's a dropdown menu)
    • "Application profile" is set to "ATOM" (it's a free text)
• create a service metadata
  • in the "Associated resources" panel, add a link to the previously created metadata
  • write down the UUID assigned to this service metadata
• change to privileges for both metadata, and make them visibile to all.

Make a call to:
http://YOUR_SERVER/geonetwork/srv/eng/atom.predefined.service?uuid=SERVICE_METADATA_UUID

[fxprunayre]

Would it make sense to add these new services in the API and not as old Jeeves path way - that gave them more visibility in the API doc - but maybe it is not relevant ?

[etj]

Good topic. These services are conformant to an "external standard", and are not an internal GN API. What's the policy that has been followed for the CSW? If CSW service is in the API, then also this endpoint should.

[fxprunayre]

Maybe a point to discuss in Bolsena (adding it to the agenda). Will you join ?

[stijngoedertier]

As discussed with @pvgenuchten I did some tests with this implementation of INSPIRE local ATOM feeds.

Test resource
After importing this set of metadata records
INSPIRE-ATOM-GeoNetwork-PR#1900-GeoSolutions-IT-export-full-1505250841308.zip, I confirm that I got a functional ATOM feed from the download-service metadata
(see https://vanilla.geocat.net/geonetwork/srv/eng/catalog.search#/metadata/ee99acf6-0c4f-4bf3-9bdd-c88f29d9eb50).

Test result
The test report (see INSPIRE-ATOM-GeoNetwork-PR#1900-GeoSolutions-IT-test-report.zip) by the INSPIRE etf-webapp validator run at http://inspire-sandbox.jrc.ec.europa.eu/etf-webapp/ does reveal some shortcomings. It seems that the URL to generate the OpenSearch description is not working (the OpenSearch description URL in that ATOM feed is https://vanilla.geocat.net/geonetwork/opensearch/eng/ee99acf6-0c4f-4bf3-9bdd-c88f29d9eb50/OpenSearchDescription.xml). Also there are some further issues with the content in the ATOM feeds.
This is also confirmed by tests by the INSPIRE GeoPortal Validator.

@etj could you please check whether there are any issues with the test resource I made or confirm that there are still some improvements to be done to get the OpenSearch description working?