Public voice (campus guide)
Use this wording on public pages: Home, Search, Map, Report, About, Submit, and indexes. Keep specialist terms in code, APIs, internal reports, and staff tools.
Prefer these words
| Avoid (public) | Prefer |
|---|---|
| edge / node | connection / place, person, or item |
| ownership unit / prefix | college or school / department |
| provenance | where this came from / sources |
| evidenced / evidence objects | supported by sources / listed items |
| harvested / layer / practice gaps | omit on public pages |
| packet | submitted material / your submission |
| map objects | listings / places and programs |
Entity IDs (PUB-306, CDM-001) |
show the title; ID only under “For editors” or in the URL |
Citations
Normal linked footnotes next to the claim they support are welcome. Put the full source line in a short Sources list under that panel—not repeated mid-sentence. Prefer a readable title and link; hide file paths and internal submission folder names.
When one claim has several sources, group the markers with commas: 1,4,63 (not three separate superscripts). Facility and publication pages are generated by scripts/apply_citations.py — see citation notes.
Default UI
The standard view (plain-language guide) is the public default at the site root (/) and on catalog resource pages. It has no top menu or header search — only the page content, with a small Developer view control. Developer view restores the full navigation bar and search; every developer page includes a Standard view button to return.