Use the harmony() app to create as many successful harmonies between 2019 ASEC and 2019 ACS as possible. Successful submission of new harmonies will automatically create a new local harmony file at /harmony/harmonies/ASEC_2019__ACS_2019.R.
Safe usage of the harmony() app requires accurate and stable/final variable names and factor levels in the associated *_processed.fst microdata file. Best practice is to ensure the donor microdata is mature and free from errors before attempting to harmonize (i.e. confident ingestion of ASEC 2019 microdata).
In practice, you may become aware of a data error only after starting the harmonization process. If so, you will need to address/fix the issue by editing the relevant microdata processing .R script, re-run it to update the associated *_processed.fst and *_dictionary.rds files, call compileDictionary(), and then call harmony() to continue with harmonization.
If an erroneous/invalid harmony is committed to disk, you may need to manually delete the offending entry from the /harmony/harmonies/ASEC_2019__ACS_2019.R file and then re-open harmony() to then continue (safely) modifying the corrected harmony file.
Be sure to read the fusionData README section on how to "Harmonize variables".
Use the
harmony()
app to create as many successful harmonies between 2019 ASEC and 2019 ACS as possible. Successful submission of new harmonies will automatically create a new local harmony file at/harmony/harmonies/ASEC_2019__ACS_2019.R
.Safe usage of the
harmony()
app requires accurate and stable/final variable names and factor levels in the associated*_processed.fst
microdata file. Best practice is to ensure the donor microdata is mature and free from errors before attempting to harmonize (i.e. confident ingestion of ASEC 2019 microdata).In practice, you may become aware of a data error only after starting the harmonization process. If so, you will need to address/fix the issue by editing the relevant microdata processing .R script, re-run it to update the associated
*_processed.fst
and*_dictionary.rds
files, callcompileDictionary()
, and then callharmony()
to continue with harmonization.If an erroneous/invalid harmony is committed to disk, you may need to manually delete the offending entry from the
/harmony/harmonies/ASEC_2019__ACS_2019.R
file and then re-openharmony()
to then continue (safely) modifying the corrected harmony file.