Conversation
- jabkit: document the new `git merge-driver` command and the new support for passing a shared-database (PostgreSQL) URL as input (JabRef/jabref#16838, JabRef/jabref#16970) - OCR: document EasyOCR, PaddleOCR, and AppleOCR as new selectable OCRmyPDF backends, alongside Tesseract and Docling (JabRef/jabref#17219) - Add the BASE (Bielefeld Academic Search Engine) and DNB (Deutsche Nationalbibliothek) catalogs to the online search fetcher list (JabRef/jabref#16530, JabRef/jabref#17070) - Add the Software Heritage (SWHID) fetcher to the "Add entry using an ID" page (JabRef/jabref#16849) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XtzicSVFTs29DBkudE3PrX
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can keep summaries lean with Findings visible per group, which tucks the rest behind a View link |
PR Summary by QodoDocument recent JabKit, OCR, and bibliography lookup features
AI Description
Diagram
High-Level Assessment
Files changed (4)
|
| # OCR | ||
|
|
||
| [OCR](https://en.wikipedia.org/wiki/Optical_character_recognition) (Optical Character Recognition) is defined as the electronic or mechanic conversion of images of typed, handwritten or printed text into machine-encoded text. Consequently, with this technology it is possible to add editable and searchable data to PDFs and other files in your Jabref library. OCR can be used via multiple tools and engines. Currently, JabRef supports two OCR engines: [OCRmyPDF](https://ocrmypdf.readthedocs.io/en/latest/) and [Docling](https://github.com/docling-project/docling). | ||
| [OCR](https://en.wikipedia.org/wiki/Optical_character_recognition) (Optical Character Recognition) is defined as the electronic or mechanic conversion of images of typed, handwritten or printed text into machine-encoded text. Consequently, with this technology it is possible to add editable and searchable data to PDFs and other files in your Jabref library. OCR can be used via multiple tools and engines. Currently, JabRef supports [OCRmyPDF](https://ocrmypdf.readthedocs.io/en/latest/) (with a selectable OCR backend: Tesseract, EasyOCR, PaddleOCR, or AppleOCR) and [Docling](https://github.com/docling-project/docling). |
There was a problem hiding this comment.
Not a joke — it's real as of 5 days ago: JabRef/jabref#17219 ("Add OCRmyPDF plugins as new engines support (EasyOCR, PaddleOCR, AppleOCR)") added APPLEOCR as a selectable value in EngineSelection, alongside TESSERACT, EASYOCR, and PADDLEOCR, wired into OcrEngineFactory to run through OCRmyPDF's appleocr plugin. It shows up in the "OCR engine" dropdown in File → Preferences → OCR on current main.
Happy to drop it from this PR if it's considered out of scope / not ready for users yet — let me know and I'll push an update.
Generated by Claude Code
| * JabRef also **auto-detects the path automatically** whenever you change the selected engine in the dropdown, you don't need to trigger this manually. When you switch engines, JabRef tries the following commands, in order, and fills in the path field with the first one that works: | ||
|
|
||
| **For OCRmyPDF:** | ||
| **For Tesseract, EasyOCR, PaddleOCR, and AppleOCR** (all run through OCRmyPDF, so they share the same path): |
There was a problem hiding this comment.
Same source as the AppleOCR one above: JabRef/jabref#17219, merged 2026-09-26, adds PADDLEOCR to EngineSelection (identifier ocrmypdf_paddleocr, run via OCRmyPDF's PaddleOCR plugin). It's a real option in the current "OCR engine" dropdown alongside Tesseract, EasyOCR, and AppleOCR.
Let me know if you'd rather hold off documenting these three until they've had more real-world testing — happy to scope this PR down to just Tesseract/Docling if so.
Generated by Claude Code
Pull Request Description
Summary
Automated monthly review of the JabRef user-documentation against user-facing changes merged into
JabRef/jabrefmain over the past month (2026-09-01 to 2026-09-30). This is a low-risk, docs-only update — no code changes. Four pages were updated to cover features that shipped recently but were missing from the docs:en/jabkit.md— added the newjabkit git merge-drivercommand and the new support for passing a PostgreSQL shared-database URL as input to anyjabkitcommand.en/advanced/OCR.md— updated the OCR engine list: the "OCR engine" dropdown now offers Tesseract, EasyOCR, PaddleOCR, and AppleOCR (all via OCRmyPDF) in addition to Docling, not just "OCRmyPDF" and "Docling".en/collect/import-using-online-bibliographic-database.md— added the two new online-search catalogs: BASE (Bielefeld Academic Search Engine) and DNB (Deutsche Nationalbibliothek).en/collect/add-entry-using-an-id.md— added the new Software Heritage (SWHID) identifier-based fetcher.Each change was verified directly against the current
jabrefsource (enum/class names, CLI command wiring) rather than only against the CHANGELOG, to avoid documenting anything speculative.Steps to test
en/jabkit.md: compare againstjabkit --helpoutput on a currentmainbuild of jabkit — it should list agitsubcommand, andjabkit git merge-driver --helpshould match the documented setup snippet.en/advanced/OCR.md: open File → Preferences → OCR in a current build and confirm the OCR engine dropdown shows Tesseract, EasyOCR, PaddleOCR, AppleOCR, and Docling.en/collect/import-using-online-bibliographic-database.md: open View → Web search and confirm "BASE" and "DNB" appear in the catalog dropdown.en/collect/add-entry-using-an-id.md: open Library → New entry and confirm "Software Heritage" appears as an ID type.Related issues and pull requests
Closes _____
Documents JabRef/jabref#16838 (git merge-driver), JabRef/jabref#16970 (shared-database URL as jabkit input), JabRef/jabref#17219 (EasyOCR/PaddleOCR/AppleOCR engines), JabRef/jabref#16530 (BASE fetcher), JabRef/jabref#17070 (DNB fetcher), JabRef/jabref#16849 (Software Heritage/SWHID fetcher)
AI usage
Claude Code (model claude-sonnet-5), running as a scheduled automated monthly documentation review. All factual claims in this PR were cross-checked against the
jabrefsource code (fetcher classes, CLI command registration, OCR engine enum) rather than taken only from the CHANGELOG or commit messages.Checklist
Given this is a documentation-only change describing already-shipped, verified behavior, it should be low risk to review and merge quickly.
🤖 Generated with Claude Code
https://claude.ai/code/session_01XtzicSVFTs29DBkudE3PrX
Generated by Claude Code