• Introduction
  • Vision
  • Mission
• Guides & Tutorials
  • 1. Our Indexes
    • 1.1. Wikidata+GeoNames
    • 1.2. WHG Union Index
    • 1.3. WHG “Pub” index
  • 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
  • 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
• Technical
  • 1. Repositories
  • 2. APIs
    • 2.1. Entity API
    • 2.2. Reconciliation Service API
    • 2.3. Documentation
    • 2.4. API Tokens
      • 2.4.1. Using an API Token
  • 3. Issues
• V4 Preview
  • 1. User Guide
    • 1.1. Note to Documentation Team
      • 1.1.1. Quick Start Guide
      • 1.1.2. Understanding WHG Concepts
      • 1.1.3. Place Record Anatomy
      • 1.1.4. Contributing Data Overview
      • 1.1.5. Reconciliation Overview
      • 1.1.6. Tutorial: Creating a Historical Route
      • 1.1.7. Frequently Asked Questions
      • 1.1.8. Glossary
    • 1.2. Getting Help
  • 2. Open Educational Resources (OER)
    • 2.1. Vision
    • 2.2. Strategic Goals
    • 2.3. Technical Requirements
      • 2.3.1. OER Metadata Schema
      • 2.3.2. Data Model Extensions
      • 2.3.3. API Endpoints
      • 2.3.4. Frontend Components
      • 2.3.5. Integration Points
      • 2.3.6. Workflow for Creating OERs
      • 2.3.7. Technical Implementation Checklist
      • 2.3.8. Success Metrics
      • 2.3.9. Sustainability Considerations
      • 2.3.10. Documentation Needs
  • 3. Data Model
    • 3.1. Introduction
      • 3.1.1. The Multi-Temporal Data Challenge
      • 3.1.2. The Solution: Attestations as Bundle Nodes
      • 3.1.3. Complete Example: Constantinople Through Time
      • 3.1.4. Why This Works
      • 3.1.5. Key Insight
      • 3.1.6. The Role of AUTHORITY and RELATION_TYPE
      • 3.1.7. Meta-Attestations: Attesting About Attestations
    • 3.2. Overview
      • 3.2.1. Core Entities
      • 3.2.2. Core Design Philosophy
      • 3.2.3. The Thing Entity
      • 3.2.4. Name Entity
      • 3.2.5. Geometry Entity
      • 3.2.6. Timespan Entity
      • 3.2.7. Attestation Entity
      • 3.2.8. Entity Relationships
      • 3.2.9. Entity Lifecycle
      • 3.2.10. Design Rationale
      • 3.2.11. Next Steps
    • 3.3. Attestations & Relations
      • 3.3.1. The Attestation as Graph Node
      • 3.3.2. Relationships Through Edges
      • 3.3.3. Relation Types via AUTHORITY Collection
      • 3.3.4. Complete Examples
      • 3.3.5. Multiple Attestations for Same Thing
      • 3.3.6. Querying Patterns
      • 3.3.7. Design Benefits
      • 3.3.8. Migration from v3
    • 3.4. Vocabularies
      • 3.4.1. Architecture Note
      • 3.4.2. Thing Classification Vocabulary
      • 3.4.3. Name Type Vocabulary
      • 3.4.4. Source Type Vocabulary
      • 3.4.5. Temporal Precision Vocabulary
      • 3.4.6. Spatial Precision Vocabulary
      • 3.4.7. Connection Type Vocabulary (for Networks)
      • 3.4.8. Directionality Vocabulary (for Networks)
      • 3.4.9. Certainty Assessment
      • 3.4.10. Meta-Attestation Types
    • 3.5. Special Thing Patterns
      • 3.5.1. Period Things
      • 3.5.2. Route Things
      • 3.5.3. Itinerary Things
      • 3.5.4. Network Things
      • 3.5.5. Gazetteer Group Things
      • 3.5.6. Timespan Inheritance and Computation
      • 3.5.7. Geometry Inheritance
    • 3.6. Contribution Types & Data Formats
      • 3.6.1. Overview
      • 3.6.2. Contribution Types
      • 3.6.3. Accepted Formats for All Types
      • 3.6.4. Relationship to Linked Places Format (LPF)
      • 3.6.5. Editing Contributions
    • 3.7. RDF Representation
      • 3.7.1. Overview
      • 3.7.2. Core Ontology Classes
      • 3.7.3. The Attestation Pattern in RDF
      • 3.7.4. Relation Type Vocabulary
      • 3.7.5. Complete Example
      • 3.7.6. Temporal Scoping
      • 3.7.7. Certainty and Provenance
      • 3.7.8. Meta-Attestations
      • 3.7.9. Integration with Existing Ontologies
      • 3.7.10. Geometry Representation
      • 3.7.11. Comparison with Other Models
      • 3.7.12. Querying with SPARQL
      • 3.7.13. Implementation Notes
      • 3.7.14. See Also
      • 3.7.15. External Resources
    • 3.8. Platform Use Cases
      • 3.8.1. Overview
      • 3.8.2. Core Platform Capabilities
      • 3.8.3. Researcher Workflow Examples
      • 3.8.4. What Sets WHG Apart
      • 3.8.5. Platform Value Proposition
      • 3.8.6. Technical Advantages of Graph Model
    • 3.9. Implementation in ArangoDB
      • 3.9.1. Overview
      • 3.9.2. Document Collections
      • 3.9.3. Indexing Strategy
      • 3.9.4. Query Patterns in AQL
      • 3.9.5. Handling Temporal Nulls and Geological Time
      • 3.9.6. ArangoDB Capabilities Assessment
      • 3.9.7. Summary
    • 3.10. Summary & Future Directions
      • 3.10.1. Core Architecture
      • 3.10.2. Key Design Principles
      • 3.10.3. What This Enables
      • 3.10.4. Implementation Choice: ArangoDB
      • 3.10.5. Future Extensions
      • 3.10.6. Research Challenges
      • 3.10.7. Sustainability Model
      • 3.10.8. Architectural Clarity
      • 3.10.9. Conclusion
  • 4. System Architecture
    • 4.1. Database Technology Assessment
      • 4.1.1. TL;DR
      • 4.1.2. Executive Summary
      • 4.1.3. Data Volume Projection
      • 4.1.4. Option 1: ArangoDB
      • 4.1.5. Option 2: PostgreSQL + Extensions
      • 4.1.6. Option 3: Neo4j
      • 4.1.7. Option 4: Vespa
      • 4.1.8. Detailed Comparison Matrix
      • 4.1.9. Recommendation
      • 4.1.10. Next Steps
      • 4.1.11. Conclusion
    • 4.2. Kubernetes Configuration
      • 4.2.1. Overview
      • 4.2.2. Setup
    • 4.3. SSH Key Setup
      • 4.3.1. 1. Generate an SSH Key
      • 4.3.2. 2. Copy the Public Key to the Remote Server
      • 4.3.3. 3. Log in to the Remote Server
      • 4.3.4. 4. Automatically Switch to the gazetteer Account
      • 4.3.5. 5. Check Kubernetes Nodes
      • 4.3.6. Secrets Management
    • 4.4. Deploying the Management Pod
      • 4.4.1. Accessing Kubernetes Dashboard and Services Locally
    • 4.5. Deploying Services
    • 4.6. Service Configuration
      • 4.6.1. Proposed Subdomain Mapping
• 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.