This site does not provide legal guidance. The information below is provided for discussion and as a suggestion only. Authors should consult with a qualified party, such as a university counsel or a lawyer, as appropriate.
When depositing in a Code and Data Repository, a license needs to be chosen. If not chosen through the menu, a license file (typically named
LICENSE.md) needs to be provided.
Some guidance on licensing of databases and software:
See the Social Science Data Editors’ Licensing Guidance and resources linked therein for more extensive guidance.
For the purpose of replicability, the AEA will insist on an open license that allows for replication by researchers unconnected to the original parties, to the extent allowed by other agreements and the law.
We suggest the Creative Commons Attribution 4.0 International Public License or the more liberal [CC0 1.0 Universal (CC0 1.0) Public Domain Dedication].
At the AEA Data and Code Repository, Creative Commons Attribution 4.0 International Public License is the default license.
“Code” or “Software” is any statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result, and may include interpretive, object or source code. The CC-BY license is not recommended for software.
Repositories with both Code and Data
Many repositories contain both code and databases. In that case, the repository might contain files under different licenses. For instance, some components may come with more restrictive licenses (MIT License for software from third parties) or more lenient licenses (CC0 license for own code), with a third license for databases.
We provide an example of a dual-license setup, suitable for use by depositors to the AEA’s Data and Code Repository (see LICENSE-template). It combines
- Modified BSD License, applies to all code, scripts, programs, and SOFTWARE
- Creative Commons Attribution 4.0 International Public License, applies to databases, images, tables, text, and any other objects
NOTE: Authors must explicitly upload this license to their deposit, as
LICENSE.txt, and choose the
Other licenseoption when publishing their repository.
A different example
A more complex implementation of the multi-license setup can be found on the Social Science Data Editors website.