tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of datasetjson and dwctaxon — 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.
A Darwin Core validator that went quiet for two years, then surfaced only to raise its R floor
dwctaxon edits and validates taxonomic data held in Darwin Core format, enforcing the referential rules that make a taxonomic database internally consistent. Its last real functional change was 2.0.3 in December 2023, which loosened an over-strict uniqueness requirement in column matching. The most recent entry is a development build two years later that does nothing but set a minimum R version and bump Roxygen.
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.
dwctaxon edits and validates taxonomic data held in Darwin Core format, enforcing the referential rules that make a taxonomic database internally consistent. Its last real functional change was 2.0.3 in December 2023, which loosened an over-strict uniqueness requirement in column matching. The most recent entry is a development build two years later that does nothing but set a minimum R version and bump Roxygen.
The visible arc is a package converging on correctness rather than growing. The 2.0.3 change is the most consequential: matching a reference column no longer demands that every value in it be unique, only that the matched values be — which is what makes dct_fill_col() usable on real taxonomic tables where scientificName legitimately repeats. Around it sits compliance work: an internet-connection and URL check added purely to satisfy CRAN policy, and examples reworked to restore user settings and skip deliberate errors.
The 2.0.3.9001 development stamp with an R >= 4.2.0 requirement suggests a 2.0.4 release is being prepared, most likely as maintenance rather than new validation rules. The two-year gap makes any stronger claim unsupported by the feed.
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 dwctaxon.
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 dwctaxon alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. datasetjson and dwctaxon are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. datasetjson and dwctaxon are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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 dwctaxon alternatives in Analytics are ranked by recent ship velocity. Browse the "dwctaxon alternatives" section above for the current picks, or visit /alternatives/dwctaxon for the full list with editorial commentary on each.