> 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/context-and-concepts/where-do-libraries-fit-in.md). # Where do libraries fit in? For a long time, libraries have helped their communities discover and understand civic data. Libraries have also historically played roles when such data could be collected and preserved. But recent developments around local civic open data have presented an opportunity -- we would say a need -- for library workers to be more directly involved in the entire distributed ecosystem of open data publication, use, and stewardship. This will take us beyond our library buildings, and involve relationships with people who may not consider themselves library users. This is a good thing! One enduring strength of libraries is that they are local community anchors. Although a lot of civic open data exists, they vary in -- just for starters -- how it is published, who is supported to use it, and how it is stewarded. There's not one way to do it, and the form of a strong civic open data ecosystem will necessarily differ from place to place. This is a fantastic opportunity -- it's at the local level that the most innovative and forward-looking ideas around open data are developing. Libraries are firmly connected to local communities; libraries and their workers should be helping to lead the development of their own civic data ecosystems. Moreover, the act of publishing data alone is not likely to result in community impact. Data intermediaries ([read more in our previous section!](/guide/context-and-concepts/defining-a-data-intermediary.md)) are entities that help the public to apply and use data to achieve impact by building relationships among publishers, users, and other members of the ecosystem; improving data, statistical, and technological literacy; enhancing data quality; providing feedback mechanisms to publishers; and building tools that enable broader data use. Sound familiar? Libraries and librarians should act as data intermediaries; their expertise adds value to a wide range of issues that affect both data publishers and users. But a key point for libraries is that this work is not conducted alone. Cultivating a healthy local civic data ecosystem ([more on that coming up, too!](/guide/understanding-your-ecosystem/mapping-your-ecosystem.md)) depends upon the coordinated efforts of a variety of data intermediaries. No single entity can effectively cover all the necessary roles. As your library works in its own ecosystem, it can learn about other players and entities -- our project provides guidance on this ecosystem mapping -- and take roles that complement and strengthen existing capacity. This process has many benefits for your community (especially if you can make the process participatory and inclusive) as well as your institution. Getting involved with civic data probably already aligns with your library mission. Your library probably already considers data literacy as increasingly important for its staff and community to cultivate. It is also likely to consider community engagement, specifically working to strengthen its communities, equally important. Because it's a good strategy for addressing tough problems (and because funding is often tight), collaborating with strategic partners may be a point of emphasis. Developing your library's role in its civic data ecosystem can address all these goals. {% hint style="info" %} Talking Points: Why Libraries Should be Key Participants in their Civic Data Ecosystems \[[PDF](https://github.com/civic-switchboard/guide/blob/master/toolkit/CSTalkingPoints.pdf), [PNG](https://github.com/civic-switchboard/guide/blob/master/toolkit/CSTalkingPoints.png)] This one-sheet provides a set of talking points developed by Civic Switchboard that you can use to advocate to yourself, your colleagues, your administrators, community groups, potential partners, and funders. {% endhint %} --- # 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/context-and-concepts/where-do-libraries-fit-in.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.