Recently I was doing work with APIs and I ran across the documents for the Crossref REST API at https://github.com/CrossRef/rest-api-doc.
This includes the following warning: "You should always url-encode DOIs and parameter values when using the API. DOIs are notorious for including characters that break URLs (e.g. semicolons, hashes, slashes, ampersands, question marks, etc.)." Parentheses can be encoded as %28 and %29. On Tuesday, June 4, 2019 at 2:07:20 PM UTC-4, Mr. B wrote: > > Hi there, > We've been experiencing some issues with the import publication details > using > DOI feature when the DOI contains parentheses. See for example > 10.1016/S2214-109X(16)30242-X, where multiple publications are found. > Parentheses are pretty rare in DOIs but there is one publisher, the > American > Society of Civil Engineers, that includes them in all publications, see for > ex: https://doi.org/10.1061/(ASCE)AE.1943-5568.0000342. > Any help would be appreciated!! > > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/de40284c-65d5-4011-9d52-8b3f94b3a1e3%40googlegroups.com.
