Support #3860

SK: Support for TG 2.0 using own value for parameter outputschema

Added by Martin Tuchyna 16 days ago. Updated 7 days ago.

Status:FeedbackStart date:22 Jul 2020
Priority:UrgentDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Submitting Organisation:SK Knowledge-Base relevant?:No
Proactive:No Keyword #1:
Country:SK - Slovakia Keyword #2:
Originating UI: Keyword #3:

Description

Dear EC INSPIRE Geoportal Team

In connection to the support for TG 2.0, we would like to ask you if it is possible to use for harvesting setup for Slovak national CSW service our own value for parameter outputschema instead of value 'http://www.isotc211.org/2005/gmd'?

Explanation why we need is, that our implementation of CSW allow to configure multiple values for outpuschema and behind this parameter on backround is hidden process of XSLT transformation of metadata records.

Using this workflow, we want to transform current metadata meeting requirements of TG 1.3 to meet requirements of TG 2.0.

Here are examples:

INSPIRE TG 1.3: https://rpi.gov.sk/rpi_csw/service.svc/get?request=getrecords&service=csw&version=2.0.2&typenames=csw:Record&namespace=xmlns(csw=http://www.opengis.net/cat/csw/2.0.2)&outputSchema=http://www.isotc211.org/2005/gmd&resulttype=results&elementsetname=full&maxRecords=50

INSPIRE TG2.0: https://rpi.gov.sk/rpi_csw/service.svc/get?request=getrecords&service=csw&version=2.0.2&typenames=gmd:MD_Metadata&namespace=xmlns(gmd=http://www.isotc211.org/2005/gmd)&outputSchema=https://inspire.ec.europa.eu&resulttype=results&elementsetname=full&maxRecords=50

Thanks in advacne for your feedback.

Best regards,

Martin

History

#1 Updated by Daniele Francioli 7 days ago

  • Subject changed from Support for TG 2.0 using own value for parameter outputschema to SK: Support for TG 2.0 using own value for parameter outputschema
  • Status changed from New to Feedback
  • Submitting Organisation set to SK

Dear Martin,

Thank you for your message.

The feature you proposed would require some development on the Geoportal system but we are limited in resources and we are not able to plan it in the next months.

Given that in the next monitoring and reporting only MD encoded with TG 2.0 will be considered, could you think about serving the MD encoded following MD TG 2.0 with the standard output schema and the ones

encoded with MD TG 1.3 with a custom one?

Best regards,

Daniele on behalf of JRC INSPIRE Support team

Also available in: Atom PDF