• Introduction
  • Vision
  • Mission
• Guides & Tutorials
  • 1. Our Indexes
    • 1.1. Wikidata+GeoNames Index (Augmentation)
    • 1.2. WHG Publication Index (Searchable Publication)
    • 1.3. WHG Union Index (Final Integration & Clustering)
  • 2. Workbench
    • 2.1. Individual datasets
    • 2.2. Multiple datasets
    • 2.3. Thematic place collections
      • 2.3.1. Instructional exercise in a class setting, or workshop
      • 2.3.2. Authored publication
  • 3. Publishing Data
    • 3.1. Create and publish a Place Collection
    • 3.2. Create and publish a Dataset Collection
  • 4. Uploading Data
    • 4.1. Choosing an upload data format: LPF or LP-TSV?
    • 4.2. Preparing data for upload
      • 4.2.1. The simple case
      • 4.2.2. The not so simple case: extracting places
      • 4.2.3. Linked Places format (LPF), a GeoJSON extension
  • 5. Reconciliation & Accessioning
    • 5.1. What does closeMatch mean?
  • 6. Reviewing accessioning results
  • 7. Collection Groups
    • 7.1. Create and manage a Collection Group for a class or workshop
• WHG Staff
  • 1. Gazetteer Configurator
    • 1.1. Where to find it
    • 1.2. What you’ll see
    • 1.3. Attribution, licence & rights
    • 1.4. Common tasks
      • 1.4.1. Adding a “core” gazetteer
      • 1.4.2. Hiding a gazetteer from the Regions panel
      • 1.4.3. Disabling Explore mode for a polygon-only gazetteer
    • 1.5. Re-ingestion
      • 1.5.1. Triggering a re-ingest
      • 1.5.2. Status lifecycle
      • 1.5.3. What “completed” actually means
      • 1.5.4. If a re-ingest gets stuck
    • 1.6. Permissions
  • 2. User API Profiles
    • 2.1. Where to find it
    • 2.2. What you’ll see
    • 2.3. Common tasks
      • 2.3.1. Bumping a researcher’s daily quota
      • 2.3.2. Resetting a user’s counter
      • 2.3.3. Investigating heavy usage
    • 2.4. Permissions
  • 3. Site smoke test
    • 3.1. What it checks
    • 3.2. Running it
    • 3.3. Dev shares the production Elasticsearch index
    • 3.4. Interpreting results
  • 4. Atlas v3.5 (forthcoming)
    • 4.1. Sections to be added
      • 4.1.1. Editorial review of submitted gazetteers
      • 4.1.2. Contributor oversight (“My Gazetteers”)
      • 4.1.3. Working / Preview-as-published toggle
      • 4.1.4. Volunteering, API, and Admin Dashboard relocations
      • 4.1.5. Retention sweep monitoring
      • 4.1.6. Gazetteers offcanvas — staff perspective
    • 4.2. Cross-references
• Technical
  • 1. Repositories
  • 2. APIs
    • 2.1. Entity API
      • 2.1.1. Entity Endpoints
      • 2.1.2. Place Identifiers and Source Namespaces
      • 2.1.3. Persistent Identifiers (w3id.org)
      • 2.1.4. Namespace Prefix (prefix.cc)
    • 2.2. Reconciliation Service API
      • 2.2.1. Reconciliation Endpoints
      • 2.2.2. Query Parameters
      • 2.2.3. Source Namespaces
      • 2.2.4. Result Format
      • 2.2.5. Filter Behaviour and Common Pitfalls
      • 2.2.6. Geometry Recovery When the Top Hit Has No Centroid
      • 2.2.7. Data Extension Properties
      • 2.2.8. Using the WHG Reconciliation API in OpenRefine
    • 2.3. Source Terms and Attribution
      • 2.3.1. Where it appears
      • 2.3.2. Shape
      • 2.3.3. Mapping a result to its terms
      • 2.3.4. namespaces_searched
      • 2.3.5. The tri-state flags — null does not mean false
      • 2.3.6. The flags that carry obligations
      • 2.3.7. The WHG overlay
    • 2.4. API Tokens
      • 2.4.1. Using an API Token
      • 2.4.2. Suggest Endpoint Example
      • 2.4.3. Entity API Example
  • 3. Issues
