> For the complete documentation index, see [llms.txt](https://docs.jabref.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jabref.org/v4/fields/specialfields.md). # Special Fields {% hint style="warning" %} This information is outdated. Please help to improve it. {% endhint %} Special fields offer the functionality * rate read papers * mark papers as relevant for the work * mark BibTeX entries as quality assured, and * prioritize unread papers. The main difference from the marked entry is that the rated entry is not floating by default and only highlight the number column. Thus, an entry may be both marked and rated. Each special field may be turned on and off in the settings. ## Types of Fields ### Ranking The aim is to add a functionality to set a range of “positive” ratings. JabRef offers a rank from one to five stars to rate papers. ### Relevance An entry may be marked as relevant. ### Quality Assured An entry may be marked as quality assured. The intention is to mark BibTeX entries, where a thorough checking of the field contents has been done. ### Priority One may prioritize entries from prio3 (low) to prio1 (high). The main intention is to prioritize unread papers. ## Storage in the BibTeX Entry Internally, each special field is stored in a separate BibTeX field. If “Write values of special fields as separate fields to BibTeX” is active, these fields are also written when the database is saved. JabRef also offers synchronizing the fields with keywords. This is enabled by the setting “Synchronize with keywords”. If this setting is active, then each change in a special field is reflected in the keyword field. Vice versa, each change in a keyword also leads to a change in the special field. Additionally, when loading a the database or pasting a new entry, the keywords are used to set the special field values. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.jabref.org/v4/fields/specialfields.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.