Skip to main content

About the Reltio collector

Use this collector to harvest metadata from your Reltio Master Data Management platform. The collector harvests metadata from the Reltio configuration file, which is exported from the Reltio Master Data Management platform.


The Reltio collector can be run in the Cloud or on-premise using Docker or Jar files.


The latest version of the Collector is 2.210. To view the release notes for this version and all previous versions, please go here.

What is cataloged

The Reltio metadata collector runs against a static configuration file which contains the following information:

  • Classes (what Reltio calls entity types) and properties (what Reltio calls attributes). Essentially, a type structure that expresses key business objects in your domain.

  • Association classes (what Reltio calls relation types) that are classes that express relationships between other entities. For example, Employee entity has a relationship to Company entity, and the relationship has start date and end date attributes.

  • Inheritance relationships between entity types.

  • Special objects called survivorship groups that express how conflicting data for a given attribute is resolved (that is, if two sources of data conflict, take the one that’s most recent. or take the value from System A over System B.) Basically, a directed graph of objects that is associated with an attribute on an entity.

  • Roles that are groupings of entities to express transient typing. For instance, a Person and an Organization can both be in the role of Customer. But a given person can be a customer today and an employee tomorrow.

  • Attributes (which can be defined apart from entities, allowing them to be reused) that have properties like type, name, label, hidden, faceted, required, searchable.

  • Data cleansers that can transform the values of attributes from one form to another. A common example is a cleanser for street address that translates ST, St., and Str to Street. An Entity Type is configured with zero to many cleansers that can be arranged in chains.

  • Matchers for entities that determine if two entities are the same. So two person entities might be the same if their SSN attributes are equal or if their cleansed names are fuzzy-matched within a certain threshold.

  • Survivorship strategies that express how to merge data from two entities that have been judged to be the same. Basically, which attribute values from the merged entities “win” as the value of the attribute for the final, combined entity.

  • Graph Types that appear to define specific hierarchies of relationships with distinct semantic meaning.

  • Interaction Types that define events in which member Entity Types participate. Each interaction/event can have its own attributes.

The Reltio collector focuses on Entity Types, Attributes, Roles, and Relationships and does the following:

  • Identifies the matchers and cleansers assigned to each class by name.

  • Works on a static configuration.

  • Identifies the first cleanser in a chain, if there is a multi-level chain.

  • Identifies the survivorship strategy for each attribute (property) by name.

  • It does not produce glossary terms.