In DataCite/Datacite and OpenAIRE/oai_datacite exports, add to GeoLocationPlace properties what user enters in Production Location and Geospatial Geographic Coverage fields and fix comma bug
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
When the user enters information in the Citation metadata block's Production Location field and in the Geospatial metadata block's Geographic Coverage fields, both the DataCite/Datacite and OpenAIRE/oai_datacite exports should be updated so that they include in a GeoLocationPlace property what the user entered.
Currently, the OpenAIRE/oai_datacite export includes only what the user enters in the Citation metadata block's Production Location field. And the DataCite/Datacite export includes only what the user enters in the Geospatial metadata block's Geographic Coverage fields, and adds a trailing comma and extra commas after the state and city.
This issue is part of a larger effort to align both metadata exports, described in https://github.com/IQSS/dataverse/issues/11916 and https://github.com/IQSS/dataverse/issues/12281.
What kind of user is the feature intended for?
API User, Superuser, and Sysadmin
What inspired the request?
This is part of a larger effort to align the OpenAIRE/oai_datacite and DataCite/Datacite metadata exports. There is more context at https://github.com/IQSS/dataverse/issues/11916 and https://github.com/IQSS/dataverse/issues/12281.
What existing behavior do you want changed?
Currently, the DataCite/Datacite export adds what the user enters in the Geospatial metadata block's Geographic Coverage fields (Country, State, etc.) to GeoLocationPlace. For example:
<geoLocationPlace>France, Corsica,, CORTE,, Other,</geoLocationPlace>
The OpenAIRE/oai_datacite export adds what the user enters in the Citation metadata block's Production Location field to GeoLocationPlace instead. For example:
<geoLocationPlace>Production Location</geoLocationPlace>
Three changes are needed:
- The DataCite/Datacite export should be updated to also include, in
GeoLocationPlace, what the user enters in the Citation metadata block's Production Location field. - The OpenAIRE/oai_datacite export should be updated to also include, in
GeoLocationPlace, what the user enters in any of the Geospatial metadata block's Geographic Coverage fields. - In both exports, there should be only one comma between each value that the user enters in the Geospatial metadata block's Geographic Coverage fields, and no trailing comma, such as:
<geoLocationPlace>France, Corsica, CORTE, Other</geoLocationPlace>
Any open or closed issues related to this feature request?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the DataCite/Datacite and OpenAIRE/oai_datacite export entry points and read their current GeoLocationPlace handling. Update both exports to combine Production Location and all Geographic Coverage values with single comma separators and no trailing comma, then run the existing metadata export tests or add coverage for the examples in this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100