metasurvey.core— Reproducible Survey Data Processing with Step Pipelines

[mauroloprete]

Editor:
Submitting Author Name: Mauro Loprete
Submitting Author Github Handle: @mauroloprete
Other Package Authors Github handles: @natydasilva, @fabriciomsv
Repository: https://github.com/metasurveyr/metasurvey.core
Version submitted: 0.3.0
Submission type: Standard
Editor: TBD
Reviewers: TBD

Archive: TBD
Version accepted: TBD
Language: en

---

• Paste the full DESCRIPTION file inside a code block below:

Package: metasurvey.core
Title: Local Engine for Reproducible Survey Data Processing
Version: 0.3.0
URL: https://metasurveyr.github.io/metasurvey.core/,
    https://github.com/metasurveyr/metasurvey.core
BugReports: https://github.com/metasurveyr/metasurvey.core/issues
Authors@R:
    c(
        person(
            given = "Mauro",
            family = "Loprete",
            role = c("aut", "cre"),
            email = "mauro.loprete@fcea.edu.uy",
            comment = c(ORCID = "0000-0003-1560-0183")
        ),
        person(
            given = "Natalia",
            family = "da Silva",
            role = "aut",
            email = "natalia.dasilva@fcea.edu.uy",
            comment = c(ORCID = "0000-0002-6031-7451")
        ),
        person(
            given = "Fabricio",
            family = "Machado",
            role = "aut",
            email = "fabricio.mch.slv@gmail.com",
            comment = c(ORCID = "0009-0008-2653-9166")
        )
    )
Description: The processing engine of the 'metasurvey' ecosystem. Provides
    a step-based pipeline for reproducible survey data processing, building on
    the 'survey' package for complex sampling designs. Supports rotating panels
    with bootstrap replicate weights and a recipe system for reproducing data
    transformation workflows across survey editions.
License: GPL (>= 3)
Depends:
    R (>= 4.1)
Imports:
    data.table (>= 1.14.2),
    cli (>= 3.0.0),
    glue (>= 1.6.0),
    lifecycle (>= 1.0.0),
    jsonlite (>= 1.7.2),
    R6 (>= 2.5.0),
    survey (>= 4.2.1),
    methods,
    stats,
    utils
Suggests:
    tibble (>= 3.1.3),
    gt (>= 0.10.0),
    visNetwork (>= 2.0.9),
    htmltools (>= 0.5.0),
    foreign (>= 0.8-81),
    haven,
    eph,
    PNADcIBGE,
    ipumsr,
    openxlsx,
    rio (>= 0.5.27),
    here (>= 1.0.1),
    convey,
    digest,
    dplyr (>= 1.0.7),
    magrittr,
    parallel,
    testthat (>= 3.0.0),
    knitr (>= 1.33),
    rmarkdown (>= 2.11)
VignetteBuilder: knitr
Config/testthat/edition: 3
Encoding: UTF-8
Language: en-US
Roxygen: list(markdown = TRUE)
RoxygenNote: 8.0.0

Scope

• Please indicate which category or categories from our package fit policies this package falls under:

  • workflow automation

• Explain how and why the package falls under these categories (1-2 paragraphs):

  metasurvey.core provides the infrastructure to turn ad-hoc survey
  processing scripts into reproducible, shareable pipelines. Its lazy step
  pipeline (step_compute, step_recode, step_rename, step_remove,
  step_join, step_filter) operates within the context of a
  survey::svydesign/svrepdesign object, preserving sampling design
  metadata (weights, strata, PSUs, replicate weights) through every
  mutation, and is materialized via bake_steps(). The Recipe system
  bundles those pipelines into portable, versioned objects with metadata
  (survey type, edition, variable dependencies) that can be validated
  against a survey's schema before execution and applied to new editions
  of the same survey; the workflow system wraps
  svymean/svytotal/svyratio/svyby with provenance tracking, tying
  each estimate back to the recipe that produced its input data.

  Following the modularization discussed in this thread, metasurvey.core
  contains only the survey-agnostic engine: it runs fully offline. The
  registry REST client, the Shiny explorer, the ANDA download client, and
  the STATA transpiler now live in companion packages
  (metasurvey.explorer.backend, metasurvey.explorer.frontend,
  metasurvey.anda, metasurvey.fromstata), which reach core through an
  injectable backend-provider hook.

