Skip to content
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

Add mass addition of bib information #372

Open
koppor opened this issue Nov 21, 2019 · 4 comments · May be fixed by JabRef/jabref#12025
Open

Add mass addition of bib information #372

koppor opened this issue Nov 21, 2019 · 4 comments · May be fixed by JabRef/jabref#12025

Comments

@koppor
Copy link
Owner

koppor commented Nov 21, 2019

In short: https://docs.jabref.org/advanced/how-to-expand-firstnames for many entries

We have
grafik

But we don't have following for all entries:

grafik

Maybe: Mass-cleanup of all entries:

Simple implementation:

  1. Determine ids (DOI and arxiv)
  2. For all entries: Fetch information from doi (and then arxiv) -- Read on at https://devdocs.jabref.org/code-howtos/fetchers.html to learn about the fetchers.
  3. For each change: merge entries dialog

Better implementation:

Step 3: Do not show popup. Just take longer string.

Better better implementation:

Step 3: Do not show popup. Use smart heuristics at merging.


I would propose to go with the "Better implementation"

@u7485624
Copy link

u7485624 commented Oct 22, 2023

Hello, I am a university student and am interested in working on this issue.

I have read the onboarding documents, and am ready to begin development.

@koppor
Copy link
Owner Author

koppor commented Oct 22, 2023

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.

@Arvinyuchen
Copy link

Hi, I was wondering if this issue still needs to be worked on. If so, I would be happy to pick it up!

@koppor
Copy link
Owner Author

koppor commented Oct 9, 2024

@Arvinyuchen Sure! Go ahead!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants