Federator
Federation refers to the process of metadata being copied and kept up to date between two related Aristotle Metadata Registries. Once a federation rule has been configured in a registry, metadata items held within a second registry can be copied into it, and any changes to these items in the second registry will be periodically updated.
Federation ensures metadata items are able to stay up to date across two or more related registries. Because every federation uses a Universally Unique Identifier (UUID), the same UUID will refer to the same metadata item across all registries, regardless of the registry the item is viewed from!
Prerequisites
The Federator must be enabled by Aristotle as part of your Aristotle Metadata Registry Plan before it can be used.
Notes:
Federation of an external registry's items does not require anything to be set up on the source registry's side
For a metadata item to be able to be federated, it must be:
Able to be endorsed by a registration authority
Published and visible to non-authenticated (logged-out) users
Publicly accessible.
When a federation rule is set up and run for the specified given metadata items, it will copy all related component metadata items as well. For example:
When copying a data element, any related data element concepts, value domains, object classes and properties will also be copied
When copying an indicator, any related data elements and their components will also be copied
When copying a distribution, any related data elements and their components will also be copied.
If any related items or components do not meet the conditions listed above, they will not be copied
Endorsement information, such as registration status or registration authority information is never copied.
Last updated