AEA Data Editor

FWIW, I added my (= AEA Data Editor) weight ⚖️ to argue for removal of unnecessary data collections. Thanks to all those who already reported this. The 🛞 are in motion.

I will continue working with ICPSR to improve the user experience, but you can help by describing your problems via the ICPSR helpdesk ("Contact Us" link at the bottom of the page).

To be clear: you need a REAL email address. ICPSR asks for registration (and I agree with that) so they can record that you agreed to the terms of use. "Free to download" does not mean "free to do anything with it", though we will always ensure that at a minimum, you can reproduce with it!

The real reason Hollywood uses "555" phone numbers | CBC Radio While watching movies or television shows, you’ve no doubt noticed that whenever a phone number is used, it begins with 555. There is a reason for that.

FWIW, I'm bringing this up with the ICPSR folks. Not the intent. That being said, I was able to create an account with a phone number that starts with area code 000. You could also use a 555 number www.cbc.ca/radio/undert...

Let me check. Registration yes, requirement for US phone number is ... novel.

Reach out if you have any questions! (8/8)

Want to see this all on the same page? aeadataeditor.github.io/aea-de-guida... (7/8)

The use of the AEA Data & Code Repository www.openicpsr.org/openicpsr/aea is strongly encouraged. Other repositories and archives considered to be “trusted” may be acceptable - if you ALREADY have a replication package @ Dataverse/Zenodo/etc. please use that (Github is NOT a “trusted” archive) (6/8)

What do we do? My replicators will review the deposit, review the README, and send you a filled-out checklist, verifying compliance with each item. If you want to get a perfect score (gamification!) you can find a printable checklist here: aeadataeditor.github.io/assets/pdfs/... (5/8)

This means: Should a reader or user of your replication package find errors or omissions at a later stage, you will be asked to remedy the situation in line with our Policy on Revisions of Data and Code Deposits. www.aeaweb.org/journals/dat... (4/8)

However, our compliance check is more limited than the checks conducted for peer-reviewed papers. Your replication package must nevertheless be fully compliant with the AEA Data and Code Availability Policy. www.aeaweb.org/journals/dat... (3/8)

Much of the preparation for papers published in Papers and Proceedings is the same as for the AEA journals, see Step 1 for basic preparation aeadataeditor.github.io/aea-de-guida... & Step 2 if depositing at the AEA Data and Code repository aeadataeditor.github.io/aea-de-guida... (2/8)

🧵For authors preparing the replication packages that accompany their 2026 AEA Papers and Proceedings publication www.aeaweb.org/journals/pandp: Here are some notes on preparing your replication package (1/8)

For those who want physical copies, the Day 1 presentation does not have a PDF version, but you can got to "🍔menu" then "Tools" and use the PDF Export mode. The Day T presentation has a link to a PDF embedded.

Jan 4: Reproducibility on Day T (or how to self-check reproducibility, and other advanced practices): larsvilhuber.github.io/self-checkin...

For those who attended the Jan 3 and 4 sessions at #assa2026 and want a copy of the slides, or those who couldn't make it:

Jan 3: Reproducibility from Day 1 larsvilhuber.github.io/day1-tutorial/

🪅DHS (not that one) Program website active again, and accepting requests for data access dhsprogram.com/Who-we-are/N... (via @ipums.bsky.social )

A data citation covers most of those (name, title, link), does not cover the disclaimer, but honestly, that seems a bit obscure. The piece so often missing is the ack that it is, actually, under CC-BY, and that that license is "sticky". I would be happy for just that.

That's not the kind of precision that the @creativecommons.bsky.social folks say: creativecommons.org/licenses/by/...

That being said, I was (for rhetorical reasons) simplifying somewhat. But I would be happy if folks would actually do that one thing, bc generally, they do none of that....

Luckily, just about any repository out there hosting replication packages (and other data) provide you with a

SIMPLE

way to do that: Copy the citation... (or use your citation manager, e.g. @zotero.org to store the DOI). #datacitation #openscience

I would like to re-emphasize that when data are "publicly available" (as authors frequently mention), the LICENSE matters. Most AEA replication packages are fully or partially under a #CC-BY license. You have ONE (only ONE) obligation, but you MUST fulfill that one obligation: CITE THE DATA!

Of course, my name tag won't say "Data Editor, speak to me". Look for this guy: @larsvil.bsky.social

#sole2025 coming up! I'll be there, hanging around the post-lunch Poster session (P01/2 Metropolitan East) on Friday, if you have questions! (My name tag will give me away). Or buttonhole me at the Cocktail reception on Saturday.

This is an important part of the scientific process!

It is always a pleasure, but also causes some trepidation 😰, when a bunch of motivated junior (and senior!) researchers get together at @i4replication.bsky.social replication games, and I get to observe how others work with the replication packages that we helped prepare! #Montreal

Not at the moment. Sorry.

None of this is a guarantee that we truly learn the identity of a firm. There are many (plausible, legitimate, legal) reasons why the identify of a data source may not be available to even the editors, and yet warrant publication. It's a balance.

And I'm always happy to discuss, by email, or at conferences, what that might look like exactly. bsky.app/profile/aead...

Some discussion of (similar) scenarios in 2024 aeadataeditor.github.io/posts/2024-0... and a bit more tangentially in 2023 aeadataeditor.github.io/posts/2023-1...

Our policy is already too long to cover all possible scenarios, I am told (repeatedly...), but it is very clear "access to the data and code is nonexclusive to the authors" in line 1 ... www.aeaweb.org/journals/dat... Need an exception? See line 3, and a discussion w/ editor + me ensues.