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 #11916 and #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 #11916 and #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?
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
GeoLocationPlaceproperty 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 #11916 and #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 #11916 and #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:The OpenAIRE/oai_datacite export adds what the user enters in the Citation metadata block's Production Location field to
GeoLocationPlaceinstead. For example:Three changes are needed:
GeoLocationPlace, what the user enters in the Citation metadata block's Production Location field.GeoLocationPlace, what the user enters in any of the Geospatial metadata block's Geographic Coverage fields.<geoLocationPlace>France, Corsica, CORTE, Other</geoLocationPlace>Any open or closed issues related to this feature request?