Skip to content

Describe the conversion of special fields stored as keywords #684

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.

Sign up for GitHub

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

Open
koppor wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Describe the conversion of special fields stored as keywords #684

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fdfd6f4
Describe the conversion of special fields stored as keywords
koppor Sep 7, 2026
2dd95f2
Mention that declined conversions are remembered
koppor Sep 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions en/finding-sorting-and-cleaning-entries/specialfields.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,3 +62,5 @@ The way the special fields are stored in the libraries can be set in **File →
* With _Write values of special fields as separated fields_ (default configuration since version 5.2)_,_ each special field is stored in a separate field of the entry.
* With _Synchronize with keywords_ enabled, the values of the special fields are stored twice: in a separated field and as a keyword. Each change in a special field is reflected in the keyword field, and, vice versa, each change in a keyword leads to a change in the special field. Additionally, when loading a database or pasting a new entry, the keywords are used to set the special field values.
{% endhint %}

When you open a library that still stores special field values as keywords (for example `prio1` or `rank3`), JabRef offers to move them to separate fields. The dialog lists every conversion of the library to the current format; deselect a conversion to keep the data unchanged. JabRef remembers deselected conversions in the library and does not offer them again. To see the dialog again, remove the `skippedMigrations` comment from the `.bib` file.
Loading