tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of datasetjson and refsplitr — release velocity, themes, recent moves, and the top alternatives to consider.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
datasetjson reads and writes CDISC Dataset-JSON, the JSON replacement for SAS transport files in clinical-trial submissions. The package went from a thin reader in 2023 to a redesigned interface in 0.3.0 that targets the 1.1.0 schema, uses yyjsonr as its JSON backend, and exposes column metadata as first-class arguments. Development is contributor-driven inside the Atorus and pharmaverse orbit.
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.
datasetjson reads and writes CDISC Dataset-JSON, the JSON replacement for SAS transport files in clinical-trial submissions. The package went from a thin reader in 2023 to a redesigned interface in 0.3.0 that targets the 1.1.0 schema, uses yyjsonr as its JSON backend, and exposes column metadata as first-class arguments. Development is contributor-driven inside the Atorus and pharmaverse orbit.
The package's roadmap is not its own — it tracks a CDISC standard that is still moving, and 0.3.0 is what happens when the standard revises: object model, read and write paths, and JSON backend all changed together. Performance was addressed in the same pass, which matters because submission datasets are large enough that a slow serialiser is a real constraint.
The next significant release will most likely follow the next Dataset-JSON schema revision rather than an internal roadmap, given that 0.3.0 was driven entirely by the 1.1.0 update.
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.
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.
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.
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 datasetjson or refsplitr.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all datasetjson alternatives → · See all refsplitr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — 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.
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.
Top datasetjson alternatives in Analytics are ranked by recent ship velocity. Browse the "datasetjson alternatives" section above for the current picks, or visit /alternatives/datasetjson for the full list with editorial commentary on each.
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.