← Back to home
Comparison · Analytics

datapack vs rbmi

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

datapack vs rbmi: at a glance

Featuredatapackrbmi
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesresearch-data, dataone, provenance, bagitclinical-trials, missing-data, multiple-imputation, pharmaverse
Last editorial update44m ago2h ago
WebsiteVisit →Visit →

What is datapack?

The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since

datapack assembles heterogeneous data files and metadata into a single transportable bundle, serialised as an OAI-ORE resource map and BagIt archive, for deposit into repositories like DataONE. Its functional surface settled with the 1.3.x line, which made assembled packages editable rather than write-once. Since then the releases have been sparse and defensive: SHA-256 as the default checksum in 1.4.0, BagIt spec conformance in 1.4.1, and a 2025 patch that states outright it contains no new features.

Read the full datapack trajectory →

What is rbmi?

Reference-based multiple imputation for trials, now shipping without Bayesian support by default.

rbmi implements reference-based multiple imputation for longitudinal clinical trial data with missing values — the estimand machinery regulators expect for handling intercurrent events and dropout. The consequential recent change was 1.3.0 moving rstan from a hard dependency to Suggests, which takes Bayesian imputation out of the default install. Since then the work has been documentation and nomenclature discipline: 1.6.1 standardized on MNAR over a mixed NMAR/MNAR vocabulary and deprecated the nmar.rm argument accordingly.

Read the full rbmi trajectory →

datapack vs rbmi: editorial side-by-side

D
datapack
ANALYTICS
0.0

The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since

◆ Current state

datapack assembles heterogeneous data files and metadata into a single transportable bundle, serialised as an OAI-ORE resource map and BagIt archive, for deposit into repositories like DataONE. Its functional surface settled with the 1.3.x line, which made assembled packages editable rather than write-once. Since then the releases have been sparse and defensive: SHA-256 as the default checksum in 1.4.0, BagIt spec conformance in 1.4.1, and a 2025 patch that states outright it contains no new features.

◆ Where it's heading

The arc runs from assembly to correctness of the resulting archive. Later releases keep tightening the metadata the resource map must carry — dc:creator always present, dcterms:modified always updated, the package correctly flagged as modified after any access-policy change — because a bundle whose provenance record is subtly wrong is worse than one that fails outright. The three-year gap between 1.4.1 and 1.4.2, and the latter's CRAN-note content, place this package firmly in preservation.

◆ Prediction

Expect the next release, if any, to be another CRAN-compliance patch rather than functional work. The 1.4.2 note that it contains no new features is the clearest statement in the feed about where this package sits.

R
rbmi
ANALYTICS
2.5

Reference-based multiple imputation for trials, now shipping without Bayesian support by default.

◆ Current state

rbmi implements reference-based multiple imputation for longitudinal clinical trial data with missing values — the estimand machinery regulators expect for handling intercurrent events and dropout. The consequential recent change was 1.3.0 moving rstan from a hard dependency to Suggests, which takes Bayesian imputation out of the default install. Since then the work has been documentation and nomenclature discipline: 1.6.1 standardized on MNAR over a mixed NMAR/MNAR vocabulary and deprecated the nmar.rm argument accordingly.

◆ Where it's heading

The package is optimizing for adoption friction over feature breadth. Dropping a compiled Stan dependency from the default install, deprecating a bespoke seed argument in favor of base set.seed(), and aligning lsmeans() behavior and weight naming with emmeans all point the same direction — behave like a conventional R package rather than a specialized one. Documentation work in 1.6.1 covering @return on every exported function and executable examples reads as preparation for validation scrutiny rather than user demand.

◆ Prediction

Given the FAQ vignette's validation statement and the recent documentation completeness pass, the next work is more likely qualification and estimand documentation than new imputation methods.

Alternatives to datapack and rbmi

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 datapack or rbmi.

See all datapack alternatives → · See all rbmi alternatives →

Recent activity from datapack and rbmi

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

  1. 22d agorbmiMNAR nomenclature standardized, documentation completed
  2. 10mo agodatapackCRAN documentation and CI cleanup
  3. 1y agorbmirstan demoted to Suggests, Bayesian imputation now opt-in
  4. 2y agorbmirbmi v1.2.5
  5. 4y agodatapackBagIt serialisation brought in line with the current spec
  6. 5y agodatapackSHA-256 becomes the default checksum algorithm
  7. 6y agodatapackResource map metadata guaranteed; removeRelationships() added
  8. 8y agodatapackupdateMetadata no longer drops package relationships
  9. 9y agodatapackAssembled data packages become editable in place

Frequently asked questions

What is the difference between datapack and rbmi?

They serve adjacent needs but don't currently overlap on shipped themes. rbmi 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 datapack better than rbmi?

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

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

What are the best alternatives to rbmi?

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