> For the complete documentation index, see [llms.txt](https://carare.gitbook.io/share-3d-guidelines/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://carare.gitbook.io/share-3d-guidelines/3d-process/metadata.md).

# Metadata

Running in parallel to the 3D capture, modelling and publication activities, the creation of metadata is essential to the success of the processing pipeline. The metadata created within the pipeline provides key information and context data to five key areas:

1. It describes in detail the artefact or monument which is being modelled in 3D and its provenance
2. It describes in detail the digital representation of the artefact or monument and its online location
3. It provides technical information and quality insurance on the processes and methods utilised in the digitisation and modelling of heritage objects
4. It provides information on the access, licensing and reuse of the created 3D models and any associated digital content
5. It enables the search, discovery and reuse of content through the mapping of metadata to aggregators e.g. Europeana Data Model (EDM)


---

# 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://carare.gitbook.io/share-3d-guidelines/3d-process/metadata.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.