TRSP Desirable Characteristics

Deposition of data: are there any restrictions (e.g. by location, country, organisation, etc.) or can anyone from anywhere deposit data?

TRSP Desirable Characteristics

Policies that explain what datasets the repository will accept for deposit, from whom, and under what conditions, including costs.

TRSP Desirable Characteristics

The repository must obtain all necessary rights from the depositor, and demonstrate that there are sufficient controls in place to ensure they are applied and monitored.

TRSP Desirable Characteristics

The repository accepts data and metadata based on defined criteria to ensure relevance and understandability for users.

Correa, R., Du, W., & Liao, G. Y. (2020). U.S. Banks and Global Liquidity (Working Paper No. 27491; Working Paper Series). National Bureau of Economic Research. https://doi.org/10.3386/w27491

A few paragraphs later this appears: "She set her phone alarm for midnight so that as Thursday turned to Friday, she could check whether Dave’s first paycheck had hit their account. She could hear the clatter of raccoons foraging in a nearby dumpster and the hum of cars rolling through the drive-through. At 12:01 a.m. she looked to see whether Dave’s paycheck had shown up in his account." First they don't have an account for the stimulus money to go to, then they're getting up at midnight to see if the paycheck had hit their account. In addition, it takes about a week to set up direct deposit with most companies.

In 2018 the law 1915/2018 modifies this law. Adding a chanche to Legal Deposit law. The chances are now underway.

Example of author sharing all code via jupyter notebooks in a github repo. They have archived to Zenodo and include both URLs in the text. Their analysis relies on an existing toolkit - it is not obvious from the manuscript whether this toolkit has been deposited anywhere.

Journal: PLOS ONE Subject area: plant biology, ecology (check?)

Example of authors archiving their own code. The eLife process is to fork the author's repo to the eLife github repo to save a snapshot of the repo at the time of acceptance. The authors here have also chosen to archive to Zenodo (via the Github release --> Zenodo mechanism?). Both the Zenodo DOI and the eLife fork are included in the text as archive/snapshot copies of the original (also cited).

Note the author's original repo is included in the references.

Journal: eLife Subject area: ecology, evolutionary biology

In this example, the archived code repository has been listed in the eLife Key Resources Table