metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
A side-by-side editorial comparison of DataSpaceR and epiparameter — release velocity, themes, recent moves, and the top alternatives to consider.
DataSpaceR's 1.0.0 rebuilt its query API and opened up HIV antibody sequence data.
The R client for the CAVD DataSpace reached 1.0.0 in July 2026 after five years of small fixes. The release removed the mAb grid filtering and view methods in favour of filtering an availableMabs object with data.table syntax, applied that pattern to every query method, and added a class for querying DAASH, the Database of Annotated Antibody Sequences for HIV-1. The August patch restored the LANL monoclonal-antibody metadata requests and batched BCR sequence queries.
epiparameter split its parameter library out of the package — and relicensed what remained.
epiparameter provides classes and methods for working with epidemiological parameter distributions — delays, offspring distributions, incubation periods — drawn from the published literature. As of 0.4.0 the library itself no longer lives here: the parameters moved to {epiparameterDB}, taken on as a dependency, leaving {epiparameter} as the code layer alone. The most recent release is a CRAN-driven patch.
The R client for the CAVD DataSpace reached 1.0.0 in July 2026 after five years of small fixes. The release removed the mAb grid filtering and view methods in favour of filtering an availableMabs object with data.table syntax, applied that pattern to every query method, and added a class for querying DAASH, the Database of Annotated Antibody Sequences for HIV-1. The August patch restored the LANL monoclonal-antibody metadata requests and batched BCR sequence queries.
The package is converging on one query idiom — build a filtered object, then fetch — instead of per-domain grid methods, and each class now accepts multiple studies or antibodies rather than one. The 1.0.1 patch suggests the rewrite dropped functionality that users noticed, and it was put back rather than redesigned.
With DAASH access in place and the query surface unified, the next work is most likely more sequence-domain coverage and follow-up fixes to the batched query paths introduced in 1.0.1.
epiparameter provides classes and methods for working with epidemiological parameter distributions — delays, offspring distributions, incubation periods — drawn from the published literature. As of 0.4.0 the library itself no longer lives here: the parameters moved to {epiparameterDB}, taken on as a dependency, leaving {epiparameter} as the code layer alone. The most recent release is a CRAN-driven patch.
Each release has clarified the boundary between the data and the tools that operate on it. 0.2.0 added coercion from {epireview} tables, 0.3.0 rewrote the classes and renamed much of the API, and 0.4.0 completed the separation while adding caching so loading the library stays cheap. Breaking changes have been frequent and deliberate rather than incidental.
With code and data separated, the two can version independently — expect parameter additions to appear in {epiparameterDB} releases while this package's changes stay focused on classes and methods.
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 DataSpaceR or epiparameter.
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
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.
See all DataSpaceR alternatives → · See all epiparameter alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. DataSpaceR 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DataSpaceR 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.
Top DataSpaceR alternatives in Analytics are ranked by recent ship velocity. Browse the "DataSpaceR alternatives" section above for the current picks, or visit /alternatives/dataspacer for the full list with editorial commentary on each.
Top epiparameter alternatives in Analytics are ranked by recent ship velocity. Browse the "epiparameter alternatives" section above for the current picks, or visit /alternatives/epiparameter for the full list with editorial commentary on each.