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

Using CSW harvester OutputSchema is ignored while gmd is imposed #258

Open
ccancellieri opened this issue Oct 22, 2021 · 0 comments · May be fixed by #259
Open

Using CSW harvester OutputSchema is ignored while gmd is imposed #258

ccancellieri opened this issue Oct 22, 2021 · 0 comments · May be fixed by #259

Comments

@ccancellieri
Copy link
Contributor

ccancellieri commented Oct 22, 2021

Hi,
CSW is a very flexible and powerful standard which allows clients to query a catalog in several ways.
Normally a getCapabilities request is performed by the client to understand which formats are available etc.
The OWLlib is a good library but it still lack lots of low level functionalities like this (geopython/OWSLib#605).
I'm starting a discussion to introduce changes to that library but in the meanwhile I don't see why we can't have this here as well.
F.e. we could use the CSWharvester to gather metadata with different output schema formats at the moment gmd is imposed!!!

I'm going to propose a simple pull request (tested) which allows us to specify the target schema from the harvester configuration so if the server supports that schema it would be possible to obtain metadata in different formats.

My usecase is:

  1. I'd like to query GeoNetwork with csw asking for iso19115* specifying the outputschema
  2. I would like to specify it into the configuration (per harvester configuration).

With the PR I'm going to propose it would be possible.

ccancellieri added a commit to ccancellieri/ckanext-spatial that referenced this issue Oct 22, 2021
@ccancellieri ccancellieri linked a pull request Oct 22, 2021 that will close this issue
ccancellieri added a commit to ccancellieri/ckanext-spatial that referenced this issue Oct 22, 2021
…mespace and tag name so we can now harvest any kind of metadata (if validation is provided or ignored) ckan#209 ckan#210 ckan#219 ckan#258
ccancellieri added a commit to ccancellieri/ckanext-spatial that referenced this issue Oct 22, 2021
ccancellieri added a commit to ccancellieri/ckanext-spatial that referenced this issue Oct 22, 2021
…mespace and tag name so we can now harvest any kind of metadata (if validation is provided or ignored) ckan#209 ckan#210 ckan#219 ckan#258
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

Successfully merging a pull request may close this issue.

1 participant