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.5. Re-ingestion
  • 1.6. Permissions
• 2. User API Profiles
  • 2.1. Where to find it
  • 2.2. What you’ll see
  • 2.3. Common tasks
  • 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 (staff notes)
  • 4.1. What the Atlas is and who can see what
  • 4.2. How it fits together (Staff)
  • 4.3. Licensing behaviour
  • 4.4. Failure modes and what users see
  • 4.5. Testing (Staff)
  • 4.6. Beta testing process
  • 4.7. Known limitations
  • 4.8. Not yet documented
• 5. Restarting the gateway
  • 5.1. What a restart does
  • 5.2. Check what is actually running
  • 5.3. If the pull fails
  • 5.4. Checking Atlas before and after a deploy

This section documents the staff-only tools available to WHG editors and administrators. Access requires a Django staff account (is_staff=True); a small subset of pages additionally require superuser privileges, noted where applicable.

The WHG admin lives at the standard Django admin URL:

• Production: https://whgazetteer.org/admin/

• Development: https://dev.whgazetteer.org/admin/

Sign in with your WHG staff account to reach the admin index, from which the pages described below are accessible.

Note

The Atlas is documented in Atlas (staff guide), with the operator sections marked as staff-only. Several v4.0 pieces are not yet shipped and are listed at the end of that page: editorial review of submitted gazetteers, contributor oversight and the retention sweep.