-
-
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
Search with GVK / ISBN does not work properly #10160
Comments
Searching with GVK raises an Exception on my 5.9 According to the Homepage from gbv there was an URL update. Therefore a simple update in the fetcher file may be sufficient:
URL_PATTERN = "http://sru.gbv.de/gvk?" --> URL_PATTERN = "http://sru.k10plus.de" Sorry, but I have no JDK to test whether that works. But if I use the URL Pattern within the Exception and update it with the new URL Pattern in the browser, I get a proper XML file. So I suppose it will work. |
Thanks a lot! We will check this! |
Fixes Part of #10160 compare code attributes in xml with ignore case
@ds-sic Hi, yes the limit of 50 is set hard in JabRef. As we rely on the goodwill of the publisher/catalogs, we have limited the results. However, the GVK Fetcher also allows searching for year https://docs.jabref.org/collect/import-using-online-bibliographic-database#search-syntax It might be possible to implement pagination, so we don't have to fetch all the results in advance. But I am not that deep into the search options of the SRU interface. |
@Siedlerchr Hej, thanks for the information, the limit is fine. And thanks for the fix. With Version 5.10 the GVP search is running again :-) |
JabRef version
5.9 (latest release)
Operating system
Windows
Details on version and operating system
No response
Checked with the latest development build
Steps to reproduce the behaviour
Searching for "Digitalisierung" alone yields only 50 results. According to this, there is a limit of 50 somewhere. Searching for "Digitalisierung 2023" only brings up 6 results for me. Could the internally set limit be the reason?
Appendix
...
Log File
The text was updated successfully, but these errors were encountered: