-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Entry creation from DOI does not recognize URL encoding, but "get bibliographical data" does #10648
Comments
Hi @Siedlerchr can I work on this bug ? |
As a general advice for newcomers: check out Contributing for a start. Also, guidelines for setting up a local workspace is worth having a look at. Feel free to ask here at GitHub, if you have any issue related questions. If you have questions about how to setup your workspace use JabRef's Gitter chat. Try to open a (draft) pull-request early on, so that people can see you are working on the issue and so that they can see the direction the pull request is heading towards. This way, you will likely receive valuable feedback. |
Hey @DEEPAM-KUMAR are you still working on this? |
Seems like nobody is working on this issue |
Hi @DominikStiller, |
@randhirrkumar, I did not realize that, thank you! That's a workaround at least. Still the behavior is inconsistent because it is generally possible to pass a URL to the new entry dialog, just not one with URL-encoded characters. So there is still a bug to be fixed here. |
Implementation steps:
|
Hey @koppor, can you please elaborate a few on this that you have mentioned "Fix org.jabref.model.entry.identifier.DOI to urldecode URL before interpreting" |
I meant: At org.jabref.model.entry.identifier.DOI#DOI, right after |
Hi. I would like to wotk on this issue. Could you assign this to me? Thanks in advance! |
At org.jabref.model.entry.identifier.DOI#DOI, the method which the trimmedDoi is decoded has been modified in the case trimmedDoi being an HTTP URL.
Issue not fully fixed by #11036, missing: "New entry from Id" is not fixed. |
* Fix for Issue #10648 At org.jabref.model.entry.identifier.DOI#DOI, the method which the trimmedDoi is decoded has been modified in the case trimmedDoi being an HTTP URL. * PR corrections 1)java.net.URLDecoder.decode(String, Charset) is now used 2)Tests from acceptEncodedDoiUrl moved to testData 3)rewriteRun task has been executed * PR corrections 1)Change Test/comment place
Hi, I'd like to be assigned to this. |
@subhramit This is kind of detective work to understand how JabRef treats Strings coming from there. |
Yes, I finally got it, it was extremely hard to debug. Many hours of breakpoint after breakpoint and turns out that the issue was because of a non-matching regex which was truncating the trailing ";2". |
Update See below. It is now about the "Entry from Id" dialog!
JabRef version
Latest development branch build (please note build date below)
Operating system
Windows
Details on version and operating system
JabRef 5.12--2023-11-16--85cd85f, Windows 10 Pro 22H2
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Find a DOI that contains URL-encoded characters such as %3C (<) or %3E( >). My example DOI: https://doi.org/10.1175/1520-0493(2002)130%3C1913:EDAWPO%3E2.0.CO;2
Add a new entry from the DOI.
Result: It fails.
Add an empty entry.
Enter the DOI in its DOI field.
Use the "get bibliographical data from DOI" function.
Result: It works.
Appendix
No response
The text was updated successfully, but these errors were encountered: