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

Improve workflow after adding new entries #1456

Closed
tobiasdiez opened this issue May 27, 2016 · 2 comments
Closed

Improve workflow after adding new entries #1456

tobiasdiez opened this issue May 27, 2016 · 2 comments

Comments

@tobiasdiez
Copy link
Member

After adding or importing a new entry, my workflow usually looks like this:

  1. "Lookup DOI"
  2. "Get fulltext"
  3. "Get BibTeX data from DOI"
  4. Cleanup (automatic and manual)
  5. Compare bibtex data with data contained in the pdf (Journal, pages etc pp)

It would be fantastic if all these steps could be reduced to one step:
Click a button "Complete entry data", which then gets the doi, the fulltext and additional bibtex data, runs some predefined cleanups on the received data and then finally compares the result in the merge dialog to the original entry, enriched with the downloaded pdf view as a third pane.

@stefan-kolb
Copy link
Member

stefan-kolb commented May 29, 2016

Get fulltext now tries to find a DOI first if none exists. However, it does not write this DOI as the user might not want it inside the entry. So you can skip this step if one just wants the full text.

@github-actions
Copy link
Contributor

This issue has been inactive for half a year. Since JabRef is constantly evolving this issue may not be relevant any longer and it will be closed in two weeks if no further activity occurs.

As part of an effort to ensure that the JabRef team is focusing on important and valid issues, we would like to ask if you could update the issue if it still persists. This could be in the following form:

  • If there has been a longer discussion, add a short summary of the most important points as a new comment (if not yet existing).
  • Provide further steps or information on how to reproduce this issue.
  • Upvote the initial post if you like to see it implemented soon. Votes are not the only metric that we use to determine the requests that are implemented, however, they do factor into our decision-making process.
  • If all information is provided and still up-to-date, then just add a short comment that the issue is still relevant.

Thank you for your contribution!

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

No branches or pull requests

2 participants