Data
The YAML files behind the EDS Research Index: the source catalog, research records, subtype registry, searches for new evidence, open questions, and the log of every change. Each file is checked against the published schema when the site builds, and every record, source, and date on the site comes from these files.
Corpus
The research records (findings, practices, events, patient-reported patterns, and programs) and the subtype registry.
/eds-corpus/subtypes.yml/eds-corpus/historiography.yml/eds-corpus/diagnosis-and-classification.yml/eds-corpus/genetics.yml/eds-corpus/comorbidities.yml/eds-corpus/management.yml/eds-corpus/community-knowledge.yml/eds-corpus/folk-and-early-management.yml/eds-corpus/patient-experience.yml/eds-corpus/research-programs.yml
Sources, searches, and the change log
The source catalog, venues, searches for new evidence, change log, open questions, collections, and publication policy.
/research/sources.yml/research/venues.yml/research/monitors.yml/research/runs.yml/research/questions.yml/research/collections.yml/research/publication-policy.yml
License
These files are licensed under CC BY 4.0. Credit them as “EDS Research Index (hraness.com/eds), CC BY 4.0” and say whether you changed them. The papers and reports they cite keep their own terms.
How the files stay consistent
Each source's ID is built from its URL and publication date, so the same source always gets the same ID and duplicates are caught. The build also checks that every record, venue, collection, and log entry points to something that exists, and that each record gives a source the same evidence level as the source catalog. A broken reference stops the build rather than breaking a page.