Lineage Metadata Catalogues

Architector allows the data team to maintain central catalogues of things (data ‘assets’) that make up data lineage. The main lineage catalogues are: data terms, processes, physical data, data-stores (or ‘interface files’), and applications (or ‘systems’).

Certain relationships that exist between these assets are also recorded in Architector, and these relationships determine the data lineage.

Catalogue items can be manually maintained through Architector, in which case Architector can act as the master repository. Some catalogues can also be imported from an external master repository.

Component Architecture - Glossary

Architector Components - Catalogues
Metadata Catalogues

Issues Catalogue

Architector also maintains a catalogue of data Issues. Issues can be related to items from other catalogues – for example we may record that a particular process has a timeliness issue because of the manual effort involved. Or we may record that an instance of physical data has a known data quality issue.

Note that issues can be plotted onto lineage diagrams, providing a very useful visual impression of what might be causing the issue, and also what the issue might be impacting. See data lineage for more information.

Data Organisation Catalogue

Architector maintains a list of people who have some responsibility or accountability over data assets. Such people are assigned one or more data management roles, and are also assigned to one or more organization units. Thus Architector can track all data management responsibilities across the entire data lineage, and can also plot this onto certain lineage diagrams.

Manage your data assets centrally, with Architector.

Case studies:

Due to the nature of work we undertake, and the types of clients we typically help, we do not post details of case studies online. Please contact us for more details.