tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of dwctaxon and posteriordb — release velocity, themes, recent moves, and the top alternatives to consider.
A Darwin Core validator that went quiet for two years, then surfaced only to raise its R floor
dwctaxon edits and validates taxonomic data held in Darwin Core format, enforcing the referential rules that make a taxonomic database internally consistent. Its last real functional change was 2.0.3 in December 2023, which loosened an over-strict uniqueness requirement in column matching. The most recent entry is a development build two years later that does nothing but set a minimum R version and bump Roxygen.
A reference posterior database that hit 1.0 with a paper, and is now graded on the statistics it ships.
posteriordb distributes Bayesian models with data and reference posterior draws so inference algorithms can be benchmarked against a common target. It reached 1.0.0 alongside a published paper, and ships both R and Python access. Recent work is about the metadata around the draws — licences, machine-readable dataset descriptors, and additional summary statistics.
dwctaxon edits and validates taxonomic data held in Darwin Core format, enforcing the referential rules that make a taxonomic database internally consistent. Its last real functional change was 2.0.3 in December 2023, which loosened an over-strict uniqueness requirement in column matching. The most recent entry is a development build two years later that does nothing but set a minimum R version and bump Roxygen.
The visible arc is a package converging on correctness rather than growing. The 2.0.3 change is the most consequential: matching a reference column no longer demands that every value in it be unique, only that the matched values be — which is what makes dct_fill_col() usable on real taxonomic tables where scientificName legitimately repeats. Around it sits compliance work: an internet-connection and URL check added purely to satisfy CRAN policy, and examples reworked to restore user settings and skip deliberate errors.
The 2.0.3.9001 development stamp with an R >= 4.2.0 requirement suggests a 2.0.4 release is being prepared, most likely as maintenance rather than new validation rules. The two-year gap makes any stronger claim unsupported by the feed.
posteriordb distributes Bayesian models with data and reference posterior draws so inference algorithms can be benchmarked against a common target. It reached 1.0.0 alongside a published paper, and ships both R and Python access. Recent work is about the metadata around the draws — licences, machine-readable dataset descriptors, and additional summary statistics.
The database is maturing from a model collection into a citable benchmark asset: licence information per model, a Croissant metadata file for dataset discovery, and summary statistics like mean squared value and lag-1 autocorrelation that let users judge whether reference draws are good enough for their comparison. Earlier releases were about content and correctness; current ones are about making the content machine-readable and verifiable.
Further work should continue on draw-quality diagnostics and metadata rather than model count, since the last two releases both added ways to assess the reference draws instead of adding posteriors.
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 dwctaxon or posteriordb.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all dwctaxon alternatives → · See all posteriordb alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. dwctaxon and posteriordb 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. dwctaxon and posteriordb 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 dwctaxon alternatives in Analytics are ranked by recent ship velocity. Browse the "dwctaxon alternatives" section above for the current picks, or visit /alternatives/dwctaxon for the full list with editorial commentary on each.
Top posteriordb alternatives in Analytics are ranked by recent ship velocity. Browse the "posteriordb alternatives" section above for the current picks, or visit /alternatives/posteriordb for the full list with editorial commentary on each.