> For the complete documentation index, see [llms.txt](https://help.aristotlemetadata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aristotlemetadata.com/creating-and-editing/how-to-move-individual-and-bulk-metadata-into-a-collection.md).
# How to move individual and bulk metadata into a collection
### Moving individual metadata into a collection
1. Go to the metadata item page and click on the Actions dropdown, then select 'Add collections'.
2\. In manage the collections of the item, click on 'Add to new collections'.
3\. A pop-up will show all the existing collections under that stewardship organisation. Select the collection where you want that metadata to move into and then click confirm.
### Moving bulk metadata into a collection
1. Go to the metadata where you want to perform a bulk move to the collection. Check the ones you want to move, then click on 'Bulk Action' and select 'Change collection'.
2\. In the 'Collection to move items to' section, select the collection where you want to move all the selected metadata and click 'Move to collections'.
3\. All the selected metadata has now been moved to the Collection.
---
# 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://help.aristotlemetadata.com/creating-and-editing/how-to-move-individual-and-bulk-metadata-into-a-collection.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.