Document per-library keyword separator

[koppor]

🤖 Generated with Claude Code

Documents the new per-library keyword separator added in JabRef PR JabRef/jabref#16835. Low-risk documentation update.

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Document per-library keyword separator behavior

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Documents the library-specific keyword separator and its precedence over global preferences.
• Explains separator inference, fallback behavior, and clearing the library-specific setting.

High-Level Assessment

Documenting the setting alongside other General library properties is the clearest approach. A separate page or callout was considered unnecessary for this small, context-specific setting.

Files changed (1) +6 / -0

Documentation (1) +6 / -0

databaseproperties.mdExplain the per-library keyword separator +6/-0

Explain the per-library keyword separator

• Adds documentation for configuring a library-specific keyword separator. Clarifies precedence over global preferences, separator inference for existing keywords, fallback behavior, and how to remove the override.

en/setup/databaseproperties.md

[qodo-free-for-open-source-projects]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Keyword guidance omits override ✓ Resolved 🐞 Bug ≡ Correctness

Description

The new section establishes a library-level separator override, while the topic-specific keyword
guide still directs users only to the global Preferences setting. Users may therefore change a
global setting that has no effect on a library carrying its own separator.

Code

en/setup/databaseproperties.md[43]

+The character that separates keywords in the `keywords` field of this library, for example `,` or `;`. It overrides the keyword separator set in the Preferences dialog.

Evidence

The added documentation says the library separator overrides Preferences, whereas the primary
keyword guide says the separator is redefined in Preferences and provides no warning that a library
override can make that change ineffective.

en/setup/databaseproperties.md[41-45]
en/finding-sorting-and-cleaning-entries/keywords.md[11-18]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Update the keyword guide so it documents the per-library keyword separator and its precedence over the global preference.
## Issue Context
The Library properties page now documents a per-library override, but the main Keywords page still presents Preferences as the only way to redefine the separator. Mention the library setting, its precedence, and link to Library properties.
## Fix Focus Areas
- en/setup/databaseproperties.md[41-45]
- en/finding-sorting-and-cleaning-entries/keywords.md[11-18]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Tip of the day

💡 Did you know, you can add REVIEW.md to your repo root and Qodo follows it on every PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