Please think of a researcher having a .bib file with 1000 entries and 850 PDFs on his hard disk. He wants to be "quickly" be able to manage that chaos.

Example:

Bib Entry A - no file attached (exists on hard disk)
Bib Entry B - no file attached (does not exist on hard disk, but entry has DOI set)
Bib Entry C - no file attached (does not exist on hard disk, entry has not DOI set, but DOI can be derived from title)
Bib Entry D - no file attached (does not exist on hard disk, entry has not DOI set, DOI cannot be determined)
Bib Entry E - file attached (exists on hard disk)
Bib Entry F - file attached (does not exist on hard disk, but entry has DOI set)
Bib Entry G - file attached (does not exist on hard disk, entry has not DOI set, but DOI can be derived from title)
Bib Entry H - file attached (does not exist on hard disk, entry has not DOI set, DOI cannot be determined)

"file attached" means that the BibEntry has a file field. F to H are rare special cases.

(DOI could also be another identifier. Go into the code of JabRef and learn about document downloaders)

When executing the file wizard, the result is as follows:

Bib Entry A - file attached
Bib Entry B - file attached (was downloaded automatically, entry has DOI set)
Bib Entry C - file attached (was downloaded automatically, entry has DOI set)
Bib Entry D - no file attached
Bib Entry E - file attached (exists on hard disk)
Bib Entry F - file attached (was downloaded automatically, entry has DOI set, content of file field updated)
Bib Entry G - file attached (was downloaded automatically, entry has DOI set, content of file field updated)
Bib Entry H - no file field anymore

Log contains INFO entries on the actions done.

Your first assumption does not hold as JabRef does not (or seldomly) stores the URL location (typically)

Can you craft an exmaple with concrete BibTeX entries A to H and respetive files or would you need support for that? You find some bib entries at https://github.com/JabRef/jabref/blob/master/src/test/resources/testbib/jabref-authors.bib.

You should find some existing test case in the source when searchign for unlinkedFilesTestBib.bib (use Ctrl+Shift+F)

https://github.com/JabRef/jabref/blob/master/src/test/resources/org/jabref/util/unlinkedFilesTestBib.bib

In other words

"Auto-link all file existing" is a fuller automation for the functionality described at https://docs.jabref.org/collect/findunlinkedfiles#for-several-pdf-files. (settings described at https://docs.jabref.org/finding-sorting-and-cleaning-entries/filelinks#auto-linking-files)
"Download all missing files" is a "for each" on the functionality behind the search glasses described at ttps://docs.jabref.org/getting-started#adding-a-full-text-document

Another example

The use case is an existing library, which should be quality-improved by JabRef.

Think about a .bib file with 1000 entries and a folder structure as follows:

Now, the user has nonono clue, if a PDF is linked in the bib file.

It is important that the Wizard can be rerun and the wizard (seems to) rember the old state.

I especially remind on VDI 90, S16.ff:

Inkrementelle Aufgabenbearbeitung ermögichen

(even though the text there describes a slightly different scenario. Nevertheless, I want to do some quality control on the process. Don't have the time to handle 4500 PDFs in one run)

Create "File Magic Wizard" #380

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions