Refine "Update with bibliographic information from the web"
JabRef offers updating with bibliographic information from the web
The menu in JabRef offers this with identifiers only:
Ideas: Offer an "intelligent" all-in-one update
Tasks:
- Add "Update with bibliographic information from the web via entry data" below "Get bibliographic data from DOI/ISBN/... (fully automated)".
- Implement logic. Use
org.jabref.gui.mergeentries.multiwaymerge.MultiMergeEntriesView. - Update
Localization.lang("Get bibliographic data from %0", "DOI/ISBN/...")toLocaliization.lang("Update with bibliographic information via identifier(s)"). Also for the "fully automated". This is only about the localization.---
Note:
org.jabref.gui.mergeentries.multiwaymerge.MultiMergeEntriesView#addSource(java.lang.String, java.util.function.Supplier<org.jabref.model.entry.BibEntry>)should be used to add an entry to the merge dialog.titleis the name of the fetcher. The supplier is invoking the fetcher. By usingSupplier, the fetching can be done in the background (and does not block the UI)- List of fetchers is read from
org.jabref.logic.importer.WebFetchers#getEntryBasedFetchers - Only first result of
org.jabref.logic.importer.EntryBasedFetcher#performSearchshould be put into merge dialog
Note: Idea "Offer this functionality also in the usual JabRef menu" dropped, because I assume that users are OK with the choice to have identifiers available in the main menu only.
/assign-me
👋 Hey @aapatil2004, 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! 🚀
Hey if there was no any response from previous assignee, could you assign it to me
⚠️ Issue Already Assigned
Hi @D-Prasanth-Kumar, this issue is currently assigned to @aapatil2004.
[!NOTE] If no progress is made within 21 days, the issue will be automatically unassigned.
Options for contributors
- Wait for availability: The issue may become available if auto-unassigned
- Collaborate: You can ask the assignee if they want help
- Maintainer assistance: A maintainer can add you as co-assignee if appropriate
⏰ Assignment Reminder
Hi @aapatil2004, this is a friendly reminder about your assignment to this issue.
[!WARNING] This issue will be automatically unassigned in 11 days if there's no activity.
Remember that you can ask the JabRef Guru or DeepWiki about anything regarding JabRef. Additionally, our contributing guide has hints on creating a pull request and a link to our Gitter chat.
How to keep your assignment
If you are working on it, you can prevent automatic unassignment by:
- Submitting a draft pull request with your progress within 11 days
- Asking for the 📌 Pinned label if you need more time
We appreciate your contribution and are here to help if needed!
/assign-me
⚠️ Issue Already Assigned
Hi @CodeRishiX, this issue is currently assigned to @aapatil2004.
[!NOTE] If no progress is made within 21 days, the issue will be automatically unassigned.
Options for contributors
- Wait for availability: The issue may become available if auto-unassigned
- Collaborate: You can ask the assignee if they want help
- Maintainer assistance: A maintainer can add you as co-assignee if appropriate
/assign @CodeRishiX
👋 Hey @CodeRishiX, 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! 🚀
/unassign-me
📋 Assignment Update
Hi @CodeRishiX, you are no longer assigned to this issue.
Next steps
If you still want to work on this:
- Comment with
/assign-meto request reassignment - Ask a maintainer to assign you again
- If you're making progress, a maintainer can add the 📌 Pinned label to prevent future automatic unassignment
/assign-me
👋 Hey @tamojitdas, 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! 🚀
⏰ Assignment Reminder
Hi @tamojitdas, this is a friendly reminder about your assignment to this issue.
[!WARNING] This issue will be automatically unassigned in 11 days if there's no activity.
Remember that you can ask the JabRef Guru or DeepWiki about anything regarding JabRef. Additionally, our contributing guide has hints on creating a pull request and a link to our Gitter chat.
How to keep your assignment
If you are working on it, you can prevent automatic unassignment by:
- Submitting a draft pull request with your progress within 11 days
- Asking for the 📌 Pinned label if you need more time
We appreciate your contribution and are here to help if needed!
📋 Assignment Update
Hi @tamojitdas, due to inactivity, you have been unassigned from this issue.
Next steps
If you still want to work on this:
- Submit a pull request showing your current state. You will be automatically assigned again.
- Ask a maintainer to assign you again.
/assign-me
Thank you for your continued work in JabRef. At this point, you probably already know the basics and the important links. If not, our contributing guidelines is the place you should go to.
Happy coding! 🚀
/unassign-me
📋 Assignment Update
Hi @D-Prasanth-Kumar, due to inactivity, you have been unassigned from this issue.
Next steps
If you still want to work on this:
- Submit a pull request showing your current state. You will be automatically assigned again.
- Ask a maintainer to assign you again.
/assign-me
👋 Hey @Nusa942, 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! 🚀