What this site is
Community archivists use this to give individual recordings durable, citable URLs beyond an internal tape-log spreadsheet. Agencies pitch it to historical societies, universities, and community organizations running oral history projects. Developers keep recording dates and duration as clean typed fields rather than log-sheet prose.
How the catalog is organized
Recording year and duration in minutes stay quantitative when documented. Topic, narrator role, and consent-and-access status stay qualitative facets. Compare is optional for topic-comparison research; map is optional for the community or neighborhood context recorded.
Why historical societies and community archives build this
Oral history projects generate hours of testimony that a spreadsheet cannot make discoverable, so per-recording pages with topic and narrator facets let researchers and community members find specific stories directly. Consent and access-restriction facets keep sensitive testimony handled responsibly rather than hidden entirely.
Related surfaces
Pairs with hvce site photographic archive catalog for community-history image crossover and with hvce site heritage walking trail directory for place-based community storytelling. See hvce reason automated discovery for how catalogs surface recordings without manual curation per page.
What ships with every page
Every item profile is crawlable HTML with its own metadata, structured data aligned to the visible record, and a clean text twin for answer engines—so specialized collections stay authoritative for researchers and legible for search and AI systems.
Metrics
| Typical Catalog Size | 600 entities |
|---|---|
| Profile Depth Score | 4 |
| Facet Dimensions | 6 |
Descriptors
| Primary Monetization | sponsorship |
|---|---|
| Discovery Surfaces | seo-aeo |
| Map Suitability | optional |
| Compare Suitability | optional |
| Delivery Mode | ssr |
| Buyer Persona | nonprofit |
| Overlap Cluster | research |
Frequently asked questions
What belongs on each recording profile?
Narrator name or role, topic, recording date and duration, and consent or access-restriction status.
How is narrator consent handled?
Publish only the access level narrators agreed to; restricted recordings stay marked rather than hidden without explanation.
Is a transcript required?
Recommended but not required—publish what your project has completed, and add transcripts incrementally.
Can community members request corrections?
A CTA field can route correction or context requests to your archive’s community liaison process.
Why per-recording pages over a tape log?
Per-recording pages earn independent search visibility and let researchers cite specific testimony precisely.