Some functions allowed users to read files by providing the path to their containing directory. As functionality for combining multiple files has been scaled back, this feature is less useful, but requires internal maintenance. For users who unzip their extract files, they can provide the direct path the decompressed files.
Additionally, microdata DDI files could be read through a zip archive, similarly to NHGIS extracts. However, DDI files are not provided in zipped format, and the ipums_ddi objects produced by doing point to data files that are not within the same containing zip archive, meaning that read_ipums_micro_*() functions often have difficulty finding the associated data file if the DDI file has been loaded through a zip archive. This functionality has also been deprecated, such that DDI files must be read with their direct file path.
Some functions allowed users to read files by providing the path to their containing directory. As functionality for combining multiple files has been scaled back, this feature is less useful, but requires internal maintenance. For users who unzip their extract files, they can provide the direct path the decompressed files.
Additionally, microdata DDI files could be read through a zip archive, similarly to NHGIS extracts. However, DDI files are not provided in zipped format, and the
ipums_ddiobjects produced by doing point to data files that are not within the same containing zip archive, meaning thatread_ipums_micro_*()functions often have difficulty finding the associated data file if the DDI file has been loaded through a zip archive. This functionality has also been deprecated, such that DDI files must be read with their direct file path.