Jabref Daily: Raw Query Support Lands for Systematic Literature Review Fetchers

Two merged pull requests extend raw query support to the Medline and Astrophysics Data System fetchers, continuing a pattern of adapting non-standard, multi-step search APIs for systematic literature reviews. Separately, three smaller fixes address search API rate limiting, drag-and-drop usability, and a UI overlap bug.

Duration: PT2M21S

Episode overview

This episode is a short developer briefing from Jabref Daily.

It explains recent repository work in plain language.

  • Show: Jabref Daily
  • Published: 2026-07-19T04:01:16Z
  • Audio duration: PT2M21S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good morning. It's July 19th, 2026, and this is Jabref Daily.

The main story today is the continued rollout of raw query support across JabRef's academic search fetchers, part of the ongoing systematic literature review effort.

Two fetchers got this treatment. In PR 16283, Loay Tarek Mostafa added raw query support to the Medline fetcher. Medline's search works in two steps: one call finds the IDs, another downloads the actual records, so a raw query can't just be dropped into a URL like normal. The fix overrides the raw search method…

Second theme: reliability fixes for search behavior. PR 16285 addresses a real production issue: Semantic Scholar search requests were missing a required API key header, which caused rate limiting errors. The fix brings search requests in line with how other Semantic Scholar methods already send that header, a…

Two smaller usability fixes rounded out the day. PR 16286 starts threading modifier key awareness into entry drag-and-drop, laying groundwork for distinguishing copy versus move operations between libraries. PR 16284 caps an autocomplete popup at five rows in the Entry Types preferences tab, fixing a case where the…

What's next: watch for the…

Nearby episodes from Jabref Daily

  1. Cleaning Up the Rough Edges
  2. Consolidating Rendering and Fixing Broken Defaults
  3. Metadata Import Gets a Deep Clean
  4. Data Correctness Over Convenience
  5. Import Pipeline Cleanup
  6. Trust and Rendering Fixes
  7. ArXiv Fetcher Gets a Rework
  8. Consistency Fixes Across Search and Data