> For the complete documentation index, see [llms.txt](https://medievalbook.gitbook.io/digitizing-medieval-archives/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://medievalbook.gitbook.io/digitizing-medieval-archives/week-3.md).

# Week 3 - Omeka

This week's exercises involves using Omeka. Sign in to our project website at <http://medievalottawa.org/admin/> with the username and password you set up in week 1. From the **Omeka Dashboard**, click on the tab "Collections" in the sidebar, and find the collection associated with your folio (collection here is used to describe the folios since they possess at least two images which are collected together - i.e. front and back). Scroll through the list until you find yours.&#x20;

Click **edit** which appears in blue underneath the name of the "collection" on the right hand side. Once on the editing page, navigate to the **Dublin Core** tab. **Dublin Core** is a cataloguing standard meant to be inclusive beyond the traditional bibliographic information and thus can theoretically be used to describe any kind of object (e.g. book, statue, code on a disk). We must adapt it to suit medieval manuscripts and thus here is where you will enter all the important **metadata** for your folio.&#x20;

**Metadata** is data that describes other data. In this case, the folio of the manuscript text is being described according to set categories, in part bibliographic (identifying author or title of work if possible, place of origin etc.), in part descriptive (what colour is the parchment, are their doodles in the margins etc.).

In the [next lesson](/digitizing-medieval-archives/week-3/dublin-core.md) we will try to get you used to entering information in Omeka's Dublin Core set up.


---

# 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://medievalbook.gitbook.io/digitizing-medieval-archives/week-3.md?ask=<question>&goal=<endgoal>
```

`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.