Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support ISO metadata harvesting #223

Closed
mandsch opened this issue Feb 20, 2014 · 7 comments
Closed

Support ISO metadata harvesting #223

mandsch opened this issue Feb 20, 2014 · 7 comments

Comments

@mandsch
Copy link

mandsch commented Feb 20, 2014

Enable pycsw to support CSW harvesting of ISO metadata records, by using gmd:MD_Metadata typename in the getrecords request (in addition to csw:Record).

@tomkralidis
Copy link
Member

@tomkralidis
Copy link
Member

I think the typenames parameter, in which gmd:MD_Metadata is required for APISO, might be a moot point for the CSW harvesting another CSW use case, unless your harvesting involves filters. pycsw does CSW harvesting against all records of another CSW and doesn't apply filters. Would this be valuable or is harvesting all CSW records good for now?

Thinking more, I guess the question becomes whether we:

1./ check if the target CSW supports ISO typename and outputschema (they should be mutually exclusive, though). If it does, then harvest the CSW's records as ISO. If not, then harvest the CSW's records as Dublin Core

2./ Set manager.csw_harvest_type=apiso and do this without checking

Other options?

Option makes this easier for the user, but makes the assumption that ISO metadata is preferred. Still option sounds easier on the user. @mandsch thoughts/comments?

@mandsch
Copy link
Author

mandsch commented Feb 24, 2014

Tom, thanks for taking this up here. My use case is driven from INSPIRE requirements.
I think the important bit for the use in the INSPIRE area is the support for harvesting other CSWs that primarily support ISO outputschema. So for this use-case the option sounds easier, but I would prefer solution 1, that would examine the capabilities, checks for the outputschema and uses the preferred typename of the remote CSW (assuming that the first in the list of typenames is the default one).

@tomkralidis
Copy link
Member

@mandsch almost there; can you provide a stable CSW server to test this against?

@smrgeoinfo
Copy link

Tom-- you can try http://catalog.usgin.org/geoportal/csw/discovery?request=GetCapabilities&service=CSW
It provides USGIN-profile ISO 19139 xml, similar to INSPIRE profile. It's an ESRI Geoportal CSW.

I'm eager to see this working as well, so we can plug it into CKAN.

@mandsch
Copy link
Author

mandsch commented Mar 6, 2014

Tom, here's the URL of our Geonetwork catalogue: http://gdk.gdi-de.org/gdi-de/srv/eng/csw?SERVICE=CSW&VERSION=2.0.2&REQUEST=GetCapabilities
(sorry, for the delay).

@jachym
Copy link
Member

jachym commented Mar 31, 2014

I think, this is also related to my issue. According to how I understand the problem, czech metadata inspire portal prefers ISO as well: http://geoportal.gov.cz/php/micka/csw/index.php

kalxas added a commit that referenced this issue May 13, 2014
 Support ISO metadata harvesting #223
@kalxas kalxas closed this as completed May 13, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants