Changelog

June 18, 2026

SCMS jobs go fully asynchronous

The headline this week is for editors and operators running busy SCMS sites: the job pipeline behind publish, checks, and converters is now fully decoupled and asynchronous. Reader also starts serving supplementary files directly, alongside another JATS release.

Curvenote SCMS

A fully decoupled job pipeline. Publish, checks, and converters now run asynchronously end-to-end on a dedicated queue — with retries, dependency chaining, and clean terminal-failure cascades. No more submissions stuck waiting on a dispatch round-trip.

Check-services maintenance mode. Platform admins can now put individual check services into maintenance from the extensions admin. Dependent controls show clear disabled-state tooltips, and the upload flow skips a check that’s in maintenance and continues — with an informational note — rather than blocking the submission.

Version history, now visible. The submission version popover now is shown for both works and submissions listings: status-coloured site chips, version tags on the work timeline, popovers trimmed to a “see all” view, and version labels on work details.

Faster ETL endpoints. The published-article API route is materially faster; ETL re-registration now unpublishes the stale copy first, so a re-extracted article never leaves an old version live; a new “exports exist” check ships; and word-count check messages now include the filename.

Figure 1:The version history popover surfaces a submission’s full timeline at a glance — status-coloured site chips, version tags, and version labels across both works and submissions listings.

Curvenote Reader

Reader’s shared rendering core picked up SCMS client-identity plumbing: every server-side fetch to the SCMS now identifies itself, and the article-listing transform sends the same headers — which, as a bonus, fixes article listings that weren’t appearing on preview submission pages.

openRxiv Labs — Curvenote Reader

In production at openRxiv Labs

The improvements below are live at openRxiv Labs, which uses Curvenote Reader for all bioRxiv and medRxiv content.

Supplementary files served directly. PDFs, datasets, and Office documents attached to preprints are now served straight through the openRxiv theme at a dedicated route — so download links for tables, figures, and appendices resolve to the source file instead of 404-ing or bouncing through the image optimizer.

JATS processing. Five fixes, all of which surface in Reader output:

  • Supplementary “media” files now render as download links instead of silently dropping.

  • JATS <statement> blocks become MyST proofs — theorems, lemmas, propositions carry through with their meaning intact.

  • Abstracts with richer title structures parse cleanly.

  • Nonstandard cross-reference types are accepted, so more in-article links resolve.

  • BibTeX export covers more citation fields.

Cleaner request logs. Every SCMS request from the openRxiv theme now carries an identifying Curvenote user-agent, so partners running their own SCMS can attribute traffic to the Reader app.

Curvenote Theme

Richer links. Citations can now surface figures inline, and links to Hugging Face, GEO, GitHub, and Figshare render as rich cards and previews.

Figure 2:Hovering a citation or an external link surfaces a rich preview card inline — figures from citations and previews for Hugging Face, GEO, GitHub, and Figshare.

Theme-server requests to the SCMS now send a descriptive user-agent and client headers, so it is now possible to attribute SCMS traffic to a specific theme app and runtime.

Curvenote Sites

Editors using the Sites extension get the same finished version popover on submission detail and listing views, and the activity feed now reflects the decoupled job pipeline — surfacing converter-task activities. The submissions listing date filter was refreshed too.