> 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/version-control-supersede.md).
# Version Control - Supersede
The Aristotle Registry has the functionality to supersede metadata items. Superseding involves replacing an existing version of a metadata item with a new version that contains updated content or revisions. When a metadata item is superseded, it ceases to be the active or current version, and the new version takes its place. However, both versions are retained to maintain a track record of which metadata item superseded another item or which item has been superseded by a specific metadata item. This allows for a comprehensive history of metadata changes and ensures transparency in the evolution of metadata items. The steps to supersede the metadata items are as follows:
* Go to the latest version of metadata item that you have created in the Aristotle registry. Click on Actions, and then click on Edit Supersedes
* Click on "Add a relationship"
* Select the metadata item by which you want this specific metadata item to be superseded. Choose the registration authority, type a message if desired, and select the effective date from which this supersede should take effect, and then click on Submit.
* On the item page, you will see that this item is a supersede to another item.
* If you click on the highlighted 'Address: Postcode' item in the above screenshot, you will see that this metadata item has been superseded by another item, as indicated in the following screenshot.
In this way, we can create supersedes and can keep a track.
---
# 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/version-control-supersede.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.