-
Notifications
You must be signed in to change notification settings - Fork 1
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
unescaped closing bracket in content URL in Zenodo metadata causes disruption in verification workflow #317
Comments
…response associated with https://zenodo.org/records/13505983; related to #317
fyi @slint note that in
the closing bracket is not escaped. This choked up my poor little java URI parser. I implemented a workaround that generates the more URI friendly
Are you aware of this? |
With current workaround,
showing that the (restricted) content can be retrieved, provided that the receiver has a api token with appropriate credentials. |
when running
on batlit (as part of testing fix of #316 ), metadata associated with https://zenodo.org/records/13505983 contains a "file link" with unescaped characters in the URL as seen in
https://zenodo.org/api/records/13505983/files/Thuiller et al. - 2006 - INTERACTIONS BETWEEN ENVIRONMENT, SPECIES TRAITS, .]/content
part of
as part of
The text was updated successfully, but these errors were encountered: