← Back to home
Comparison · Infra & APIs

artoo vs surveytidy

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

Shared themes:r-packages

artoo vs surveytidy: at a glance

Featureartoosurveytidy
SectorInfra & APIsInfra & APIs
Velocity score2.50.0
Sparks · 30d00
Top themesr-packages, clinical-trials, cdisc, data-conversionsurvey-statistics, tidyverse, dplyr-verbs, metadata-tracking
Last editorial update1h ago43m ago
WebsiteVisit →Visit →

What is artoo?

artoo makes any-to-any clinical dataset conversion lossless by construction.

artoo reads and writes SAS XPORT, CDISC Dataset-JSON, NDJSON, Parquet and RDS around one canonical metadata model, so a conversion between any two formats carries labels, CDISC types, lengths, display formats, controlled-terminology references and sort keys intact. It is pure R with no SAS or Java runtime. It reached CRAN at 0.1.1 and has spent 0.1.2 and 0.1.3 on the character-encoding edges.

Read the full artoo trajectory →

What is surveytidy?

surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.

surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.

Read the full surveytidy trajectory →

artoo vs surveytidy: editorial side-by-side

A
artoo
INFRA · APIS
2.5

artoo makes any-to-any clinical dataset conversion lossless by construction.

◆ Current state

artoo reads and writes SAS XPORT, CDISC Dataset-JSON, NDJSON, Parquet and RDS around one canonical metadata model, so a conversion between any two formats carries labels, CDISC types, lengths, display formats, controlled-terminology references and sort keys intact. It is pure R with no SAS or Java runtime. It reached CRAN at 0.1.1 and has spent 0.1.2 and 0.1.3 on the character-encoding edges.

◆ Where it's heading

Recent work is all about text that does not survive a format change. 0.1.3 adds an invalid_encoding dimension to artoo_checks() that flags bytes which are not valid UTF-8 before a writer aborts on them, accepts the SAS OEM/DOS encoding names, and gives the writers on_invalid = "translit" and "fold" so smart punctuation and accented characters resolve to pinned ASCII instead of failing. The fold tables ship as data specifically so the result is identical on every platform, which is the same determinism argument behind C-locale row sorting in 0.1.0.

◆ Prediction

The new WLATIN1-to-UTF-8 migration article and the width warning on write_xpt() point the next attention at length and truncation semantics rather than at additional formats. These notes name no further target format.

S
surveytidy
INFRA · APIS
0.0

surveytidy taught every dplyr verb to operate on a whole collection of surveys at once.

◆ Current state

surveytidy is the tidyverse-facing half of a two-package survey stack, wrapping survey design objects from surveycore so filter, mutate, select and the rest work on them while carrying variable labels, value labels and a transformation log alongside the data. The May release extended that verb surface to survey_collection, the abstraction surveycore uses to hold several surveys as one object, so a pipeline written once dispatches across every member.

◆ Where it's heading

The package is being built in two layers that arrive in order: vector-level transformations first, structural dispatch second. The make_* family in 0.4.0 handles the recoding that survey work actually consists of — labelled to factor, multi-level to dichotomous, scale reversal, valence flipping — with value labels propagating automatically. Collection support then applies data-masking, tidyselect, grouping, slicing and collapsing verbs per survey, with joins explicitly refused and a typed message reporting which surveys were skipped. Metadata fidelity is the recurring bug source: labels surviving across(), stale labels left behind by recoding, the transformation log keeping up with what the verbs did.

◆ Prediction

Joins are the one verb family that errors on collections, with users directed to join before constructing the collection, so that restriction is the clearest outstanding gap. The re-export of surveycore's collection constructors suggests the package is positioning itself as the single import users need, which points toward more re-exports as surveycore's stable API settles.

Alternatives to artoo and surveytidy

Other Infra & APIs 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 artoo or surveytidy.

See all artoo alternatives → · See all surveytidy alternatives →

Recent activity from artoo and surveytidy

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

  1. 28d agoartooEncoding checks and translit/fold modes for the writers
  2. 1mo agoartoonoLD check fix; codec unchanged
  3. 2mo agoartooInitial CRAN release after resubmission
  4. 2mo agoartooLossless any-to-any CDISC dataset conversion in pure R
  5. 2mo agosurveytidymutate() syncs metadata for across() recodes
  6. 3mo agosurveytidydplyr and tidyr verbs dispatch across survey collections
  7. 5mo agosurveytidyFive label-aware recoding functions for use inside mutate()

Frequently asked questions

What is the difference between artoo and surveytidy?

Both compete on the same themes — r-packages — within Infra & APIs. artoo 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 artoo better than surveytidy?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. artoo 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 Infra & APIs products to evaluate alongside.

What are the best alternatives to artoo?

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

What are the best alternatives to surveytidy?

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