Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

crosswalk README file within product? #65

Closed
jGaboardi opened this issue Jul 15, 2020 · 5 comments
Closed

crosswalk README file within product? #65

jGaboardi opened this issue Jul 15, 2020 · 5 comments
Assignees
Labels
data product documentation Improvements or additions to documentation
Projects
Milestone

Comments

@jGaboardi
Copy link
Member

The questions was raised about whether to include a README.txt within a zipped archive for all crosswalk products. This is currently done with the original nhgis_blkYEAR-blkYEAR_g{e}{j} data available here.

@jGaboardi jGaboardi added documentation Improvements or additions to documentation data product labels Jul 15, 2020
@jGaboardi jGaboardi added this to the v0.0.7 milestone Jul 15, 2020
@jGaboardi jGaboardi self-assigned this Jul 15, 2020
@jGaboardi jGaboardi added this to In progress in v0.0.7 Jul 15, 2020
@jGaboardi jGaboardi removed this from In progress in v0.0.7 Jul 29, 2020
@jGaboardi jGaboardi removed this from the v0.0.7 milestone Jul 29, 2020
@jGaboardi jGaboardi added this to To do in v0.0.8 Jul 29, 2020
@jGaboardi
Copy link
Member Author

Options for storage/saving

  • compressed nhgis_blkYEAR-blkYEAR_g{e}{j}.csv and standard README.txt in a directory then zip the directory
  • standard nhgis_blkYEAR-blkYEAR_g{e}{j}.csv and standard README.txt in a directory then zip the directory
  • other?

@jGaboardi jGaboardi moved this from To do to In progress in v0.0.8 Jul 30, 2020
@jGaboardi jGaboardi added this to the v0.0.8 milestone Jul 30, 2020
@jGaboardi
Copy link
Member Author

Proposed workflow/content:

  • README.txt files stored in /resources/readme_files/
    • one for each source-target combination (same file for each state subset)
  • add upper-level function for generating data based on the /notebooks/generate-nation-and-states-*ipynb notebooks
    • include functionality to:
      • fetch the proper README.txt
      • create directory named {crosswalk} with {crosswalk}.csv and README.txt
      • zip the directory
  • revisit .csv - .csv.zip - .zip in xwalk_df_to_csv and xwalk_df_from_csv

@jGaboardi
Copy link
Member Author

jGaboardi commented Aug 3, 2020

product progress

  • nhgis_blk1990_blk2010_gj
    • nation
    • state-level
  • nhgis_blk1990_blk2010_ge
    • nation
    • state-level
  • nhgis_blk2000_blk2010_gj
    • nation
    • state-level
  • nhgis_blk2000_blk2010_ge
    • nation
    • state-level
  • nhgis_bgp1990_bg2010
    • nation
    • state-level
  • nhgis_bgp1990_tr2010
    • nation
    • state-level
  • nhgis_bgp1990_co2010
    • nation
    • state-level
  • nhgis_bgp2000_bg2010
    • nation
    • state-level
  • nhgis_bgp2000_tr2010
    • nation
    • state-level
  • nhgis_bgp2000_co2010
    • nation
    • state-level
  • decision add archives to ./testing_data/ ?
    • nhgis_blk1990_blk2010_gj.csvthis is currently nhgis_blk1990_blk2010_gj.zip
    • nhgis_blk1990_blk2010_gj.zipthis should be the zipped archive
    • nhgis_blk2000_blk2010_gj.csvthis is currently nhgis_blk1990_blk2010_gj.zip
    • nhgis_blk2000_blk2010_gj.zipthis should be the zipped archive
  • decision regarding original crosswalks vs. archives...
    • add archives to ../../crosswalks/?

@jGaboardi
Copy link
Member Author

retry with preprocessing step:

  • use shutil to zip up the original block stuff prior to running the blk-blk creation notebook.

@jGaboardi
Copy link
Member Author

Partially resolved via #72 --> continuing in #80.

@jGaboardi jGaboardi moved this from In progress to Done in v0.0.8 Aug 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data product documentation Improvements or additions to documentation
Projects
No open projects
v0.0.8
  
Done
Development

No branches or pull requests

1 participant