-
Notifications
You must be signed in to change notification settings - Fork 0
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
Added DataCite metadata using PyCSW's latest version. #3
Conversation
@@ -77,6 +85,6 @@ | |||
"pycsw:Publisher": "publisher", | |||
"pycsw:Contributor": "contributor", | |||
"pycsw:Relation": "relation", | |||
"pycsw:Links": "download_links", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please double check if this will lead to regressions
please check the pycsw test error |
… not support the DataCite metadata.
…R at PyCSW referred.
This test error is due to an error on PyCSW 3.0. An issue (geopython/pycsw#924) and a PR (geopython/pycsw#925) has been created for PyCSW. This error is totally unrelated to what we did for DatCite metadata, in fact this error originates from FGDC metadata (which is not even used for GeoNode, we only have ISO and Dublin Core for now). I have temporarily disabled the failing test, and should be re-enabled once the PR is merged. |
@gannebamm currently the datacite feature is only in the |
… is released. Re-added the breaking test for FGDC metadata.
PR is updated with 3.0.0-alpha5 |
Adds download button for DataCite format. This PR is related to the Thuenen-GeoNode-Development/geonode#3 which integrates pyCSW `v3` (as alpha) to provide DataCite download format on the backend. Closes #27
Fixed the issue of contacts not appearing in DataCite metadata. The URLs for contact's profile are still not appearing because of a bug in pycsw. A PR (geopython/pycsw#945) has been opened for this issue (geopython/pycsw#944). |
Resolves https://github.com/Thuenen-GeoNode-Development/Sprints/issues/5
Checklist
For all pull requests:
The following are required only for core and extension modules (they are welcomed, but not required, for contrib modules):
Submitting the PR does not require you to check all items, but by the time it gets merged, they should be either satisfied or inapplicable.