• Development Roadmap
  • v3.3: Collaborative Workbench
    • 1. Map your Data
      • 1.1. What it is
      • 1.2. Why a new tool
      • 1.3. Getting started
      • 1.4. 1 · Import a dataset
      • 1.5. 2 · Confirm column roles
      • 1.6. 3 · Reconcile against WHG
      • 1.7. 4 · Review & confirm matches
      • 1.8. 5 · Map
      • 1.9. 6 · That’s a gazetteer — enrich & export
      • 1.10. 7 · Collaborate & share
      • 1.11. Caveats
    • 2. Collaborative Collections
      • 2.1. What it is
      • 2.2. Starting a new document
      • 2.3. Finding your material — “Edit published…”
      • 2.4. The editor at a glance
      • 2.5. Building a Place Collection
      • 2.6. Building an Itinerary
      • 2.7. Building a Gazetteer Group
      • 2.8. Editing something already published
      • 2.9. Collaborating
      • 2.10. A note on names
      • 2.11. How this relates to the older builders
    • 3. Beta Testing Plan
      • 3.1. How testing is tracked, and how issues get resolved
      • 3.2. Getting access
      • 3.3. Before you start
      • 3.4. Test checklists
  • 1. Atlas: Discovering Linked Places
    • 1.1. The problem Atlas solves
    • 1.2. What Atlas does
    • 1.3. How Atlas decides two records are the same place
    • 1.4. You are in control: the grouping dial
    • 1.5. It all happens in your browser
    • 1.6. Confirmed links and your corrections
    • 1.7. Why not just fix the groups once and for all?
    • 1.8. What’s coming
  • 2. v3.5: Toponym Phonetics
    • 2.1. Overview
      • 2.1.1. Goals
      • 2.1.2. Why Not Elasticsearch’s Built-in Phonetic Analysis?
      • 2.1.3. Limitations
      • 2.1.4. Architecture Summary
      • 2.1.5. Data Sources
    • 2.2. Elastic Management Guide
      • 2.2.1. Table of Contents
      • 2.2.2. Architecture Overview
      • 2.2.3. Installation
      • 2.2.4. Configuration
      • 2.2.5. Storage Architecture
      • 2.2.6. Production Instance (VM)
      • 2.2.7. Staging Instance (Slurm)
      • 2.2.8. Authority Data Ingestion
      • 2.2.9. Index Management
      • 2.2.10. Snapshot Management
      • 2.2.11. Production Deployment
      • 2.2.12. Health Monitoring
      • 2.2.13. Troubleshooting
      • 2.2.14. Quick Reference
    • 2.3. Infrastructure Summary
      • 2.3.1. Overview
      • 2.3.2. Architecture
      • 2.3.3. Authority Data Sources
      • 2.3.4. WHG-Contributed Datasets
      • 2.3.5. Phonetic Search
      • 2.3.6. Index Schemas
      • 2.3.7. Deployment Strategy
      • 2.3.8. Storage Requirements
      • 2.3.9. Snapshot Strategy
      • 2.3.10. Resource Summary
      • 2.3.11. Operational Commands
      • 2.3.12. Directory Structure
      • 2.3.13. References
    • 2.4. Components
      • 2.4.1. Infrastructure
      • 2.4.2. Elasticsearch Indices
      • 2.4.3. Processing Components
    • 2.5. Data Flow
      • 2.5.1. Authority File Ingestion
      • 2.5.2. WHG-Contributed Dataset Ingestion
      • 2.5.3. Embedding Generation
      • 2.5.4. Incremental Updates
    • 2.6. Elasticsearch Index Design
      • 2.6.1. Index Schemas
      • 2.6.2. Ingest Pipelines
      • 2.6.3. HNSW Configuration
      • 2.6.4. Analysers
    • 2.7. Training the Phonetic Similarity Model
      • 2.7.1. 1. Architecture Overview
      • 2.7.2. 2. Key Features
      • 2.7.3. 3. Installation
      • 2.7.4. 4. The Training Pipeline
      • 2.7.5. 5. Python Inference API
      • 2.7.6. 6. Configuration
    • 2.8. Query Pipeline
      • 2.8.1. Search Strategy
      • 2.8.2. Elasticsearch Query Structure
      • 2.8.3. Spatial Containment Filtering
      • 2.8.4. Error Handling
      • 2.8.5. Performance Optimisation
    • 2.9. Advantages of This Architecture
      • 2.9.1. Two-Instance Isolation
      • 2.9.2. Unified Infrastructure
      • 2.9.3. Scalable Storage Tiers
      • 2.9.4. Zero-Downtime Deployments
      • 2.9.5. Flexible Embedding Generation
      • 2.9.6. Toponym Deduplication
      • 2.9.7. Efficient Phonetic Search
      • 2.9.8. Graceful Degradation
      • 2.9.9. Unified Search Across Sources
      • 2.9.10. Maintainability
      • 2.9.11. Research Reproducibility
    • 2.10. Monitoring & Observability
      • 2.10.1. Key Metrics
      • 2.10.2. Health Check Endpoints
      • 2.10.3. Log Locations
      • 2.10.4. Dashboards
      • 2.10.5. Alerting
      • 2.10.6. Runbook: Common Issues
    • 2.11. Future Extensions
      • 2.11.1. Short-Term Enhancements
      • 2.11.2. Medium-Term Development
      • 2.11.3. Long-Term Vision
    • 2.12. Deployment Plan
      • 2.12.1. Phase 1: Infrastructure Setup
      • 2.12.2. Phase 2: Core Index Population
      • 2.12.3. Phase 3: Model Training
      • 2.12.4. Phase 4: Embedding Generation
      • 2.12.5. Phase 5: Query Integration
      • 2.12.6. Phase 6: Production Rollout
      • 2.12.7. Ongoing Operations
    • 2.13. Risk Assessment
      • 2.13.1. Technical Risks
      • 2.13.2. Operational Risks
      • 2.13.3. Data Quality Risks
      • 2.13.4. Mitigation Strategies
    • 2.14. Success Criteria
      • 2.14.1. Technical Metrics
      • 2.14.2. User Experience Metrics
      • 2.14.3. Research Impact
      • 2.14.4. Acceptance Criteria by Phase
    • 2.15. Summary & References
      • 2.15.1. Key Design Decisions
      • 2.15.2. Technology Stack
      • 2.15.3. Storage Requirements
      • 2.15.4. Timeline
      • 2.15.5. References
  • 3. V4: Graph Datamodel
    • 3.1. User Guide
      • 3.1.1. Note to Documentation Team
      • 3.1.2. Getting Help
    • 3.2. Open Educational Resources (OER)
      • 3.2.1. Vision
      • 3.2.2. Strategic Goals
      • 3.2.3. Technical Requirements
    • 3.3. Data Model
      • 3.3.1. Introduction
      • 3.3.2. Overview
      • 3.3.3. Attestations & Relations
      • 3.3.4. Vocabularies
      • 3.3.5. Special Thing Patterns
      • 3.3.6. Contribution Types & Data Formats
      • 3.3.7. RDF Representation
      • 3.3.8. Platform Use Cases
      • 3.3.9. Implementation in ArangoDB
      • 3.3.10. Summary & Future Directions
    • 3.4. System Architecture
      • 3.4.1. Database Technology Assessment
      • 3.4.2. Kubernetes Configuration
      • 3.4.3. SSH Key Setup
      • 3.4.4. Deploying the Management Pod
      • 3.4.5. Deploying Services
      • 3.4.6. Service Configuration
• License
  • Creative Commons Attribution-NonCommercial 4.0 International Public License
    • Section 1 – Definitions.
    • Section 2 – Scope.
    • Section 3 – License Conditions.
    • Section 4 – Sui Generis Database Rights.
    • Section 5 – Disclaimer of Warranties and Limitation of Liability.
    • Section 6 – Term and Termination.
    • Section 7 – Other Terms and Conditions.
    • Section 8 – Interpretation.