Decision Records
Below, all “any decision records” for JabRef are listed. This list uses the TOC functionality of the Just the Docs Jekyll template.
For new ADRs, please use adr-template.md as basis. More information on MADR is available at https://adr.github.io/madr/. General information about architectural decision records is available at https://adr.github.io/.
Table of contents
- Use Markdown Any Decision Records
- Use Crowdin for translations
- Use slf4j together with log4j2 for logging
- Use Gradle as build tool
- Use MariaDB Connector
- Fully Support UTF-8 Only For LaTeX Files
- Only translated strings in language file
- Provide a human-readable changelog
- Use public final instead of getters to offer access to immutable variables
- Use Plain JUnit5 for advanced test assertions
- Use H2 as Internal SQL Database
- Test external links in documentation
- Handle different bibentry formats of fetchers by adding a layer
- Add Native Support for BibLatex-Software
- Separate URL creation to enable proper logging
- Query syntax design
- Mutable preferences objects
- Allow org.jabref.model to access org.jabref.logic
- Use regular expression to split multiple-sentence titles
- Implement special fields as separate fields
- Use Jackson to parse study.yml
- Keep study as a DTO
- Remove stop words during query transformation
- Localized Preferences
- Use # as indicator for BibTeX string constants
- Reviewdog findings are code reviews
- Use Java Native Access to Determine Default Directory
- Store Chats Alongside Database
- Synchronization with remote databases
- Store Chats in MVStore
- Return BibTeX string and CSL Item JSON in the API
- Use Citation Key for Grouping Chat Messages
- Exporting multiple entries to CFF
- Generate Embeddings Online
- Use Apache Commons IO for directory monitoring
- Use TextArea for Chat Message Content
- Use currently active tab in Select style (OO Panel) to decide style type
- RAG Architecture Implementation
- Use BibEntry.getId for BibEntry at indexing
- ADR Template