r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
nodbi vs refsplitr
A side-by-side editorial comparison of nodbi and refsplitr — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:ropensci
nodbi vs refsplitr: at a glance
What is nodbi?
One document API over six databases, and every release is spent absorbing their JSON engines' churn
nodbi presents a single document-store interface — docdb_create, docdb_query, docdb_update — over SQLite, DuckDB, PostgreSQL, MongoDB, CouchDB and Elasticsearch. The engineering reality behind that abstraction is that each backend's JSON support keeps moving, and the releases show it: jsonb_tree adopted as RSQLite 2.4.4 exposes it, json_tree reworked for DuckDB 1.3.0, then avoided entirely for DuckDB listfields because it was too slow. The 0.11.0 release in late 2024 is the one that changed the contract, making docdb_query() return columns of a single consistent type.
What is refsplitr?
Author disambiguation for bibliometrics, still grinding on the hard part: which names are the same person.
refsplitr parses Web of Science reference records into tidy data and tries to resolve which author strings belong to the same researcher, then georeferences their institutional addresses for network and map visualizations. The active work is squarely on the disambiguation core: 1.2.3 continues refining the author grouping algorithm and 1.2.1 adjusted ORCID ID matching. Earlier, 1.2.0 replaced the address parsing algorithm and changed the default georeferencing option for author institutions.
nodbi vs refsplitr: editorial side-by-side
nodbi
0.0ANALYTICS
One document API over six databases, and every release is spent absorbing their JSON engines' churn
◆ Current state
nodbi presents a single document-store interface — docdb_create, docdb_query, docdb_update — over SQLite, DuckDB, PostgreSQL, MongoDB, CouchDB and Elasticsearch. The engineering reality behind that abstraction is that each backend's JSON support keeps moving, and the releases show it: jsonb_tree adopted as RSQLite 2.4.4 exposes it, json_tree reworked for DuckDB 1.3.0, then avoided entirely for DuckDB listfields because it was too slow. The 0.11.0 release in late 2024 is the one that changed the contract, making docdb_query() return columns of a single consistent type.
◆ Where it's heading
Two threads dominate. The first is performance, pursued backend by backend: fast direct NDJSON import moved from DuckDB-only to SQLite and PostgreSQL, query refactors chasing each DuckDB release, and the removal of expensive tree-walking where a cheaper path exists. The second is making results predictable — consistent column types, version checks on the database backend, clearer messages when a Postgres database does not exist yet or when column names contain the dots nodbi reserves for JSON paths.
◆ Prediction
Given that most recent releases are triggered by DuckDB and RSQLite version changes, the next one likely follows the same pattern — adopting a new JSON function or working around a slow one. The duplicate-_id handling added in 0.14.0 suggests NDJSON ingestion edge cases are the current active area.
refsplitr
5.0ANALYTICS
Author disambiguation for bibliometrics, still grinding on the hard part: which names are the same person.
◆ Current state
refsplitr parses Web of Science reference records into tidy data and tries to resolve which author strings belong to the same researcher, then georeferences their institutional addresses for network and map visualizations. The active work is squarely on the disambiguation core: 1.2.3 continues refining the author grouping algorithm and 1.2.1 adjusted ORCID ID matching. Earlier, 1.2.0 replaced the address parsing algorithm and changed the default georeferencing option for author institutions.
◆ Where it's heading
Development has narrowed to the two operations that determine whether the output is usable — grouping author name variants and resolving addresses to coordinates. Everything else has been shedding: the maptools dependency was removed once that package was deprecated, and visualization changes are mostly about surfacing records the pipeline could not resolve, as with plot_net_country() returning fixable_countries so users can correct and rerun. Release notes are terse and defer to NEWS, so the changelog itself carries little detail.
◆ Prediction
Expect further incremental passes on author grouping and ORCID matching rather than new outputs; that algorithm is the package's accuracy ceiling and the last several releases have all touched it.
Alternatives to nodbi and refsplitr
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 nodbi or refsplitr.
DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
webmockr
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul
crul took mocking back from webmockr and made it a property of the client itself
dendroNetwork
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all nodbi alternatives → · See all refsplitr alternatives →
Recent activity from nodbi and refsplitr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 28d agorefsplitrFurther refinement of the author grouping algorithm
- 29d agorefsplitrMinor fixes and ORCID matching edits
- 8mo agonodbijsonb_tree adopted; $in string queries and duplicate _id handling fixed
- 1y agonodbiDuckDB version parsing and listfields fix
- 1y agonodbidocdb_query reworked for DuckDB 1.3.0
- 1y agonodbiNDJSON writing delegated to DuckDB's internal function
- 1y agorefsplitrNew address parsing algorithm, changed georeferencing default
- 1y agonodbiQuery results get consistent column types; fast NDJSON import reaches SQLite and Postgres ⚡
- 1y agonodbiQuery and file-import speedups via newer DuckDB features
- 2y agorefsplitrUnresolved countries surfaced, maptools dependency dropped
- 6y agorefsplitrrOpenSci release v0.9.0
Frequently asked questions
What is the difference between nodbi and refsplitr?
Both compete on the same themes — ropensci — within Analytics. refsplitr is currently shipping more aggressively (velocity 5.0 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 nodbi better than refsplitr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. refsplitr is currently shipping more aggressively (velocity 5.0 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 nodbi?
Top nodbi alternatives in Analytics are ranked by recent ship velocity. Browse the "nodbi alternatives" section above for the current picks, or visit /alternatives/nodbi for the full list with editorial commentary on each.
What are the best alternatives to refsplitr?
Top refsplitr alternatives in Analytics are ranked by recent ship velocity. Browse the "refsplitr alternatives" section above for the current picks, or visit /alternatives/refsplitr for the full list with editorial commentary on each.