Search errors in different catalogues

[emilianosalatino]

JabRef version

5.15 (latest release)

Operating system

Windows

Details on version and operating system

Windows 10, Windows 11

Checked with the latest development build (copy version output from About dialog)

• I made a backup of my libraries before testing the latest development version.
• I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

1. I get errors while searching in different databses. Did API's change? Are some search querys correct? Some do work like :

Appendix

Searching in many databses fails.

Log File

org.jabref.logic.importer.FetcherException: An internal parser error occurred while fetching from https://scholar.archive.org/search?q=wordpress&from=0&size=20&format=json
	at org.jabref@5.15.60000/org.jabref.logic.importer.SearchBasedParserFetcher.getBibEntries(Unknown Source)
	at org.jabref@5.15.60000/org.jabref.logic.importer.SearchBasedParserFetcher.performSearch(Unknown Source)
	at org.jabref@5.15.60000/org.jabref.logic.importer.PagedSearchBasedParserFetcher.performSearch(Unknown Source)
	at org.jabref@5.15.60000/org.jabref.logic.importer.SearchBasedFetcher.performSearch(Unknown Source)
	at org.jabref@5.15.60000/org.jabref.gui.importer.fetcher.WebSearchPaneViewModel.lambda$search$2(Unknown Source)
	at org.jabref@5.15.60000/org.jabref.gui.util.BackgroundTask$1.call(Unknown Source)
	at org.jabref@5.15.60000/org.jabref.gui.util.UiTaskExecutor$1.call(Unknown Source)
	at javafx.graphics@22.0.1/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
Caused by: org.jabref.logic.importer.ParseException: kong.unirest.core.json.JSONException: Invalid JSON
	at org.jabref@5.15.60000/org.jabref.logic.importer.util.JsonReader.toJsonObject(Unknown Source)
	at org.jabref@5.15.60000/org.jabref.logic.importer.fetcher.ScholarArchiveFetcher.lambda$getParser$0(Unknown Source)
	... 14 more
Caused by: kong.unirest.core.json.JSONException: Invalid JSON
	at org.jabref.merged.module@5.15.60000/kong.unirest.modules.gson.GsonEngine.newEngineObject(Unknown Source)
	at org.jabref.merged.module@5.15.60000/kong.unirest.core.json.JSONObject.<init>(Unknown Source)
	... 16 more

[github-actions]

👋 Hey @AkshithKumar97, looks like you’re eager to work on this issue — great! 🎉 It also looks like you don't know how to assign issues to yourself. Please read our CONTRIBUTING.md to find out how. It will also guide you in other aspects of contributing to JabRef.

[AkshithKumar97]

@koppor Could you please assign this issue to me? I’d like to work on it as my first contribution.

[github-actions]

👋 Hey @AkshithKumar97, looks like you’re eager to work on this issue — great! 🎉 It also looks like you don't know how to assign issues to yourself. Please read our CONTRIBUTING.md to find out how. It will also guide you in other aspects of contributing to JabRef.

[AkshithKumar97]

I’ve read the CONTRIBUTING.md guide and set up JabRef locally.
Could you please assign this issue to me so I can start working on it?

[github-actions]

👋 Hey @AkshithKumar97, looks like you’re eager to work on this issue — great! 🎉 It also looks like you don't know how to assign issues to yourself. Please read our CONTRIBUTING.md to find out how. It will also guide you in other aspects of contributing to JabRef.

[emilianosalatino]

I’ve read the CONTRIBUTING.md guide and set up JabRef locally. Could you please assign this issue to me so I can start working on it?

THE MANUAL SAYS YOU COMMENT WITH A SLASH TAG.. .TO GET IT ASSIGNED...

SORRY FOR CAPS.. KB BROKN

[AkshithKumar97]

/assign-me

[github-actions]

👋 Hey @AkshithKumar97, thank you for your interest in this issue! 🎉

We're excited to have you on board. Start by exploring our Contributing guidelines, and set up your local development workspace by following the steps in our workspace setup guidelines to get started smoothly.

For questions on JabRef functionality, you can consult the JabRef Guru. For questions related to the codebase, please start using DeepWiki.

In case you encounter failing tests during development, please check our developer FAQs!

Still facing issues or having more questions? Feel free to ask here on GitHub or on JabRef's Gitter chat. Please don't hesitate to open a (draft) pull request early on to show the direction you are heading towards if unsure.

Happy coding! 🚀

[emilianosalatino]

👋 Hey @AkshithKumar97, thank you for your interest in this issue! 🎉

We're excited to have you on board. Start by exploring our Contributing guidelines, and set up your local development workspace by following the steps in our workspace setup guidelines to get started smoothly.

For questions on JabRef functionality, you can consult the JabRef Guru. For questions related to the codebase, please start using DeepWiki.

In case you encounter failing tests during development, please check our developer FAQs!

Still facing issues or having more questions? Feel free to ask here on GitHub or on JabRef's Gitter chat. Please don't hesitate to open a (draft) pull request early on to show the direction you are heading towards if unsure.

Happy coding! 🚀

YEAY!!!

[AkshithKumar97]

Status Update:
The ACM fetcher code is implemented according to JabRef requirements, but the ACM Portal currently blocks all automated programmatic access (HTTP 403).

Manual import from ACM Portal is the current workaround.

Future Monitoring:
If ACM’s public API or access rules change or allow automated access in the future, the fetcher implementation should be revisited to restore this functionality.