Entity and relationship model
Archives and evidence
Research Database Development
A research database should preserve the path from public interpretation back to the source, while making inconsistent names, dates, places, and formats usable as one corpus.
Scope
Designed for institutions and difficult source material
Research databases, source-aware digital archives, provenance systems, place authorities, and public discovery interfaces for complex collections.
The engagement is structured around the actual research object and the public responsibility of the finished work. Existing data is evaluated before new collection begins, and visual design follows the evidence model rather than replacing it.
- Archives and libraries
- Research centers
- Museums
- Editorial teams
- Universities
- Long-term documentation projects
Deliverables
A complete working result
Source, citation, and provenance registry
Place, person, organization, and period authorities
Import and normalization workflow
Search, facets, records, and public discovery pages
Review status, confidence, and correction process
Method
Research discipline before interface spectacle
Model the research object
The database begins with what a record means in the discipline, not with the columns available in the first spreadsheet.
Separate claim from source
A public summary, source transcription, analytical classification, and geographic interpretation remain connected but distinct.
Resolve identities
Aliases, transliterations, duplicate records, institutional IDs, and geographic authorities are reconciled transparently.
Design for discovery
Stable URLs, search facets, related records, citations, exports, and structured metadata turn the corpus into a usable publication.
Applications
Where this practice operates
Historical archives
People, places, events, documents, photographs, collections, citations, and relationships.
Geographic catalogs
Coordinates, geometry confidence, historical names, administrative context, and map-ready summaries.
Evidence registers
Claims, sources, review states, uncertainty, corrections, and public record history.
Evidence of practice
Related public systems
Questions
Technical and methodological answers
Can several incompatible archives be combined?+
Yes, through a normalized integration layer that preserves source-specific fields, identifiers, licenses, and uncertainty.
Can private review data remain separate from public records?+
Yes. Acquisition, staging, review, and public release can be isolated so unfinished records are not accidentally presented as verified output.
Will individual records be indexable?+
Where appropriate, stable server-rendered record pages can expose titles, summaries, citations, structured data, and canonical URLs to search engines.
Commission
Build the system the subject requires
Begin with the research question, available evidence, geographic scope, intended audience, and required public result.
Start a project inquiry