feat: support open reference at google scholar

[brandon-lau0]

Summary of Changes

This PR adds a new "Search Google Scholar" feature to JabRef, similar to the existing "Search ShortScience" functionality. The feature allows users to quickly search for a selected entry's title in Google Scholar directly from the main table's context menu. The search engines are moved under the "Search..." tab in the right click menu for better organization.

In addition, we make Google Scholar and Short Science links configurable in the Preferences tab, under a new section named "Search Engine URL Templates". One of the comments mentioned, in the issue, that "the URL should be configurable. Reason: We cannot maintain JabRef for all site URLs; and the list of sites might be oppionated." This allows users to customize their URL templates, such as adding additional query parameters like author or strings.

The following shows the link the user is directed to after clicking "Search Google Scholar".

Closes #12268.

Bullet Pointed List of Changes:

• Added new search Google Scholar option
• Moved search engines to a "Search" sub-menu in right click menu
• Allow "Search Google Scholar" and "Search Short Science" URLs to be configurable in Preferences under the "Search Engine URL Templates" section

Collaborators

@lydia-yan @yoasaaa @brandon-lau0 @FlyJoanne

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• Change in CHANGELOG.md described in a way that is understandable for the average user (if change is visible to the user)
• [/] Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• Screenshots added in PR description (if change is visible to the user)
• Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
• Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

[koppor]

Update following are wrong comments; the feature is about opening using the web browser

Please investigate org.jabref.logic.importer.fetcher.GoogleScholar and read on at https://devdocs.jabref.org/code-howtos/fetchers.html.

Also look at #7075

You can try to work on JabRef#695.

[jabref-machine]

Your code currently does not meet JabRef's code guidelines. We use Checkstyle to identify issues. You can see which checks are failing by locating the box "Some checks were not successful" on the pull request page. To see the test output, locate "Tests / Checkstyle (pull_request)" and click on it.

In case of issues with the import order, double check that you activated Auto Import. You can trigger fixing imports by pressing Ctrl+Alt+O to trigger Optimize Imports.

Please carefully follow the setup guide for the codestyle. Afterwards, please run checkstyle locally and fix the issues, commit, and push.

[koppor]

Small comment on the tests

(I currently don't have much time to dive into this PR, but wanted to give a little pice of work to move this PR forward)

[koppor]

Typically, this is done with mock and when. See other classes. Can you try this?

[brandon-lau0]

Yep, I removed the StubImporterPreferences and replaced it with mock.

[koppor]

@brandon-lau0 May I ask if you are going to continue to work on this? - There are merge conflicts to resolve and tests made properly. If not, it is allright for us; we can then ask another student to continue.

[brandon-lau0]

@brandon-lau0 May I ask if you are going to continue to work on this? - There are merge conflicts to resolve and tests made properly. If not, it is allright for us; we can then ask another student to continue.

Thank you for your patience. I just resolved the merge conflicts and the tests to use mocks.

[trag-bot]

@trag-bot didn't find any issues in the code! ✅✨

[jabref-machine]

JUnit tests of jablib are failing. You can see which checks are failing by locating the box "Some checks were not successful" on the pull request page. To see the test output, locate "Tests / Unit tests (pull_request)" and click on it.

You can then run these tests in IntelliJ to reproduce the failing tests locally. We offer a quick test running howto in the section Final build system checks in our setup guide.

[Yubo-Cao]

Great work! I have tried out your PR, and basically everything works.

[koppor]

I like the idea of preferences; therefore, this PR should be continued.

[brandon-lau0]

I like the idea of preferences; therefore, this PR should be continued.

Thank you for your feedback and for supporting the preferences feature! At this time, I won’t be able to continue working on this PR due to other commitments. I hope what I’ve done so far can serve as a useful starting point for further development. I appreciate the opportunity to contribute. Thank you!

[calixtus]

Hey @Yubo-Cao , are you maybe interested in finalizing this PR? This is maybe a low hanging fruit. Would be great for the students who have worked on this to see, that this gets into the code.

[jabref-machine]

You ticked that you modified CHANGELOG.md, but no new entry was found there.

If you made changes that are visible to the user, please add a brief description along with the issue number to the CHANGELOG.md file. If you did not, please replace the cross ([x]) by a slash ([/]) to indicate that no CHANGELOG.md entry is necessary. More details can be found in our Developer Documentation about the changelog.

[jabref-machine]

Your code currently does not meet JabRef's code guidelines. IntelliJ auto format covers some cases. There seem to be issues with your code style and autoformat configuration. Please reformat your code (Ctrl+Alt+L) and commit, then push.

In special cases, consider using // formatter:off and // formatter:on annotations to allow deviation from the code style.