JabRef lets you link up your entries with files of any type stored on your system. Thereby, it uses the field
file, which contains a list of linked files. Each entry can have an arbitrary number of file links, and each linked file can be opened quickly from JabRef. The fields
doi are used as links to documents on the web in the form of an URL or a DOI identifier, respectively (see URL and DOI in JabRef).
In BibTeX/biblatex terms, the file links are stored as text in the field
file. From within JabRef, however, they appear as an editable list of links accessed from the entry editor along with other fields.
If the "file" field is included in General fields, you can edit the list of external links for an entry in the Entry editor. The editor includes buttons for inserting, editing and removing links, as well as buttons for reordering the list of links.
JabRef offers the following directory settings:
Options → Preferences → Linked files, item Main file directory.
File → Library properties, items General file directory, and User-specific file directory.
One of these settings is required. Mostly the "Main file directory" is enough.
JabRef uses these 3 directories to search for the files: JabRef starts in the user-specific file directory, then the general file directory, and, finally, the main file directory
JabRef enables setting a directory per database. When sharing a library across multiple persons, each user might have a different directory. Either each user can set his directory in the "Main file directory". In case the group also shares papers and thus there are two directories (the private one and a group-shared one), one can set a directory within the library (the "General file directory"). In case a user has a different location of the shared folder (e.g., different paths on Linux and Windows), he can use the "User-specific file directory". This setting is persisted in the
bib file in a way that it does not overwrite the setting of another user. For this, JabRef uses the username of the currently logged in user (
-<loginname> is used as a suffix in the
jabref-meta field). So, both
aileen can set a different user-specific file directory.
If JabRef saves an attached file and my loginname matches the name stored in the
bib file, it chooses that directory. If no match is found, it uses the "General file directory" of the bib file. If that is not found, it uses the one configured at Options → Preferences → Linked files.
In some settings, the bib file is stored in the same directory as the PDF files. Then, one ignores all the above directories and enable "Search and store files relative to library file location". In this case, JabRef starts searching for PDF files in the directory of the
bib file. It is also possible to achieve this result by setting
. as "General file directory" in the library properties.
Relative file directories obviously only work in the library properties fo a bib file, e.g.
a.bib Library → Library properties → General file directory →
papers. Assume to have two bib files:
b.bib located in different directories:
a.bib located at
b.bib located at
X:\b.bib. When I click on the
+ icon in the general Tab of file
a.bib, the popup is opened in the directory
If you have a file within or below one of your file directories with an extension matching one of the defined external file types, and a name starting with (or matching) an entry's citation key, the file can be auto-linked. JabRef will detect the file and display a "link-add" icon in the entry editor, at the left to the filename. Click on the "link-add" icon to link this file to the entry.
The rules for which file names can be auto-linked to a citation key can be set up in Options → Preferences → Linked files, section Autolink files.
For an entry, if you want to download a file and link it to the entry, you can do this by clicking the Download button in the entry editor.
A dialog box will appear, prompting you to enter the URL. The file will be downloaded to your main file directory, named based on the entry's citation key, and finally linked from the entry.
It is possible to have greater flexibility in the naming scheme by using regular expressions for the search. In most cases, it should not be necessary though to adapt the given default.
If you open the preferences (Options → Preferences → Linked Files), you will find in the section Autolink files an option called "Use regular expression search". Checking this option will allow you to enter your own regular expression for search in the PDF directories.
The following syntax is understood:
* - Search in all immediate subdirectories excluding the current and any deeper subdirectories.
** - Search in all subdirectories recursively AND the current directory.
.. - The current directory and the parent directory.
[title] - All expressions in square brackets are replaced by the corresponding field in the current entry
[extension] - Is replaced by the file-extension of the field you are using.
All other text is interpreted as a regular expression. But caution: You need to escape backslashes by putting two backslashes after each other to not confuse them with the path-separator.
The default for searches is
**/.*[citationkey].*\\.[extension]. As you can see this will search in all subdirectories of the extension-based directory (for instance in the PDF directory) for any file that has the correct extension and contains the citation key somewhere.
There are several ways to open an external file or web page. In the entry table, you can click on the PDF icon to open the PDF. In case there are multiple PDFs linked, always the first one is opened. You can also right-click on the line of the entry in the entry table and select "Open file". There is also a keyboard shortcut for this: In the default setting, this is
F4, but it can also be customized.
To access any of an entry's links, click on the icon with the right mouse button (or
Ctrl + Click on Mac OS X) to bring up a menu showing all links.
In general, there is no need to change the settings of external file types. So, this setting is for advanced users. See Manage external file types.