Skip to main content
Ctrl+K
This is not yet fully debugged - report any issues!
Logo image
  • Introduction

Overview

  • Background

Preliminary Tasks

  • Pre-requisites
    • Pre-training tasks
    • Toolkit

Basics

  • Basic Concepts
  • Reproducible practices
  • The README template
  • Data citations and data availability statements
  • Generic data workflow
  • Assessing computational reproducibility
  • A guided walk through the Replication Report

AEA-specific Jira Workflow

  • AEA Jira workflow
    • Assigned
    • Creating a repository and running pipeline
    • In Progress
    • Preparing Part A - Preliminary Report
    • Preparing to Run Code (Part B)
    • Running Code (Part B)
    • Writing Report
    • Report completed
  • AEA: Revision reports after author resubmission
  • AEA-related meetings

Advanced AEA-related tasks

  • Checking Unassigned Jira Tickets
  • AEA: Reviewing and (Pre-) Approving Reports
    • Original Replication Report
    • Revision Report
    • Choosing a Recommendation
  • AEA: Submitting information back to the Editorial Office and to authors
    • Basic setup
    • Submitting to the JMS ScholarOne
    • Deleting restricted data
    • Submitting deposit-related information via openICPSR
  • AEA: Interfacing with openICPSR
    • AEA: Monitoring Pending openICPSR Changes
    • AEA: Publishing a deposit
    • Adding the article DOI to the openICPSR deposit metadata
  • AEA: Instructions for Papers and Proceedings checks

Running code

  • Guidelines for running code
  • Stata-related procedures
    • Using config.do in STATA
    • Running Code in Stata
    • Using scan_packages.do
    • Stata on Linux
    • Debugging Stata
  • R-related procedures
    • Using config.R in R
    • Running Code in R
    • Running R on Linux systems
    • Running R from other software
    • Debugging R
  • MATLAB-related procedures
    • Adding config.m to MATLAB and path names
    • Running MATLAB without the desktop GUI and with log file
    • Running Dynare from MATLAB
    • Debugging MATLAB-related problems
  • Python-related procedures
  • Julia-related procedures
  • Docker-related procedures
    • Docker on Windows
  • Mathematica-related procedures
  • Rare software
    • Ox-related procedures
    • Mosek

Sundry other guidance

  • External reproducibility checks

Appendix

  • Glossary
  • Setup Checklist
  • Privacy
  • Communication
  • Identifying differences between original manuscript and reproduction
    • Using screenshot and annotation tools on Windows
    • Using screenshot and annotation tools on macOS
    • Include Screenshots in the Report
  • Downloading Data
    • Using pre-publication openICPSR Projects
    • Alternate sources of data
    • Accessing privately provided data
    • Globus Transfers
    • Updating Replication Materials after Revisions
  • Access to Computers
    • Connecting to remote Windows servers
    • Connecting to remote Linux servers
    • Reproducibility Checks in Codeocean
    • Conducting reproducibility checks on WholeTale
    • Computing using Github Codespaces
    • Setting up your Bash environment
    • Additional setup instructions
  • Authentication-related issues
    • Bitbucket Authentication
    • openICPSR Authentication
  • Various templates for correspondence by AEA Data Editor team members
    • Preparing a Legacy Deposit for Updates by Authors
    • IPUMS Beta API request
    • Requesting Restricted-Access Data from Authors
    • Request for External Reproducibility Check (general)
    • Clarification regarding privately-provided restricted access files
  • Technical issues
  • Code of Conduct
  • Videoconferencing Rules and Etiquette
  • References
  • Older versions
  • Repository
  • Suggest edit
  • Open issue
  • .md

Submitting deposit-related information via openICPSR

Contents

  • Decision point?
  • Request revisions
  • Preparing Deposit for Publication
    • FOR ACCEPT WITH CHANGES
    • FOR ACCEPT:

Submitting deposit-related information via openICPSR#

Decision point?#

Note

If

  • [MCStatus] contains CA and [MCRecommendationV2] = Conditional Accept, or

  • [MCStatus] contains RR

then proceed to Request revisions.

Otherwise, if [MCStatus] contains CA and [MCRecommendationV2] = Accept or Accept with changes then proceed to Preparing Deposit for Publication.

Request revisions#

In principle, once the report is uploaded, the author will get the report with the requested revisions via ScholarOne. However, under the post-August 2020 workflow on openICPSR, the project may need to be unlocked for the author to make changes. To do so, proceed as follows:

  1. Open the issue on Jira.

  2. If the issue is still in Submitted to MC, then choose Post message to openICPSR transition, which will pop up with fields displayed. Wait here.

  3. Right-click on the [Replication package URL] field to open the openICPSR deposit.

  4. On openICPSR,

    • verify what the openICPSR Deposit Status is (top right corner) Deposit in Progress image.

    • if Deposit Status = Deposit in Progress, you are done on openICPSR. Go back to the Jira issue

    • if Deposit Status = Submitted, then

      • click on Change Status, choose Request revisions

  • in the pop-up, paste and submit the following lines:

We call this

the “Request-revisions-RR” message.

Use this template if the paper is in [RR] :

Revisions requested. Details in the full report, which you will receive via ScholarOne
or from the editor in charge of the paper.

> [NOTE] Replication packages may be published as soon as all requested changes to the deposit have been made. Please process any requested changes as soon as possible.

