JabRef / JabRef/user-documentation

Splitting of "Add entry using PDFs"?

Open
#300 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
54
Forks
142
Avg merge
23h 56m
Merged PRs (30d)
12

Description

I have started to update the section entitled "Add entry using PDFs" (https://docs.jabref.org/collect/findunlinkedfiles).
In fact, most of it is about "Add PDFs to existing entries" (section entitled "Mass-link PDFs").
So, I propose to split this file into two files:

  • "Add entry using PDFs" (that will be short)
  • "Add PDFs to existing entries"

To my mind "Add PDFs to existing entries" will stay in the chapter "Collect" (it might be moved to the section "Organize")

Any thought?

PS: What does the following sentence means?
In the concrete case, \bibtexkey only may be the better option as the described citation key already contains the title.
(last sentence of the file).
Is it In the concrete case, \bibtexkey only may be the best option as the entry already contains the title.?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the findunlinkedfiles documentation page and compare the “Add entry using PDFs” and “Mass-link PDFs” sections. Split the content into the proposed “Add entry using PDFs” and “Add PDFs to existing entries” files or sections, decide whether the latter remains under Collect, and clarify the final \bibtexkey sentence.

Written by the indexing model from the issue text.

Assessment

Tech stack
latex
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.