> For the complete documentation index, see [llms.txt](https://bcds.gitbook.io/handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bcds.gitbook.io/handbook/digital-scholarship-methods/overview/digital-exhibits.md). # ΒΆ Digital Exhibits Like physical exhibits, digital exhibits require research, curation, the writing of captions and other contextual information, information organization, and design. Beyond displaying and contextualizing digitized or [born-digital](https://en.wikipedia.org/wiki/Born-digital) materials like historical documents, photographs, film footage, or audio clips, digital exhibits allow for such things as linking to outside resources and the incorporation of a variety of digital objects like maps and timelines. Digital exhibits often come from existing digital collections or begin with the creation of a digital collection, which requires digitization and [metadata](https://en.wikipedia.org/wiki/Metadata) generation among other steps. --- # 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://bcds.gitbook.io/handbook/digital-scholarship-methods/overview/digital-exhibits.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.