Use this template if the paper is in [CA] :

Revisions requested. Details in the full report, which you will receive via ScholarOne
in a few business days.

> [NOTE] We may publish replication packages as soon as all requested changes
to the deposit have been made. Please process any requested changes as soon
as possible.
  1. Back in the Jira issue, continue to transition the issue to Done.

Preparing Deposit for Publication#

FOR ACCEPT WITH CHANGES#

  1. Open the issue on Jira.

  2. Click on the Wait for response on openICPSR transition to Pending openICPSR changes.

  • In the pop-up, you should have all the necessary information.

    • Note: links in the pop-up window are not clickable: double-click, then use right-click to “Open in New Tab”.

    • If not already done: Replication package URL should point to openICPSR. If not, go to the final step.

    • Make a note of the issue number (in the URL) and the Manuscript Central identifier again.

Pop-up for transition to Pending openICSPR

  1. On openICPSR,

  • verify what the openICPSR Deposit Status is (top right corner) Deposit in Progress image.

  1. On openICPSR, if Deposit Status = Deposit in Progress

    • start a message in the Communication log:

      • with subject line: Please make the following changes (AEAREP-xxx) (replace with appropriate numbers)

      • Message content:

        • the contents of the portion of the report after “Action Items (openICPSR)”, but ONLY the action items.

        • then the following lines

We call this

the “Request-revisions-CA” message when Deposit in Progress is shown.

Details in the full report, which you will receive via ScholarOne in a
few business days. Please provide your response to the items listed above
via the openICPSR Project Communication log, specifying AEAREP-xxx.
Other items in the report may need to be addressed via ScholarOne.

Once all changes have been made, please change the status of your deposit to "Submit to AEA".


> [NOTE] Replication packages may be published as soon as all 
requested changes to the deposit have been made. Please process 
any requested changes as soon as possible.

(replace xxx with the issue number)

  1. On openICPSR, if Deposit Status = Submitted:

  • click on Change Status, choose Request revisions

  • in the pop-up,

    • paste the contents of the repository-specific portion of the report after “Action Items (openICPSR)”, but ONLY the action items.

    • then the following lines:

We call this

the “Request-revisions-CA” message when Submitted is shown.

Details in the full report, which you will receive via ScholarOne in a
few business days. Please provide your response to the items listed above
via the openICPSR Project Communication log, specifying AEAREP-xxx.
Other items in the report may need to be addressed via ScholarOne.

Once all changes have been made, please change the status of your deposit
to "Submit to AEA".


> [NOTE] We may publish replication packages as soon as all requested changes
to the deposit have been made. Please process any requested changes as soon
as possible.

(replace xxx with the issue number)

FOR ACCEPT:#

  1. Open the issue on Jira

  2. Click on the Prepare for publication transition

  3. In the pop-up, you should have all the necessary information.

    • Note: links in the pop-up window are not clickable: double-click, then use right-click to “Open in New Tab”.

    • If not already done: Replication package URL should point to openICPSR. If not, go to the final step.

    • Make a note of the issue number (in the URL) and the Manuscript Central identifier again.

  4. On openICPSR,

    • remove any RAs from the Share list (leave anybody else who is on there!)

    • (new!) verify what the openICPSR Deposit Status is (top right corner) Deposit in Progress image.

  5. On openICPSR, if Deposit Status = Deposit in Progress

    • start a message in the Communication log:

      • with subject line: Data and Code Deposit accepted for MCNumberXXX AEAREP-xxx (replace with appropriate numbers)

      • with body

We call this

the “Sign-off” message when author needs to Submit.

This data and code deposit is accepted.

Action items:

 - Author: Please change the status of your deposit to "Submit to AEA"
 - AEA Staff: update DOI, Vol, Iss, Year of related publication, then publish.
  1. On openICPSR, if Deposit Status = Submitted:

  • start a message in the Communication log:

    • with subject line: Data and Code Deposit accepted for MCNumberXXX AEAREP-xxx (replace with appropriate numbers)

    • with body

We call this

the “Final Sign-off” message.

This data and code deposit is accepted.

Action items:

 - Author: no further action required
 - AEA Staff: update DOI, Vol, Iss, Year of related publication, then publish.
  1. Back in the Jira popup, finalize by clicking OK. The issue will be moved to Pending Publication.

  2. You are not quite done yet!

    • You will receive an email from openICPSR.

    • forward the email to dataeditor-queue@aeapubs.org , but don’t press send yet!

    • manually add the issue number (AEAREP-xxx) into the subject line

    • delete anything in the body of the email before the “From:”

    • Now send the email.

    • This will add the message to the Jira ticket.

ICPSR does not always successfully send out a notification email for the posting of the comment. If you don’t receive the email, as a last resort, simply copy and paste your ICPSR comment into the Jira ticket so that we have a record.

previous

Deleting restricted data

next

AEA: Interfacing with openICPSR

Contents
  • Decision point?
  • Request revisions
  • Preparing Deposit for Publication
    • FOR ACCEPT WITH CHANGES
    • FOR ACCEPT:

By Lars Vilhuber, Michael Darisse, Sofia Encarnación, Ilanith Nizard, Leonel Borja Plaza, Takshil Sachdev, Hyuk Son, Linda Wang, David Wasser, Meredith Welch

© Copyright 2018-2024.