> 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/special-features/activation-pipelines.md).

# Activation Pipelines

Activation pipelines allow users to scan a source database for information, then capture that information in bulk as metadata items in their Aristotle Metadata Registry.

Pipelines themselves are in-registry configurations which represent all of the data that can be imported from a single source. They are made up of 'payloads': snapshots and representations of a single activation event each, confined to the period of time during which a relevant database was 'activated' (imported) into Aristotle.

The contents of each payload are informed by either of:

* [A .CSV file **and** accompanying YAML ruleset](https://help.aristotlemetadata.com/special-features/activation-pipelines/bulk-creating-and-editing-metadata-items-from-a-source-file.md)
* [A JSON ruleset](https://help.aristotlemetadata.com/special-features/activation-pipelines/bulk-creating-and-editing-metadata-items-using-json-instructions.md).

Activation pipelines read and write metadata in a specific order, which is based firstly on item type dependency, then secondarily on metadata hierarchy. This means a pipeline will read and write independent item types first (e.g. glossaries and relations), then move onto dependent item types in hierarchal order, from child to parent (e.g. data elements, then distributions).

By reading their payloads' preprepared YAML, JSON or .CSV files then inserting the data described therein into a registry, activation pipelines:

* Reduce or eliminate the need for manual metadata entry
* Keep an Aristotle registry in sync with source data systems
* Support repeatable and consistent data imports
* Reduce human error by applying standardised metadata mappings
* Allow for scheduled and recurring metadata item updates.

**Notes:**

* Changes made to a source database's already-activated items will be automatically updated within Aristotle, but the reverse is not true. This means that if a change is made to an activated metadata item from within the Aristotle Metadata Registry, and a subsequent change is then made to the same item in its source database, the latter change will undo and overwrite the former
* If any items fail to activate:
  * The remaining items in their payload will **not** attempt to activate
  * Any payloads configured to activate after one containing an item that failed (via the 'Stream' configuration) will not activate until all of the prior payload's items have activated successfully

## Prerequisites

* For any user to manage activation pipelines, the feature must be enabled by Aristotle in the backend of their registry
* For a non-privileged user to manage activation pipelines, they must either:
  * Have the 'Allow user to manage activation pipelines' permission enabled in their [site-wide permissions](https://help.aristotlemetadata.com/single-sign-on/how-to-invite-and-update-permissions-of-aristotle-metadata-staff-on-a-client-registry.md#how-to-change-permissions-of-the-aristotle-staff-on-the-platform) by a Registry Administrator
  * Be added to the list of addon users for their Stewardship Organisation by a Stewardship Organisation or Registry Administrator.

## Functionality of activation pipelines:

Activation Pipelines can be used to create and edit metadata items in bulk based on a combination of:

* YAML instructions
* Either of the below, unique to each payload:
  * A .CSV source file
  * JSON instructions.