• Who is the target audience and what are scientific applications of this package?

  Government statistical offices (INEs) and academic researchers in
  economics, demography, and the social sciences working with household
  survey microdata. The primary use case is reproducible processing of
  recurring national surveys — Uruguay's ECH, Argentina's EPH, Brazil's
  PNAD-C, Chile's CASEN, or the US CPS.

  metasurvey.core is not a package for a single survey. Packages like
  ech, eph, PNADcIBGE, or lodown are tied to one survey and
  hardcode its variable names and conventions. metasurvey.core is
  survey-agnostic infrastructure: the abstraction layer (steps, recipes,
  workflows, provenance) that works for any complex survey. What makes
  it useful for a specific survey is a Recipe contributed by the
  community, not code baked into the package — so the ecosystem scales
  through community contributions. The bundled vignettes demonstrate this
  with a ECH 2023 sample (shipped with the package, runs offline) and
  reproducible examples for seven international surveys.

• Are there other R packages that accomplish the same thing? If so, how does yours differ?

  No single package covers the same ground; metasurvey.core integrates
  capabilities that individually overlap with existing tools:

  • survey (Lumley): the estimation engine. metasurvey.core wraps it
    and adds everything upstream — the pipeline that prepares microdata
    before svymean()/svytotal() can run.
  • srvyr: tidyverse syntax for survey objects, focused on the
    analysis phase. metasurvey.core focuses on the processing phase and is
    complementary.
  • recipes (tidymodels): general-purpose preprocessing for
    modeling. metasurvey.core's recipes are domain-specific: they carry
    survey metadata, validate against a survey's schema, and operate on
    design-aware survey objects, not bare data frames.
  • ech/eph/PNADcIBGE/lodown: survey-specific packages.
    metasurvey.core is the infrastructure layer underneath, usable with or
    without them.
  • targets: general workflow orchestration. metasurvey.core's
    workflow system is survey-specific, with design-aware estimation and
    provenance tied to recipes.

• Any other questions or issues we should be aware of?

  This submission continues metasurvey — Reproducible Survey Data Processing with Step Pipelines #752: following the editors' concern about
  package size, the original metasurvey monolith (now archived as
  metasurvey-legacy)
  was split into a modular ecosystem, and metasurvey.core is its base.
  Compared with the monolith reviewed in the original checks, core has no
  network, Shiny, or STATA code and no httr2/xml2/shiny dependencies;
  8 Imports total. We chose R6 because survey objects are inherently stateful (accumulating steps,
  holding mutable design objects) — happy to discuss this design choice.

Technical checks

Confirm each of the following by checking the box.

• I have read the rOpenSci packaging guide.
• I have read the rOpenSci statistical software guide and confirm this package is not a statistical software package.
• I have run pkgcheck::pkgcheck() locally and addressed all issues.
• I have run R CMD check with no errors, warnings, or notes.

Use of Generative AI

• Generative AI tools were used to produce some of the material in this submission.

  As described in detail earlier in this thread
  (2026-02-21): the architecture and all design decisions are the
  authors'; Claude Code assisted with test boilerplate, documentation
  drafts, packaging mechanics, and the modularization grunt work. The
  wording and translation of the English vignettes were AI-assisted
  and each English vignette discloses this in a footnote; the Spanish
  vignettes, the code, the examples, and all technical content are by the
  authors. Everything AI-assisted was human-reviewed.

Publication options

