Add support for API features added in May 2024 #75
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Supports Time Use extracts with no vars or time use vars
Time use extracts can contain only time use variables
…alue of `rectangular_on`
…_spec() or tu_var_spec() field using add_to_extract()
…ged api-tests branch Merge branch 'api-docs' into api-dev # Conflicts: # R/api_define_extract.R
…d of sysreqs to install system dependencies in R-CMD-check
…oping that setup-r-dependencies takes care of that now
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These changes add support for new API features added in May 2024. Specifically, they add support for creating, submitting, checking status, and downloading extracts for IPUMS Time Use (ATUS, AHTUS, and MTUS) and IPUMS Health Surveys (NHIS and MEPS) data collections.
Along with the addition of support for these collections, these commits also change the functions that users should use to define extracts for microdata collections. Instead of using collection-specific functions like
define_extract_usa(), users should now usedefine_extract_micro()for all microdata collections, passing the desired collection to thecollectionargument of that function. This simplifies the documentation for defining microdata extracts, because there is a large degree of overlap in the options across microdata collections.