← Back to home
Comparison · Analytics

datapack vs DoseFinding

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

datapack vs DoseFinding: at a glance

FeaturedatapackDoseFinding
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesresearch-data, dataone, provenance, bagitdose-response, mcp-mod, clinical-trials, model-averaging
Last editorial update1h ago1h 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 DoseFinding?

New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing

DoseFinding implements MCP-Mod and related dose-response methodology for clinical trial design and analysis. In 2024 it changed hands — Marius Thomas took over as maintainer, Novartis was recorded as copyright holder and funder, and the package moved to the openpharma GitHub organisation with roxygen documentation and a proper NEWS file. The two releases since have added substantive methodology: model averaging for dose-response fitting in 1.3-1, and conditional and predictive power for interim analyses in 1.4-1.

Read the full DoseFinding trajectory →

datapack vs DoseFinding: 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.

D
DoseFinding
ANALYTICS
0.0

New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing

◆ Current state

DoseFinding implements MCP-Mod and related dose-response methodology for clinical trial design and analysis. In 2024 it changed hands — Marius Thomas took over as maintainer, Novartis was recorded as copyright holder and funder, and the package moved to the openpharma GitHub organisation with roxygen documentation and a proper NEWS file. The two releases since have added substantive methodology: model averaging for dose-response fitting in 1.3-1, and conditional and predictive power for interim analyses in 1.4-1.

◆ Where it's heading

The pattern before the handover was maintenance — R-devel compliance, a bug fix, a link. After it, each release carries a named methodological addition with an acknowledged contributor, plus documentation to match: a longitudinal analysis vignette shipped alongside the interim power work. Housekeeping continues underneath, mostly clearing deprecated ggplot2 interfaces, aes_string in one release and qplot in the next.

◆ Prediction

Given the last two releases each added one method with a supporting vignette, expect the next to follow the same shape. Both additions so far extend the package beyond fixed dose-response fitting, so adaptive and interim methodology is the more likely direction.

Alternatives to datapack and DoseFinding

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

See all datapack alternatives → · See all DoseFinding alternatives →

Recent activity from datapack and DoseFinding

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

  1. 10mo agodatapackCRAN documentation and CI cleanup
  2. 1y agoDoseFindingConditional and predictive power for interim analyses
  3. 1y agoDoseFindingModel averaging arrives for dose-response fitting
  4. 1y agoDoseFindingPackage moves to openpharma under new maintainership
  5. 2y agoDoseFindingCompliance update for R-devel
  6. 3y agoDoseFindingpowMCTBinCount bug fix
  7. 4y agodatapackBagIt serialisation brought in line with the current spec
  8. 5y agodatapackSHA-256 becomes the default checksum algorithm
  9. 6y agodatapackResource map metadata guaranteed; removeRelationships() added
  10. 8y agodatapackupdateMetadata no longer drops package relationships
  11. 9y agodatapackAssembled data packages become editable in place

Frequently asked questions

What is the difference between datapack and DoseFinding?

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

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

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