Data
Everything the viewers use is published here. If you want to check a number, reproduce a chart, or build something else on top of this, start with these files.
What is published#
Derived facts only. Each record says which work, which passage, which journal, which year, and which article DOI. There is no article text of any kind. The verbatim citation context extracted during processing is confidential under the JSTOR Text Analysis Support terms and is dropped before any shareable file is written.
| File | Contents |
|---|---|
meta.json | Journals, year range and histogram, corpus totals, thresholds used. |
view_a.json | Per work: placed count (the floor), uncertainty band, unplaceable mass, distinct articles, collision partners. Also carries an internal resolution_rate / tier, retained for provenance but no longer used by the site (see methods). |
view_a_filter.json | Per work: sparse journal × year matrix of placed citations. The time chart's source. |
works_index.json | Work list with placed-citation totals (plus an unused internal tier field). |
view_b/<work>.json | Per work: section-level cells and per-citation records with DOI links. |
Licence#
The derived data is CC BY 4.0 — use it for anything, including commercially, provided you attribute the source. The pipeline and site code are MIT; the site prose is CC BY 4.0 on the same terms as the data.
The underlying JSTOR full text is not redistributable and is not available here. It never leaves the machine that processes it: the verbatim context of each citation is dropped before anything is written to a shareable file, and what is published is derived facts only — work, passage, journal, year, DOI.
Reproducing the build#
The aggregator that produces these files runs locally against the JSTOR delivery. Given the delivery, build_viewer_data.py regenerates every file above, and prints invariant self-checks so a bad run announces itself.
Without the delivery you cannot regenerate the data from scratch — but you can verify every published number against these files, and the methods page documents each transformation between the two.