← Back to home
Comparison · Analytics

datasetjson vs qualtRics

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

Shared themes:r-package

datasetjson vs qualtRics: at a glance

FeaturedatasetjsonqualtRics
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-data, cdisc, json, r-packagesurvey-data, api-client, qualtrics, ropensci
Last editorial update1h ago4h ago
WebsiteVisit →Visit →

What is datasetjson?

datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.

datasetjson reads and writes CDISC Dataset-JSON, the JSON replacement for SAS transport files in clinical-trial submissions. The package went from a thin reader in 2023 to a redesigned interface in 0.3.0 that targets the 1.1.0 schema, uses yyjsonr as its JSON backend, and exposes column metadata as first-class arguments. Development is contributor-driven inside the Atorus and pharmaverse orbit.

Read the full datasetjson trajectory →

What is qualtRics?

qualtRics moved its contact functions onto XM Directory days before the old endpoints died.

qualtRics is the R client for the Qualtrics v3 API — fetching survey responses, definitions, distributions, and contact lists into tidy data frames. Version 3.3.0 migrated all_mailinglists() and fetch_mailinglist() from the deprecated Research Core Contacts endpoints to XM Directory, ahead of Qualtrics retiring the old ones on June 30, 2026. Authentication and directory discovery are handled automatically, but the new endpoints return a different data shape, so column names changed. Before that, releases had been steady maintenance for two years, mostly around how survey response archives are unpacked.

Read the full qualtRics trajectory →

datasetjson vs qualtRics: editorial side-by-side

D
datasetjson
ANALYTICS
0.0

datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.

◆ Current state

datasetjson reads and writes CDISC Dataset-JSON, the JSON replacement for SAS transport files in clinical-trial submissions. The package went from a thin reader in 2023 to a redesigned interface in 0.3.0 that targets the 1.1.0 schema, uses yyjsonr as its JSON backend, and exposes column metadata as first-class arguments. Development is contributor-driven inside the Atorus and pharmaverse orbit.

◆ Where it's heading

The package's roadmap is not its own — it tracks a CDISC standard that is still moving, and 0.3.0 is what happens when the standard revises: object model, read and write paths, and JSON backend all changed together. Performance was addressed in the same pass, which matters because submission datasets are large enough that a slow serialiser is a real constraint.

◆ Prediction

The next significant release will most likely follow the next Dataset-JSON schema revision rather than an internal roadmap, given that 0.3.0 was driven entirely by the 1.1.0 update.

Q
qualtRics
ANALYTICS
0.0

qualtRics moved its contact functions onto XM Directory days before the old endpoints died.

◆ Current state

qualtRics is the R client for the Qualtrics v3 API — fetching survey responses, definitions, distributions, and contact lists into tidy data frames. Version 3.3.0 migrated all_mailinglists() and fetch_mailinglist() from the deprecated Research Core Contacts endpoints to XM Directory, ahead of Qualtrics retiring the old ones on June 30, 2026. Authentication and directory discovery are handled automatically, but the new endpoints return a different data shape, so column names changed. Before that, releases had been steady maintenance for two years, mostly around how survey response archives are unpacked.

◆ Where it's heading

This package's roadmap is set by Qualtrics, not by its maintainers, and the release history reads as a sequence of accommodations — endpoint changes, retired APIs, and edge cases in exported files. The team's own recurring theme is reducing surprise: caching was removed from fetch_survey() in 3.2.0 so results are never stale, error handling was standardized on retry semantics, and column mappings were made inspectable via extract_colmap(). Feature additions, when they come, are new endpoints wrapped rather than new abstractions.

◆ Prediction

With the Contacts migration complete, the next likely work is bringing the remaining Research Core-era functions onto XM Directory equivalents before Qualtrics retires more of the old surface.

Alternatives to datasetjson and qualtRics

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 datasetjson or qualtRics.

See all datasetjson alternatives → · See all qualtRics alternatives →

Recent activity from datasetjson and qualtRics

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

  1. 1mo agoqualtRicsMailing list functions migrated to the XM Directory API
  2. 11mo agoqualtRicsZip extraction handles more special characters in survey titles
  3. 1y agodatasetjsonDataset-JSON 1.1.0 support with a redesigned object model
  4. 1y agoqualtRicsFix for questions with both recoded values and variable naming
  5. 1y agoqualtRicsBuild and CI housekeeping alongside the 3.2.1 release
  6. 2y agoqualtRicsSurvey response caching removed from fetch_survey()
  7. 2y agodatasetjsonReads and validates Dataset-JSON from URLs
  8. 2y agodatasetjsonInitial CRAN release
  9. 3y agoqualtRicsArgument checking refactor and include_* NA fix

Frequently asked questions

What is the difference between datasetjson and qualtRics?

Both compete on the same themes — r-package — within Analytics. datasetjson and qualtRics 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 datasetjson better than qualtRics?

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

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

What are the best alternatives to qualtRics?

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