> For the complete documentation index, see [llms.txt](https://civic-switchboard.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://civic-switchboard.gitbook.io/guide/library-roles.md).
# Library Roles
Throughout this guide you've read why we believe libraries should be **key actors in civic open data ecosystems**.
This section of the guide offers roles that your library might play in your local civic data ecosystem. The specifics will (and should) be different in different regions.
These roles are meant as a list of possibilities and opportunities. We understand that it is unlikely your library will have the capacity to perform all of them. Libraries are different and at different stages of work with civic data. If you’re at the very beginning of your civic data journey, we hope these descriptions can help you clarify why the library should/could be involved. If your organization has been engaging with civic and open data, these roles may provide you with new ideas and directions for your work.
As you consider potential roles for your library, remember the larger civic data ecosystem. Think about what is already taking place, who is already active, and where you might work in [partnership with other organizations](https://civic-switchboard.gitbook.io/guide/engaging/finding-a-data-intermediary-partne)**.** Remember, other libraries can be partners, too! We have found many cases where different libraries (such as a public and an academic) have capacity and expertise that complements each other around these roles.
### [**Connecting data users**](https://app.gitbook.com/@civic-switchboard/s/guide/library-roles/connecting-data-users)
### [**Connecting data producers** ](/guide/library-roles/connecting-data-producers.md)
### [**Showing the importance of civic data** ](/guide/library-roles/showing-importance-civic-data.md)
### [**Developing civic data literacy**](/guide/library-roles/developing-civic-data-literacy.md)
### [**Advocating for ethical, responsible, and accessible civic data** ](/guide/library-roles/advocating.md)
### [**Making civic data more usable** ](/guide/library-roles/making-civic-data-more-usable.md)
### [**Providing expertise on data management** ](/guide/library-roles/providing-expertise-on-civic-data.md)
### [**Creating civic data** ](/guide/library-roles/creating-civic-data.md)
### [**Using civic data** ](/guide/library-roles/using-civic-data.md)
### [**Publishing civic data** ](/guide/library-roles/publishing-civic-data.md)
### [**Archiving civic data** ](/guide/library-roles/archiving-civic-data.md)
### [**Increasing the library's capacity to do all of the above**
](/guide/library-roles/increasing-the-librarys-capacity.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://civic-switchboard.gitbook.io/guide/library-roles.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.