← Back to home
Comparison · Analytics

ojoregex vs r-owidapi

A side-by-side editorial comparison of ojoregex and r-owidapi — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

ojoregex vs r-owidapi: at a glance

Featureojoregexr-owidapi
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themescriminal-justice, court-data, r-package, text-classificationopen-data, our-world-in-data, r-package, api-wrapper
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is ojoregex?

Oklahoma's court-data nonprofit maintains the regex layer that turns charge text into categories.

ojoregex is Open Justice Oklahoma's pattern library for classifying criminal charge descriptions from court records — the unglamorous translation layer between free-text charge fields and analysable categories. Its entire release history reached this feed as four tags published within three minutes, so the feed order reflects a backfill rather than a shipping cadence. Release notes are merge references rather than descriptions, which limits how much can be read from the changelog alone.

Read the full ojoregex trajectory →

What is r-owidapi?

The R client for Our World in Data found its search had been reading a tenth of the catalog.

owidapi is a small R client for Our World in Data, covering chart data retrieval, metadata, the full chart catalog, and search over it, with experimental Shiny output helpers. It is three releases old and the most recent one is almost entirely repair: the catalog function was silently truncating at 1000 rows because of a Datasette row cap, which meant search had been operating on a fraction of what exists.

Read the full r-owidapi trajectory →

ojoregex vs r-owidapi: editorial side-by-side

O
ojoregex
ANALYTICS
0.0

Oklahoma's court-data nonprofit maintains the regex layer that turns charge text into categories.

◆ Current state

ojoregex is Open Justice Oklahoma's pattern library for classifying criminal charge descriptions from court records — the unglamorous translation layer between free-text charge fields and analysable categories. Its entire release history reached this feed as four tags published within three minutes, so the feed order reflects a backfill rather than a shipping cadence. Release notes are merge references rather than descriptions, which limits how much can be read from the changelog alone.

◆ Where it's heading

What the notes do show is a package alternating between domain corrections and R tooling upkeep: a fix to property-crime matching in one release, dplyr select semantics in the next. That is the expected shape for a regex catalogue — accuracy work arrives as individual charge types get miscategorised in real analyses, and the rest is keeping the package installable against a moving tidyverse. Contributions come from a small internal team, and the vignette work referenced in the earliest tag suggests the pattern list doubles as documentation for analysts.

◆ Prediction

The visible pattern is incremental match fixes as charge types surface in use; the release notes carry too little detail to predict anything beyond that without reading the underlying pull requests.

R
r-owidapi
ANALYTICS
2.5

The R client for Our World in Data found its search had been reading a tenth of the catalog.

◆ Current state

owidapi is a small R client for Our World in Data, covering chart data retrieval, metadata, the full chart catalog, and search over it, with experimental Shiny output helpers. It is three releases old and the most recent one is almost entirely repair: the catalog function was silently truncating at 1000 rows because of a Datasette row cap, which meant search had been operating on a fraction of what exists.

◆ Where it's heading

Development is about making a thin wrapper trustworthy against an upstream that moves without notice. The truncation fix pages through the catalog properly; a separate fix stops the function breaking when Our World in Data dropped a column, by parsing typed columns only when present. Tests moved to mocked responses, with a small live suite retained purely to detect schema drift and skipped on CRAN — a sensible design for a package whose main risk is that the API changes shape rather than that the code is wrong. The user-facing surface has not grown since the initial release; the work is in defending it.

◆ Prediction

On this pattern the next release is likelier to be another upstream-compatibility fix than new functionality, with the schema-drift tests the mechanism that surfaces it.

Alternatives to ojoregex and r-owidapi

Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either ojoregex or r-owidapi.

See all ojoregex alternatives → · See all r-owidapi alternatives →

Recent activity from ojoregex and r-owidapi

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 20d agor-owidapiCatalog was silently capped at 1000 charts; now paged in full
  2. 1mo agoojoregexPatch for dplyr select semantics
  3. 1mo agoojoregexojoregex v0.10.0
  4. 1mo agoojoregexNamespace prefixes fixed, plus a property-crime match bug
  5. 1mo agoojoregexFirst tagged release, carrying the whole development history
  6. 1y agor-owidapiRequest logic consolidated, with graceful catalog errors
  7. 1y agor-owidapiFirst release: data, metadata, catalog and search

Frequently asked questions

What is the difference between ojoregex and r-owidapi?

Both compete on the same themes — r-package — within Analytics. r-owidapi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is ojoregex better than r-owidapi?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. r-owidapi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to ojoregex?

Top ojoregex alternatives in Analytics are ranked by recent ship velocity. Browse the "ojoregex alternatives" section above for the current picks, or visit /alternatives/ojoregex for the full list with editorial commentary on each.

What are the best alternatives to r-owidapi?

Top r-owidapi alternatives in Analytics are ranked by recent ship velocity. Browse the "r-owidapi alternatives" section above for the current picks, or visit /alternatives/r-owidapi for the full list with editorial commentary on each.