• Do you intend for this package to go on CRAN?
• Do you intend for this package to go on Bioconductor?
• Do you wish to submit an Applications Article about your package to Methods in Ecology and Evolution?

Code of conduct

• I agree to abide by rOpenSci's Code of Conduct during the review process and in maintaining my package should it be accepted.

[ropensci-review-bot]

Thanks for submitting to rOpenSci, our editors and @ropensci-review-bot will reply soon. Type @ropensci-review-bot help for help.

[ropensci-review-bot]

🚀

Editor check started

👋

[ropensci-review-bot]

Five most similar rOpenSci packages

• dataset 'Create Data Frames for Exchange and Reuse' (v0.4.5, released 2026-06-03)
• rixpress 'Build Reproducible Analytical Pipelines with 'Nix'' (v0.12.3, released 2026-05-19)
• eph 'Argentina's Permanent Household Survey Data and Manipulation
  Utilities' (v1.0.2, released 2024-06-23)
• tic 'Tasks Integrating Continuously: CI-Agnostic Workflow Definitions' (No releases to date.)
• nlrx 'Setup, Run and Analyze 'NetLogo' Model Simulations from 'R' via
  'XML'' (v0.4.6, released 2025-11-25)

Five most similar CRAN packages

• metasurvey 'Reproducible Survey Data Processing with Step Pipelines' (v0.0.21, published 2026-06-27)
• surveycore 'Core Survey Analysis Infrastructure' (v1.0.0, published 2026-06-08)
• weightflow 'Declarative API for Staged Survey Weights' (v0.2.0, published 2026-07-22)
• stepssurvey 'Analyse WHO STEPS Survey Data' (v0.1.0, published 2026-05-11)
• mpindex 'Multidimensional Poverty Index (MPI) via the Alkire-Foster
  Method' (v0.3.0, published 2026-06-15)

---

Matches are generated by the 'pkgmatch' package, based on inverse-term frequencies; see the main function documentation for details.

[ropensci-review-bot]

Checks for metasurvey.core (v0.3.1)

git hash: 551e404e

• ✔️ Package name is available
• ✔️ has a 'contributing' file.
• ✔️ uses 'roxygen2'.
• ✔️ 'DESCRIPTION' has a URL field.
• ✔️ 'DESCRIPTION' has a BugReports field.
• ✔️ Package has at least one HTML vignette
• ✔️ All functions have examples.
• ✔️ Repository has a website
• ✖️ Package fails continuous integration checks.
• ✔️ Package coverage is 86.3%.
• ✔️ R CMD check found no errors.
• ✔️ R CMD check found no warnings.
• 👀 Some goodpractice linters failed.
• 👀 Function names are duplicated in other packages
• 👀 Examples should not use \dontrun{} unless really necessary.

Important: All failing checks above must be addressed prior to proceeding

(Checks marked with 👀 may be optionally addressed.)

Package License: GPL (>= 3)

---

1. Package Dependencies

Details of Package Dependency Usage (click to open)

The table below tallies all function calls to all packages ('ncalls'), both internal (r-base + recommended, along with the package itself), and external (imported and suggested packages). 'NA' values indicate packages to which no identified calls to R functions could be found. Note that these results are generated by an automated code-tagging system which may not be entirely accurate.

type	package	ncalls
internal	base	1426
internal	metasurvey.core	299
internal	Matrix	22
internal	graphics	10
internal	grDevices	2
imports	stats	50
imports	utils	43
imports	data.table	42
imports	methods	18
imports	glue	14
imports	R6	13
imports	jsonlite	8
imports	survey	7
imports	lifecycle	5
imports	cli	NA
suggests	gt	11
suggests	knitr	1
suggests	tibble	NA
suggests	visNetwork	NA
suggests	htmltools	NA
suggests	foreign	NA
suggests	haven	NA
suggests	eph	NA
suggests	PNADcIBGE	NA
suggests	ipumsr	NA
suggests	openxlsx	NA
suggests	rio	NA
suggests	here	NA
suggests	convey	NA
suggests	digest	NA
suggests	dplyr	NA
suggests	magrittr	NA
suggests	parallel	NA
suggests	testthat	NA
suggests	rmarkdown	NA
linking_to	NA	NA

