← Back to home
Comparison · Analytics

datasetjson vs Tplyr

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

Shared themes:r-packagepharmaverse

datasetjson vs Tplyr: at a glance

FeaturedatasetjsonTplyr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-data, cdisc, json, r-packageclinical-trials, tables, traceability, r-package
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is datasetjson?

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.

Read the full datasetjson trajectory →

What is Tplyr?

Tplyr made clinical summary tables explain where every number came from.

Tplyr builds clinical summary tables through a layered grammar — count, descriptive statistics, and shift layers assembled onto a table object. The 1.0.0 release added a traceability metadata framework that lets a user ask which source rows produced any given cell, and later releases extended it to cases the first pass missed. The package is maintained by Atorus within the pharmaverse ecosystem.

Read the full Tplyr trajectory →

datasetjson vs Tplyr: editorial side-by-side

D
datasetjson
ANALYTICS
0.0

datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

T
Tplyr
ANALYTICS
0.0

Tplyr made clinical summary tables explain where every number came from.

◆ Current state

Tplyr builds clinical summary tables through a layered grammar — count, descriptive statistics, and shift layers assembled onto a table object. The 1.0.0 release added a traceability metadata framework that lets a user ask which source rows produced any given cell, and later releases extended it to cases the first pass missed. The package is maintained by Atorus within the pharmaverse ecosystem.

◆ Where it's heading

Post-1.0 work has been about completing the metadata story and filling gaps in layer composition rather than adding table types — metadata for missing subjects, add_anti_join(), missing-subject rows, data limiting, and fixes to nested count layers where an inner value appears under several outer groups. Releases cluster tightly after a major version, then go quiet, and the window ends with a patch issued days after the release it corrects.

◆ Prediction

Further releases will most likely continue closing traceability and nested-layer edge cases rather than introducing new layer types, following the pattern of both post-1.0 feature releases.

Alternatives to datasetjson and Tplyr

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 Tplyr.

See all datasetjson alternatives → · See all Tplyr alternatives →

Recent activity from datasetjson and Tplyr

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

  1. 1y agodatasetjsonDataset-JSON 1.1.0 support with a redesigned object model
  2. 2y agoTplyrMissing-subject metadata, add_anti_join(), and nested-layer fixes
  3. 2y agodatasetjsonReads and validates Dataset-JSON from URLs
  4. 2y agodatasetjsonInitial CRAN release
  5. 3y agoTplyrMetadata vignette fix and parenthesis hugging
  6. 3y agoTplyrDenominator logic fix ahead of CRAN release
  7. 3y agoTplyrReverse-dependency fix
  8. 3y agoTplyr1.0.0 introduces the traceability metadata framework

Frequently asked questions

What is the difference between datasetjson and Tplyr?

Both compete on the same themes — r-package, pharmaverse — within Analytics. datasetjson and Tplyr 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.

Is datasetjson better than Tplyr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. datasetjson and Tplyr 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.

What are the best alternatives to datasetjson?

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.

What are the best alternatives to Tplyr?

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