search

datacite / lupo

DataCite REST API
https://api.datacite.org
MIT License
12 stars 8 forks source link

Add support for geoLocationPolygon entries as part of the json API attributes #327

Open richardhallett opened 5 years ago

richardhallett commented 5 years ago

Add support for geoLocationPolygon entries as part of the json API attributes

This should allow you to send a full geoLocation entry with associated geoLocationPolygon elements as you would in the XML.

Front logo Front conversations

kjgarza commented 5 years ago

more detail in to fix: https://app.frontapp.com/open/msg_4ieecub

richardhallett commented 4 years ago

Still a requirement, causes some confusion in regards to what is and isn't allowed via the attributes.

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

nensor commented 2 years ago

Wondering if this is still active; my recent tests appear to ignore "geoLocationPolygon" attributes entirely. I see the "geoLocationPlace" is taken, but none of the points. Example DOI on DataCite test server: 10.80447/23903. More details can be provided if needed.

KellyStathis commented 2 years ago

Hi @nensor - it is not currently possible to provide geoLocationPolygon attributes as JSON via the REST API. However, this metadata can be provided via XML as described here: https://support.datacite.org/docs/api-create-dois#provide-metadata-in-formats-other-than-json/

I took a look at your example and it looks like the geoLocationPolygon field is there: https://api.test.datacite.org/dois/10.80447/23903. Was this created by submitting metadata in XML format?

nensor commented 2 years ago

Yes, I've gone back to submitting in XML format for this information. Upcoming projects were transitioning to JSON, but running across this issue has forced a regression in this case.

nensor commented 2 years ago

I should note, the program in question is still using DataCite's old (?) MDS service exclusively in XML, which was what I was intending to transition from. Is the only really viable way to submit this is essentially creating an entire XML string in memory, encode that to base64, and tack that in via an "xml" attribute in order to support this functionality? That seems rather excessive.

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

tmorrell commented 4 months ago

This is still an issue

Califer commented 3 days ago

It's been five years. As it is, trying to use JSON with the API is crippled because there are fields that are unavailable with JSON that are available through the API if I use XML. I've been waiting so long to be able to use JSON. I can't fathom why you would set up the ability for us to use JSON, but not make it fully functional.