← Back to home
Comparison · Analytics

datapack vs excluder

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

datapack vs excluder: at a glance

Featuredatapackexcluder
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesresearch-data, dataone, provenance, bagitsurvey-data, data-cleaning, r-package, qualtrics
Last editorial update1h ago44m ago
WebsiteVisit →Visit →

What is datapack?

The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since

datapack assembles heterogeneous data files and metadata into a single transportable bundle, serialised as an OAI-ORE resource map and BagIt archive, for deposit into repositories like DataONE. Its functional surface settled with the 1.3.x line, which made assembled packages editable rather than write-once. Since then the releases have been sparse and defensive: SHA-256 as the default checksum in 1.4.0, BagIt spec conformance in 1.4.1, and a 2025 patch that states outright it contains no new features.

Read the full datapack trajectory →

What is excluder?

A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.

excluder marks, checks, and excludes online-survey rows that fail quality criteria — duplicate responses, suspicious IP or geolocation, screen resolution, completion duration, preview rows. The mark_*/check_*/exclude_* verb trio and the column-renaming helpers are the whole public surface. Recent releases are dependency chasing and test robustness rather than new exclusion criteria.

Read the full excluder trajectory →

datapack vs excluder: editorial side-by-side

D
datapack
ANALYTICS
0.0

The DataONE bundler learned to edit packages in 2017 and has coasted on that ever since

◆ Current state

datapack assembles heterogeneous data files and metadata into a single transportable bundle, serialised as an OAI-ORE resource map and BagIt archive, for deposit into repositories like DataONE. Its functional surface settled with the 1.3.x line, which made assembled packages editable rather than write-once. Since then the releases have been sparse and defensive: SHA-256 as the default checksum in 1.4.0, BagIt spec conformance in 1.4.1, and a 2025 patch that states outright it contains no new features.

◆ Where it's heading

The arc runs from assembly to correctness of the resulting archive. Later releases keep tightening the metadata the resource map must carry — dc:creator always present, dcterms:modified always updated, the package correctly flagged as modified after any access-policy change — because a bundle whose provenance record is subtly wrong is worse than one that fails outright. The three-year gap between 1.4.1 and 1.4.2, and the latter's CRAN-note content, place this package firmly in preservation.

◆ Prediction

Expect the next release, if any, to be another CRAN-compliance patch rather than functional work. The 1.4.2 note that it contains no new features is the clearest statement in the feed about where this package sits.

E
excluder
ANALYTICS
0.0

A Qualtrics data-cleaning package that has been in maintenance mode since its CRAN acceptance.

◆ Current state

excluder marks, checks, and excludes online-survey rows that fail quality criteria — duplicate responses, suspicious IP or geolocation, screen resolution, completion duration, preview rows. The mark_*/check_*/exclude_* verb trio and the column-renaming helpers are the whole public surface. Recent releases are dependency chasing and test robustness rather than new exclusion criteria.

◆ Where it's heading

The package is stable and its maintenance load comes from things it does not control: the {iptools} package leaving CRAN, {tidyselect} deprecating the .data pronoun, IP-geolocation tests breaking when the underlying address data shifts. Much of that work is about staying installable, not about better exclusions. Note that several of these entries were backfilled into the feed within the same two-minute window and are not in version order.

◆ Prediction

The next release will most likely be another dependency or CRAN-check response rather than a new exclusion criterion, following the pattern of the last three.

Alternatives to datapack and excluder

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 datapack or excluder.

See all datapack alternatives → · See all excluder alternatives →

Recent activity from datapack and excluder

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

  1. 10mo agodatapackCRAN documentation and CI cleanup
  2. 1y agoexcluderInternet-dependent tests and examples made conditional
  3. 2y agoexcluderqualtrics_fetch2 dataset and tidyselect deprecation fixes
  4. 3y agoexcluderCRAN acceptance and graceful IP-lookup failure
  5. 3y agoexcluderdplyr 1.0.8 across()/is.na() compatibility fix
  6. 3y agoexcluderuse_labels(), rename_columns(), and orientation-agnostic resolution
  7. 3y agoexcluderSwaps iptools for ipaddress
  8. 4y agodatapackBagIt serialisation brought in line with the current spec
  9. 5y agodatapackSHA-256 becomes the default checksum algorithm
  10. 6y agodatapackResource map metadata guaranteed; removeRelationships() added
  11. 8y agodatapackupdateMetadata no longer drops package relationships
  12. 9y agodatapackAssembled data packages become editable in place

Frequently asked questions

What is the difference between datapack and excluder?

They serve adjacent needs but don't currently overlap on shipped themes. datapack and excluder 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 datapack better than excluder?

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

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

What are the best alternatives to excluder?

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