marquee
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
A side-by-side editorial comparison of metatools and pharmaversesdtm — release velocity, themes, recent moves, and the top alternatives to consider.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
metatools provides the utilities that build and check SDTM and ADaM datasets against their metadata in the pharmaverse. The 0.1.6 release in July 2024 is the substantive one: combine_supp() learned to handle zero-row supplemental data, to refuse QNAM columns already present in the source, and to route multiple QNAM values to the same IDVAR, alongside enhanced controlled-terminology checks and record-uniqueness verification. Nothing has shipped since.
pharmaversesdtm is the test-data layer every pharmaverse package now builds against.
The package ships example SDTM datasets and has grown one therapeutic area at a time — ophthalmology, oncology response criteria, vaccines, metabolic, neurology, and now lymphoma under Lugano 2014. Sibling packages keep moving their internal test data here, so its release notes double as a record of what the rest of the pharmaverse is building.
metatools provides the utilities that build and check SDTM and ADaM datasets against their metadata in the pharmaverse. The 0.1.6 release in July 2024 is the substantive one: combine_supp() learned to handle zero-row supplemental data, to refuse QNAM columns already present in the source, and to route multiple QNAM values to the same IDVAR, alongside enhanced controlled-terminology checks and record-uniqueness verification. Nothing has shipped since.
The package's development has been concentrated on one function, combine_supp(), which is where the messy realities of supplemental qualifiers surface — whitespace in join keys, empty supp datasets, colliding names. 0.1.6 also drew three first-time contributors, which is the healthiest signal in the history, but no release has followed. Sibling packages have meanwhile been dropping metatools as a dependency.
Without a release in two years the package looks stable rather than active; the plausible trigger is a controlled-terminology or dplyr change that forces the checks to be updated.
The package ships example SDTM datasets and has grown one therapeutic area at a time — ophthalmology, oncology response criteria, vaccines, metabolic, neurology, and now lymphoma under Lugano 2014. Sibling packages keep moving their internal test data here, so its release notes double as a record of what the rest of the pharmaverse is building.
Two kinds of work alternate: adding domains and biomarkers for a new indication, and making the existing data easier to reach — CSV copies under inst/extdata for non-R programmers, a datasets preview vignette, reference pages categorised by therapeutic area, variable-by-variable breakdowns. Consistency fixes against CDISC terminology and SDTM guidelines run through every release.
New therapeutic areas will keep arriving in step with the admiral extension packages that need them; the neurology and metabolic datasets landed just ahead of admiralneuro and admiralmetabolic needing them, and lymphoma looks like the next in that sequence.
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 metatools or pharmaversesdtm.
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
FedData has spent two major versions migrating US federal geodata off R's retiring spatial stack.
See all metatools alternatives → · See all pharmaversesdtm alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — pharmaverse, sdtm, clinical-trials — within Analytics. metatools and pharmaversesdtm 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. metatools and pharmaversesdtm 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 metatools alternatives in Analytics are ranked by recent ship velocity. Browse the "metatools alternatives" section above for the current picks, or visit /alternatives/metatools for the full list with editorial commentary on each.
Top pharmaversesdtm alternatives in Analytics are ranked by recent ship velocity. Browse the "pharmaversesdtm alternatives" section above for the current picks, or visit /alternatives/pharmaversesdtm for the full list with editorial commentary on each.