← Back to home
Comparison · Infra & APIs

bulkreadr vs surveytidy

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

bulkreadr vs surveytidy: at a glance

Featurebulkreadrsurveytidy
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesdata-import, survey-data, labelled-data, spss-statasurvey-statistics, tidyverse, dplyr-verbs, metadata-tracking
Last editorial update1h ago2h ago
WebsiteVisit →Visit →

What is bulkreadr?

A bulk file reader became a labelled-survey-data toolkit, then went quiet

bulkreadr started as a way to read many files at once and turned into tooling for labelled survey data: SPSS and Stata importers that convert labelled variables to factors, generate_dictionary() for building data dictionaries, look_for() for searching variable descriptions, and imputation helpers. The most recent release does the opposite of adding — it pulls inspect_na() in-house to drop an external dependency.

Read the full bulkreadr 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 →

bulkreadr vs surveytidy: editorial side-by-side

B
bulkreadr
INFRA · APIS
0.0

A bulk file reader became a labelled-survey-data toolkit, then went quiet

◆ Current state

bulkreadr started as a way to read many files at once and turned into tooling for labelled survey data: SPSS and Stata importers that convert labelled variables to factors, generate_dictionary() for building data dictionaries, look_for() for searching variable descriptions, and imputation helpers. The most recent release does the opposite of adding — it pulls inspect_na() in-house to drop an external dependency.

◆ Where it's heading

Growth came in a burst across 2023, slowed to one release a year, and has now turned inward. The 2023 cadence added a format or a labelled-data function every few weeks; 2025 added a single Excel-to-CSV exporter; 2026 removed a dependency. The GitHub notes are cumulative — each release restates every prior version's changelog — which makes the feed look busier than the work is.

◆ Prediction

With inspectdf gone, the remaining Suggests-level dependencies are the obvious next targets for the same treatment. Nothing in these entries points to a new file format or a return to the 2023 pace.

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 bulkreadr 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 bulkreadr or surveytidy.

See all bulkreadr alternatives → · See all surveytidy alternatives →

Recent activity from bulkreadr and surveytidy

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

  1. 2mo agosurveytidymutate() syncs metadata for across() recodes
  2. 3mo agosurveytidydplyr and tidyr verbs dispatch across survey collections
  3. 5mo agobulkreadrinspect_na() brought in-house to drop the inspectdf dependency
  4. 5mo agosurveytidyFive label-aware recoding functions for use inside mutate()
  5. 1y agobulkreadrEvery Excel sheet exported to its own CSV file
  6. 2y agobulkreadrSix imputation strategies for fill_missing_values()
  7. 2y agobulkreadrData dictionaries and keyword search over labelled variables
  8. 2y agobulkreadrStata .dta import alongside SPSS
  9. 2y agobulkreadrSPSS import converting labelled variables to factors

Frequently asked questions

What is the difference between bulkreadr and surveytidy?

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

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

What are the best alternatives to bulkreadr?

Top bulkreadr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "bulkreadr alternatives" section above for the current picks, or visit /alternatives/bulkreadr 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.