Click below for tallies of functions used in each package. Locations of each call within this package may be generated locally by running 's <- pkgstats::pkgstats(<path/to/repo>)', and examining the 'external_calls' table.

base

list (289), c (63), call (57), names (52), for (51), by (46), lapply (40), if (39), vapply (38), character (36), as.character (34), length (32), seq_along (28), is.null (22), as.list (21), paste0 (19), as.call (17), tryCatch (17), substitute (16), file (14), Filter (14), unlist (14), data.frame (13), setdiff (13), unique (13), as.numeric (11), version (11), args (10), deparse (10), eval (10), getOption (10), pretty (10), tolower (10), comment (9), environment (9), match.call (9), nrow (9), paste (9), source (9), switch (9), integer (8), print (8), search (8), unname (8), as.integer (7), do.call (7), labels (7), return (7), attr (6), class (6), get (6), is.call (6), is.na (6), quote (6), rep (6), logical (5), ordered (5), sub (5), Sys.time (5), which (5), all.vars (4), basename (4), format (4), gsub (4), ifelse (4), load (4), order (4), parent.frame (4), save (4), split (4), sum (4), deparse1 (3), intersect (3), mean (3), missing (3), nzchar (3), regmatches (3), round (3), seq_len (3), seq.int (3), sprintf (3), abs (2), all (2), any (2), as.Date (2), colnames (2), cut (2), expression (2), identical (2), inherits (2), is.character (2), is.list (2), is.name (2), isTRUE (2), ls (2), match (2), merge (2), message (2), new.env (2), proc.time (2), rank (2), raw (2), Reduce (2), row (2), sqrt (2), strsplit (2), url (2), all.names (1), as.name (1), as.POSIXlt (1), asNamespace (1), baseenv (1), cat (1), cumsum (1), date (1), drop (1), grep (1), is.atomic (1), is.numeric (1), is.symbol (1), list.files (1), mapply (1), match.fun (1), ncol (1), parse (1), regexec (1), regexpr (1), remove (1), replicate (1), rownames (1), sample.int (1), subset (1), tempfile (1), toupper (1), try (1), unclass (1), vector (1)

metasurvey.core

default_engine (28), recipe (20), get_data (18), get_type (13), get_edition (12), get_engine (12), canonicalize_step_call (10), step_quantile (7), generate_id (5), metadata_args (5), extract_time_pattern (4), get_steps (4), add_category (3), cat_recipes (3), compute (3), create_title (3), get_comments (3), get_formulas (3), get_type_step (3), lazy_default (3), metadata_recipe (3), read_file (3), recode (3), remove_category (3), add_recipe (2), apply_interval (2), cat_design (2), cat_design_type (2), collect_assigned_vars (2), default_weight_var (2), evaluate_cv (2), filter_recipes (2), filter_rows (2), find_dependencies (2), get_backend (2), get_design (2), get_distinct_recipes (2), get_follow_up (2), get_implantation (2), get_info_weight (2), load_survey (2), provenance (2), quantile_group (2), survey_tooltip (2), validate_weight_time_pattern (2), add_replicate (1), add_weight (1), agg_one (1), bake_recipes (1), bake_step (1), bake_steps (1), bake_steps_rotative (1), bake_steps_survey (1), bake_validate (1), cat_estimation (1), cat_estimation.cvystat (1), cat_estimation.default (1), cat_estimation.svyby (1), cat_estimation.svyratio (1), certify_recipe (1), check_inherits (1), config_survey (1), decode_step (1), default_categories (1), describe_class (1), encoding_recipe (1), escape_braces (1), extract_surveys (1), filter_workflows (1), find_workflows_for_recipe (1), get_metadata (1), get_recipe (1), get_weight (1), get_workflow_backend (1), group_dates (1), harmonize (1), has_design (1), has_recipes (1), has_steps (1), is_baked (1), is_blank (1), list_recipes (1), list_workflows (1), load_panel_survey (1), load_survey_example (1), load_survey.data.table (1), metasurvey_msg (1), msvy_abort (1), msvy_warn (1), new_step (1), parse_short_date (1), print.metasurvey_provenance (1), print.metasurvey_provenance_diff (1), print.Recipe (1), print.RecipeWorkflow (1), provenance_diff (1), provenance_to_json (1), provenance.data.table (1), provenance.default (1), provenance.Survey (1), publish_recipe (1), publish_workflow (1), rank_recipes (1), rank_workflows (1), read_recipe (1), read_workflow (1), recipe_category (1), recipe_certification (1), recipe_to_json (1), recipe_user (1), save_recipe (1), save_workflow (1), search_recipes (1), search_workflows (1), set_backend (1), set_data (1), set_edition (1), set_type (1), set_weight (1), show_engines (1), survey_empty (1), topo_sort_recipes (1), use_copy_default (1), validate_monthly (1), validate_time_pattern (1), weighted_quantile (1), workflow (1), workflow_from_list (1)

