# Page Not Found

The URL `activating/typology-of-library-roles` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Saint Paul Public Library, St. Paul, MN](https://civic-switchboard.gitbook.io/guide/case-studies/st-paul-public-library-st-paul-mn.md)
- [Queens Public Library, Queens, NY](https://civic-switchboard.gitbook.io/guide/case-studies/queens-borough-public-library-queens-ny.md)
- [Spokane Public Library, Spokane, WA](https://civic-switchboard.gitbook.io/guide/case-studies-2020/spokane-public-library-spokane-wa.md)
- [Indianapolis Public Library, Indianapolis, IN](https://civic-switchboard.gitbook.io/guide/case-studies-2020/indianapolis-public-library-indianapolis-in.md)
- [Library Roles](https://civic-switchboard.gitbook.io/guide/library-roles.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://civic-switchboard.gitbook.io/guide/case-studies/st-paul-public-library-st-paul-mn.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://civic-switchboard.gitbook.io/guide/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://civic-switchboard.gitbook.io/guide/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/guide/case-studies/st-paul-public-library-st-paul-mn.md`).

You may also use `Accept: text/markdown` header for content negotiation.
