Raleighpedia:Hierarchy of sources: Difference between revisions
FrankMuraca (talk | contribs) Created page with "= Raleighpedia: Hierarchy of Sources = == Purpose == Raleighpedia documents Raleigh’s civic, historical, and community record. To do this consistently and transparently, the project uses a hierarchy of sources that reflects how decisions are actually made, recorded, and experienced. This hierarchy guides: * How claims are supported * How conflicting sources are resolved * How readers should interpret evidence * How Raleighpedia distinguishes fact from context and int..." |
FrankMuraca (talk | contribs) No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Purpose == | == Purpose == | ||
Raleighpedia documents Raleigh’s civic, historical, and community record. To do this consistently and transparently, the project uses a hierarchy of sources that reflects how decisions are actually made, recorded, and experienced. | Raleighpedia documents Raleigh’s civic, historical, and community record. To do this consistently and transparently, the project uses a hierarchy of sources that reflects how decisions are actually made, recorded, and experienced. | ||
| Line 18: | Line 16: | ||
Lower tiers add context, interpretation, or experience. | Lower tiers add context, interpretation, or experience. | ||
== Tier 1: Official civic record == | === Tier 1: Official civic record === | ||
These sources document formal government action. | These sources document formal government action. | ||
| Line 32: | Line 30: | ||
* Confirming what was approved, rejected, or deferred | * Confirming what was approved, rejected, or deferred | ||
When available, Tier 1 sources should | When available, Tier 1 sources should be used to back up factual claims. | ||
== Tier 2: Administrative and technical documents == | === Tier 2: Administrative and technical documents === | ||
These sources explain how decisions were evaluated and implemented within government. | These sources explain how decisions were evaluated and implemented within government. | ||
| Line 51: | Line 49: | ||
These sources provide context but do not supersede formal actions. | These sources provide context but do not supersede formal actions. | ||
== Tier 3: Quasi official and institutional sources == | === Tier 3: Quasi official and institutional sources === | ||
These sources are adjacent to city government but are not direct decision making bodies. | These sources are adjacent to city government but are not direct decision making bodies. | ||
| Line 64: | Line 62: | ||
* Technical framing relied upon by staff or council | * Technical framing relied upon by staff or council | ||
== Tier 4: Journalism and contemporary reporting == | === Tier 4: Journalism and contemporary reporting === | ||
These sources document how civic actions were communicated and perceived publicly. | These sources document how civic actions were communicated and perceived publicly. | ||
| Line 79: | Line 77: | ||
Reporting should not override official records when establishing facts. | Reporting should not override official records when establishing facts. | ||
== Tier 5: Community documentation and oral history == | === Tier 5: Community documentation and oral history === | ||
These sources capture lived experience and informal knowledge. | These sources capture lived experience and informal knowledge. | ||
| Line 94: | Line 92: | ||
These sources should always be clearly labeled as community based. | These sources should always be clearly labeled as community based. | ||
== Tier 6: Raleighpedia synthesis and interpretation == | === Tier 6: Raleighpedia synthesis and interpretation === | ||
Raleighpedia allows original synthesis when it is transparent and well documented. | Raleighpedia allows original synthesis when it is transparent and well documented. | ||
| Line 126: | Line 124: | ||
Making this structure explicit improves clarity for readers and reduces misinterpretation when Raleighpedia content is reused in research, reporting, or AI generated summaries. | Making this structure explicit improves clarity for readers and reduces misinterpretation when Raleighpedia content is reused in research, reporting, or AI generated summaries. | ||
This hierarchy may evolve as Raleighpedia grows. Any changes should be documented and discussed openly. | This hierarchy may evolve as Raleighpedia grows. Any changes should be documented and discussed openly. | ||