Replication & Data Policy (jbf-replication-and-data-policy)
When to trigger
- The paper uses CRSP, Compustat, BankFocus, Dealscan, TRACE, Call Reports, hand-collected data, or simulations
- You need a data availability statement for Elsevier/JBF submission
- You want a legal and useful replication package despite proprietary data
Policy stance
JBF follows Elsevier Option C research-data instructions. At submission, authors
must state data availability. For shareable data, deposit the research data in a
relevant repository and cite/link it in the article. If data cannot be shared,
state why (for example, proprietary, sensitive, confidential, or licensing limits).
JBF does not operate a dedicated journal-run replication archive, so the practical
package should combine a repository deposit where rights allow, code, metadata,
and a precise access route for restricted inputs.
Package structure
README.md
data_access/ # licensed-data instructions, not raw proprietary files
code/
00_setup.*
01_build_sample.*
02_main_tables.*
03_figures.*
04_robustness.*
output/
tables/
figures/
requirements.* # renv.lock / requirements.txt / Stata package list
Data availability statements
- Public data: name source, URL, access date, and archive copy if permitted.
- Proprietary data: identify vendor, product, access terms, and exact query or
extraction instructions; do not redistribute restricted files.
- Hand-collected data: share the dataset if rights allow, with coding rules.
- No external data / simulation: state that no external data were used and
provide simulation code and seeds.
Code expectations
- One master script regenerates all tables and figures.
- Random seeds and software versions are recorded.
- Output files match manuscript numbering.
- Confidential paths and author identity are removed before double-anonymized submission.
Proprietary-data audit
For licensed banking/finance sources, add a data_access/README.md that records:
- vendor/product, query filters, identifiers, and date accessed;
- variables needed to recreate the analysis;
- any hand-cleaning or link-table rules;
- whether a pseudo dataset can exercise the full code path;
- who can legally access the raw data and under what license.
Source-by-source sharing matrix
| Typical JBF source |
Redistribution |
What the package carries instead |
| US Call Reports / FDIC SDI |
public — share extracts |
pull scripts with vintage, date, and series mnemonics |
| Orbis Bank Focus / BankScope legacy |
licensed — do not share |
query filters, consolidation codes, variable list, access date |
| DealScan |
licensed — do not share |
extraction steps, facility/package level, link-table code |
| CRSP / Compustat (when used) |
licensed — do not share |
WRDS query description and merge keys |
| Hand-collected regulatory events |
usually shareable |
coding manual, per-event sources, inter-coder checks |
| Confidential supervisory data |
cannot leave the authority |
aggregate descriptives plus the access route for replicators |
Worked statement draft (illustrative)
Data availability. Bank balance-sheet data come from US Call Reports (FFIEC,
public; pull scripts and vintages in /code/01). Loan-facility data are from
DealScan under license; we provide extraction filters and borrower link-table
code but not raw files. Hand-collected deregulation dates and coding rules are
deposited with the package. All tables and figures regenerate from run_all
with the licensed inputs in place; a synthetic sample exercises the full
pipeline without them.
Pre-submission package audit
A package failing two or more boxes usually signals deeper pipeline debt; route back to jbf-data-analysis before drafting the statement.
Editor pushbacks on data
- "The package cannot run without DealScan." → ship a synthetic or masked sample that exercises every script end to end.
- "Which Bank Focus vintage?" → record vendor vintage and download date; bank coverage shifts across vintages.
- "Confidential supervisory data make this unreviewable." → document the authority's access procedure and provide all code plus aggregate moments; the data statement must explain the access limits.
Output format
[Data status] public / proprietary / confidential / simulated / mixed
[Statement draft] ...
[Shareable files] ...
[Restricted files] ...
[Reproducibility gaps] ...
[Next step] jbf-submission
1---2name: jbf-replication-and-data-policy3description: Use when preparing the required data statement, code archive, repository deposit/link, and proprietary-data documentation for a Journal of Banking & Finance manuscript under Elsevier Option C research-data expectations.4metadata:5 source: https://skillmd.com/skills/brycewang-stanford/jbf-replication-and-data-policy6---78# Replication & Data Policy (jbf-replication-and-data-policy)910## When to trigger1112- The paper uses CRSP, Compustat, BankFocus, Dealscan, TRACE, Call Reports, hand-collected data, or simulations13- You need a data availability statement for Elsevier/JBF submission14- You want a legal and useful replication package despite proprietary data1516## Policy stance1718JBF follows Elsevier **Option C** research-data instructions. At submission, authors19must state data availability. For shareable data, deposit the research data in a20relevant repository and cite/link it in the article. If data cannot be shared,21state why (for example, proprietary, sensitive, confidential, or licensing limits).22JBF does not operate a dedicated journal-run replication archive, so the practical23package should combine a repository deposit where rights allow, code, metadata,24and a precise access route for restricted inputs.2526## Package structure2728```text29README.md30data_access/ # licensed-data instructions, not raw proprietary files31code/32 00_setup.*33 01_build_sample.*34 02_main_tables.*35 03_figures.*36 04_robustness.*37output/38 tables/39 figures/40requirements.* # renv.lock / requirements.txt / Stata package list41```4243## Data availability statements4445- **Public data**: name source, URL, access date, and archive copy if permitted.46- **Proprietary data**: identify vendor, product, access terms, and exact query or47 extraction instructions; do not redistribute restricted files.48- **Hand-collected data**: share the dataset if rights allow, with coding rules.49- **No external data / simulation**: state that no external data were used and50 provide simulation code and seeds.5152## Code expectations5354- One master script regenerates all tables and figures.55- Random seeds and software versions are recorded.56- Output files match manuscript numbering.57- Confidential paths and author identity are removed before double-anonymized submission.5859## Proprietary-data audit6061For licensed banking/finance sources, add a `data_access/README.md` that records:6263- vendor/product, query filters, identifiers, and date accessed;64- variables needed to recreate the analysis;65- any hand-cleaning or link-table rules;66- whether a pseudo dataset can exercise the full code path;67- who can legally access the raw data and under what license.6869## Source-by-source sharing matrix7071| Typical JBF source | Redistribution | What the package carries instead |72| --- | --- | --- |73| US Call Reports / FDIC SDI | public — share extracts | pull scripts with vintage, date, and series mnemonics |74| Orbis Bank Focus / BankScope legacy | licensed — do not share | query filters, consolidation codes, variable list, access date |75| DealScan | licensed — do not share | extraction steps, facility/package level, link-table code |76| CRSP / Compustat (when used) | licensed — do not share | WRDS query description and merge keys |77| Hand-collected regulatory events | usually shareable | coding manual, per-event sources, inter-coder checks |78| Confidential supervisory data | cannot leave the authority | aggregate descriptives plus the access route for replicators |7980## Worked statement draft (illustrative)8182```text83Data availability. Bank balance-sheet data come from US Call Reports (FFIEC,84public; pull scripts and vintages in /code/01). Loan-facility data are from85DealScan under license; we provide extraction filters and borrower link-table86code but not raw files. Hand-collected deregulation dates and coding rules are87deposited with the package. All tables and figures regenerate from run_all88with the licensed inputs in place; a synthetic sample exercises the full89pipeline without them.90```9192## Pre-submission package audit9394- [ ] `run_all` executes on a clean machine with only the licensed inputs mounted95- [ ] every manuscript exhibit maps to exactly one output file, with matching numbering96- [ ] the synthetic or masked sample passes every script end to end97- [ ] vendor vintages and download dates recorded for Bank Focus, DealScan, and any WRDS pulls98- [ ] no author-identifying paths or initials in code comments (double-anonymized review)99- [ ] repository deposit linked and cited where rights allow, or non-sharing reason stated clearly100101A package failing two or more boxes usually signals deeper pipeline debt; route back to `jbf-data-analysis` before drafting the statement.102103## Editor pushbacks on data104105- "The package cannot run without DealScan." → ship a synthetic or masked sample that exercises every script end to end.106- "Which Bank Focus vintage?" → record vendor vintage and download date; bank coverage shifts across vintages.107- "Confidential supervisory data make this unreviewable." → document the authority's access procedure and provide all code plus aggregate moments; the data statement must explain the access limits.108109## Output format110111```text112[Data status] public / proprietary / confidential / simulated / mixed113[Statement draft] ...114[Shareable files] ...115[Restricted files] ...116[Reproducibility gaps] ...117[Next step] jbf-submission118```