stats

step (11), filter (8), confint (6), qnorm (4), setNames (4), formula (3), dt (2), start (2), ts (2), as.formula (1), df (1), end (1), frequency (1), quantile (1), smooth (1), var (1), weights (1)

utils

data (35), timestamp (4), head (1), packageName (1), packageVersion (1), str (1)

data.table

copy (22), data.table (5), rbindlist (5), set (5), setnames (2), uniqueN (2), as.data.table (1)

Matrix

s (16), strata (4), index (2)

methods

initialize (13), is (3), new (2)

glue

glue (14)

R6

R6Class (13)

gt

px (9), gt (2)

graphics

title (5), text (3), arrows (1), pairs (1)

jsonlite

read_json (5), toJSON (3)

survey

cv (6), SE (1)

lifecycle

deprecated (5)

grDevices

cm (1), palette (1)

knitr

kable (1)

NOTE: Some imported packages appear to have no associated function calls; please ensure with author that these 'Imports' are listed appropriately.

---

2. Statistical Properties

This package features some noteworthy statistical properties which may need to be clarified by a handling editor prior to progressing.

Details of statistical properties (click to open)

The package has:

• code in R (100% in 27 files) and
• 3 authors
• 13 vignettes
• no internal data file
• 10 imported packages
• 110 exported functions (median 9 lines of code)
• 82 non-exported functions in R (median 12 lines of code)

---

Statistical properties of package structure as distributional percentiles in relation to all current CRAN packages
The following terminology is used:

• loc = "Lines of Code"
• fn = "function"
• exp/not_exp = exported / not exported

All parameters are explained as tooltips in the locally-rendered HTML version of this report generated by the checks_to_markdown() function

The final measure (fn_call_network_size) is the total number of calls between functions (in R), or more abstract relationships between code objects in other languages. Values are flagged as "noteworthy" when they lie in the upper or lower 5th percentile.

measure	value	percentile	noteworthy
files_R	27	92.3
files_vignettes	14	99.5
files_tests	38	99.3
loc_R	7440	98.3	TRUE
loc_vignettes	3694	99.0	TRUE
loc_tests	8665	99.3	TRUE
num_vignettes	13	99.1	TRUE
n_fns_r	192	96.9	TRUE
n_fns_r_exported	110	96.7	TRUE
n_fns_r_not_exported	82	96.2	TRUE
n_fns_per_file_r	7	90.1
num_params_per_fn	2	51.1
loc_per_fn_r	11	64.2
loc_per_fn_r_exp	9	58.1
loc_per_fn_r_not_exp	12	82.2
doclines_per_fn_exp	30	62.3
doclines_per_fn_not_exp	6	93.4
fn_call_network_size	403	95.0	TRUE

