Data Pipeline
Two source streams, one inspectable chain—and several places where a geographic frame enters.
A scanned map and a source page do not become map objects in the same way. They travel through parallel processes, meet in shared reference systems, and remain distinguishable after they reach the interface.
- 01Scan and provenance
- 02Control points and georeferencing
- 03Boundary tracing and dating
- 04Validated geometry
These make comparison possible but never become the source’s own assertion.
- 01Scan and transcription
- 02Verbatim capture
- 03Entities, places, and relations
- 04Interpretation, last
- Source vocabularyWhat spatial language does the document use?
Names, administrative terms, and scales are preserved before matching.
- Archival arrangementWhy did this record survive and how was it classified?
Collection and source type shape what can be extracted and what remains absent.
- Spatial anchoringHow was a name connected to a place or geometry?
Exact, regional, route-level, uncertain, and unresolved matches remain distinct.
- Interpretive frameWhich polity system or present reference is being applied?
These readings are late, named, and reversible.
- Interface frameHow are records grouped, filtered, labeled, and compared?
The display is part of the argument and is therefore documented as a mediation.
The source assertion survives every later reading
When a source names Filasṭīn, the platform records that usage as written. A present-day polity match or administrative comparison may be added later, but it cannot replace the source term. The same separation governs coordinates, dates, affiliations, journeys, and boundaries.
Recognition → anchors → schemas → assemblages → interfaces
The pipeline does not remove mediation. It records where mediation occurs and keeps the result open to revision.
Read the governing method →