Using pre-publication openICPSR Projects#
Typically the AEA Data Editor team will access code and data provided by authors that is stored on openICPSR.
Cornell replicators: You will need to set up an openICPSR account using your Cornell email.
Basics of openICPSR#
Authors will create a draft deposit that contains the replication archive for their paper.
Each deposit is identified with a six digit number (
123456
)You will download the project and commit the code (but not the data) files to the corresponding Bitbucket repo.
Downloading from openICPSR#
The most convenient way to download the information is to use the LDI-specific script tools/download_openicpsr-private.py
(be sure to have set up your environment first).
Short version of call to script
While in your repository directory, open a (Git) Bash shell, and type
python3 tools/download_openicpsr-private.py 123456
which will download a file 123456.zip
. If this has not been done before, it will unzip it into a directory 123456
.
You may need to adjust python3
to be python
, depending on your environment.
Full options for script
python3 tools/download_openicpsr-private.py 123456 . mylogin@cornell.edu
where
.
indicates the directory to download the ZIP file to (here, the current directory)mylogin@cornell.edu
is the login you use on the openICPSR website (typically,netid@cornell.edu
)
See appendix on how to set up the environment to make the script simpler (i.e., allow the short form to run).
Log on to the openICPSR website by clicking on the
Replication package URL
link in JiraIf you get an error, the project has probably not been shared with you. Contact your supervisor.
If successfully logged on, you will be able to download the project from the “more” menu:
Reminders#
Normally, none of the actions below are technically possible, but you should nevertheless follow these guidelines:
Do not publish the openICPSR projects.
Do not upload files to the projects.
Do not share projects with others unless instructed otherwise.
Do not share screenshots with others
See Privacy section about expectations on privacy.