---

2a. Network visualisation

Click to see the interactive network visualisation of calls between objects in package

---

3. goodpractice and other checks

Details of goodpractice checks (click to open)

---

3b. goodpractice results

Test coverage with covr

Package coverage: 86.31

Cyclocomplexity with cyclocomp

The following functions have cyclocomplexity >= 15:

function	cyclocomplexity
step_join	41
workflow_table	38
extract_surveys	35
print.Recipe	32
bake_recipes	31
step_quantile	30
print.RecipeWorkflow	29
step_remove	29
validate_time_pattern	29
bake_step	28
extract_time_pattern	23
harmonize	23
step_rename	23
read_recipe	20
step_collapse	20
view_graph	19
cat_estimation.svyby	18
compute	18
print.metasurvey_provenance	18
topo_sort_recipes	17
evaluate_cv	16
bake_validate	15
get_metadata	15
parse_short_date	15
step_recode	15

Static code analyses with lintr

lintr found the following 1256 potential issues:

message	number of times
!all(x) is better than any(!x).	1
Avoid duplicate arguments in function calls.	2
Avoid implicit assignments in function calls.	7
Avoid undesirable operator :::.	113
Avoid undesirable operator <<-.	1
Construct file paths with file.path(...) instead of paste0(x, "/", y, "/", z).	1
expect_false(x) is better than expect_true(!x), and vice versa.	30
expect_gt(x, y) is better than expect_true(x > y).	27
expect_gte(x, y) is better than expect_true(x >= y).	15
expect_identical(x, y) is better than expect_true(x == y).	2
expect_length(x, n) is better than expect_equal(length(x), n)	74
expect_lt(x, y) is better than expect_true(x < y).	10
expect_lte(x, y) is better than expect_true(x <= y).	2
expect_named(x, n) is better than expect_equal(names(x), n)	1
expect_named(x, n) is better than expect_identical(names(x), n)	2
expect_null(x) is better than expect_true(is.null(x))	1
expect_s3_class(x, k) is better than expect_true(is.(x)) or expect_true(inherits(x, k)).	27
expect_s4_class(x, k) is better than expect_true(is(x, k)).	2
expect_type(x, t) is better than expect_true(is.(x))	21
Lines should not be more than 80 characters.	211
Pass is directly as a symbol to vapply() instead of wrapping it in an unnecessary anonymous function.	1
Pass step_collapse directly as a symbol to lapply() instead of wrapping it in an unnecessary anonymous function.	1
Pass step_compute directly as a symbol to lapply() instead of wrapping it in an unnecessary anonymous function.	3
Pass step_filter directly as a symbol to lapply() instead of wrapping it in an unnecessary anonymous function.	1
Pass step_join directly as a symbol to lapply() instead of wrapping it in an unnecessary anonymous function.	1
Pass step_recode_survey directly as a symbol to lapply() instead of wrapping it in an unnecessary anonymous function.	1
Pass step_remove directly as a symbol to lapply() instead of wrapping it in an unnecessary anonymous function.	1
Pass step_validate directly as a symbol to lapply() instead of wrapping it in an unnecessary anonymous function.	1
Prefer if (A) x else y to the less-readable if (!A) y else x in a simple if/else statement.	14
Prefer as.integer(x) to ifelse(x, 1L, 0L) if really needed.	20
Remove unnecessary c() of a constant.	13
Replace unnecessary c() by NULL or, whenever possible, vector() seeded with the correct type and/or length.	1
Supply an explicit value for stringsAsFactors for this code to work before and after R version 4.0.	2
toString(.) is more expressive than paste(., collapse = ", ").	55
Use ":" with fixed = TRUE here.	3
Use "1 workflows" with fixed = TRUE here.	1
Use "42" with fixed = TRUE here.	1
Use "A workflow with DOI" with fixed = TRUE here.	1
Use "age_cat" with fixed = TRUE here.	1
Use "anda" with fixed = TRUE here.	1
Use "annual" with fixed = TRUE here.	1
Use "atkinson" with fixed = TRUE here.	1
Use "bootstrap" with fixed = TRUE here.	1
Use "Calls" with fixed = TRUE here.	1
Use "Compute" with fixed = TRUE here.	1
Use "estimate" with fixed = TRUE here.	1
Use "Estimations" with fixed = TRUE here.	1
Use "Filter:" with fixed = TRUE here.	1
Use "gini" with fixed = TRUE here.	1
Use "Pipeline" with fixed = TRUE here.	1
Use "Print Test Recipe" with fixed = TRUE here.	1
Use "Print WF" with fixed = TRUE here.	1
Use "Printer" with fixed = TRUE here.	1
Use "printing" with fixed = TRUE here.	1
Use "Produces" with fixed = TRUE here.	1
Use "Recipes" with fixed = TRUE here.	1
Use "Remove:" with fixed = TRUE here.	1
Use "Rename:" with fixed = TRUE here.	1
Use "Requires" with fixed = TRUE here.	1
Use "Simple design" with fixed = TRUE here.	1
Use "svymean" with fixed = TRUE here.	2
Use "Test User" with fixed = TRUE here.	1
Use "W_ANO" with fixed = TRUE here.	1
Use "Weights" with fixed = TRUE here.	1
Use "WorkflowRegistry" with fixed = TRUE here.	1
Use deparse1(x) instead of paste(deparse(x), collapse = ...).	3
Use expect_identical(x, y) by default; resort to expect_equal() only when needed, e.g.	549
Use paste(), not paste0(), to collapse a character vector when sep= is not used.	3
Use x != y, not !(x == y).	1
Write multiple expectations like expect_true(A) and expect_true(B) instead of expect_true(A && B).	1

Other goodpractice checks

✖️ All internal functions are used
✖️ Package names in Title/Description are single-quoted
✖️ No misspelled words in documentation

---

4. Other Checks

Details of other checks (click to open)

✖️ The following 93 function names are duplicated in other packages:

• • add_category from metasurvey
• • add_recipe from workflows, worcs, metasurvey
• • add_replicate from metasurvey
• • add_weight from ricu, metasurvey
• • bake_recipes from metasurvey
• • bake_steps from metasurvey
• • cat_design from metasurvey
• • cat_design_type from metasurvey
• • certify_recipe from metasurvey
• • default_categories from metasurvey
• • evaluate_cv from metasurvey
• • extract_surveys from metasurvey
• • extract_time_pattern from metasurvey
• • filter_recipes from metasurvey
• • filter_workflows from metasurvey
• • find_workflows_for_recipe from metasurvey
• • get_backend from metasurvey
• • get_data from COINr, DSjobtracker, DTSEA, NeuroDecodeR, TBox, bonn, canvasXpress.data, cbsodataR, cimir, completejourney, dawaR, deckgl, ecb, exvatools, finnishgrid, ggPMX, gofigR, invivoPKfit, jtools, mcmsupply, mpathsenser, mxfda, qrmtools, r4googleads, radiant.data, radous, rbedrock, rchallenge, tidySEM, tsmp, ugatsdb, ukhsadatR, yfhist, yfscreen, istatR, StatsTFLValR, mapbayr, ggvis, tabs, tidyLPA, xpose, swissparl, pixieweb, optimall, metacoder, rsimsum, dynamite, basksim, ILORA, psborrow2, hespdiv, SUNGEO, metasurvey, insight, cohortBuilder, imf.data, cograph, EMC2, imdR, melodi
• • get_engine from metasurvey
• • get_follow_up from metasurvey
• • get_implantation from metasurvey
• • get_metadata from OpenSpecy, RGCxGC, RNeXML, SC2API, asdreader, bonn, chem16S, geogenr, gloBFPr, gwasrapidd, kofdata, bidux, ipumsr, NBDCtools, rKolada, irpfR, opencis, mpactr, metasurvey, Tplyr, bidser, rjd3workspace, melodi, tidyllm
• • get_recipe from metasurvey
• • get_steps from fitbitr, metasurvey
• • get_workflow_backend from metasurvey
• • group_dates from metasurvey
• • harmonize from StratifiedSampling, ltertools, benthos, metasurvey, spatstat.geom
• • has_design from metasurvey
• • has_recipes from metasurvey
• • has_steps from metasurvey
• • is_baked from metasurvey
• • lazy_default from metasurvey
• • list_recipes from metasurvey
• • list_workflows from metasurvey
• • load_panel_survey from metasurvey
• • load_survey from socialmixr, metasurvey
• • load_survey_example from metasurvey
• • PoolSurvey from metasurvey
• • provenance from provenance, dataset, metasurvey
• • provenance_diff from metasurvey
• • provenance_to_json from metasurvey
• • publish_recipe from metasurvey
• • publish_workflow from metasurvey
• • rank_recipes from metasurvey
• • rank_workflows from metasurvey
• • read_recipe from metasurvey
• • read_workflow from metasurvey
• • recipe from recipes, metasurvey
• • Recipe from metasurvey
• • recipe_category from metasurvey
• • recipe_certification from metasurvey
• • recipe_user from metasurvey
• • RecipeCategory from metasurvey
• • RecipeCertification from metasurvey
• • RecipeUser from metasurvey
• • RecipeWorkflow from metasurvey
• • remove_category from metasurvey
• • RotativePanelSurvey from metasurvey
• • save_recipe from metasurvey
• • save_workflow from metasurvey
• • search_recipes from metasurvey
• • search_workflows from metasurvey
• • set_backend from baskwrap, metasurvey
• • set_data from ashr, cccm, ggPMX, rhandsontable, tsmp, TrialEmulation, metasurvey
• • set_engine from parsnip, metasurvey
• • set_lazy_processing from metasurvey
• • set_use_copy from metasurvey
• • set_user_info from metasurvey
• • set_version from semver, metasurvey
• • set_workflow_backend from metasurvey
• • show_engines from parsnip, metasurvey
• • step_collapse from kerasnip
• • step_compute from metasurvey
• • step_filter from recipes, metasurvey
• • step_join from metasurvey
• • step_quantile from mapgl
• • step_recode from metasurvey
• • step_remove from metasurvey
• • step_rename from recipes, metasurvey
• • step_validate from metasurvey
• • steps_to_recipe from metasurvey
• • Survey from limonaid, metasurvey
• • survey_empty from metasurvey
• • survey_to_data_frame from metasurvey
• • survey_to_data.table from metasurvey
• • survey_to_datatable from metasurvey
• • survey_to_tibble from metasurvey
• • use_copy_default from metasurvey
• • validate_time_pattern from metasurvey
• • view_graph from metasurvey
• • workflow from TSPred, drake, workflows, metasurvey
• • workflow_from_list from metasurvey
• • workflow_table from metasurvey

---

Package Versions

package	version
pkgstats	0.2.4.1
pkgcheck	0.1.3.10

---

Editor-in-Chief Instructions:

Processing may not proceed until the items marked with ✖️ have been resolved.

This package has some noteworthy properties, see 'Package Statistics' details above.

[adamhsparks]

Hi @mauroloprete, thank you for submitting {metasurvey.core} to rOpenSci for review.

Could you please address the issues that {goodpractice} has flagged that are marked with the "✖️"?

Also, several of the issues that {lintr} identified are easily fixed and will help you also maintain the package in the future with many of the test improvements suggested due to better more informative messages from using the suggested tests.