opendataalex / kettle-metadata-repository Goto Github PK

As a KMR user, I should be able to compare actual database schema to proposed or logical schema adaptations (i.e. if a physical schema does not use foreign keys and the logical/proposed schema does, I should be alerted on the schema's page).

While developing business formula logic, names of fields should automatically become links to those actual fields.

As a KMR user, I want to be able to monitor the quality of the data in all systems being tracked with the toolset. If specific quality events occur (i.e. tolerance levels surpassed), alerts should be sent out and the issues made known.

As a KMR user, I should be able to trace data from source systems through to the data warehouse, data marts, and any end-user solutions. This way if a change occurs in a source system I will be able to quickly perform an impact analysis and estimate the amount of work resulting from the change.

As a KMR user, I should have a way to visualize changes or schema status so that I can take action as necessary.

As a KMR user, I need to see the basic information for tables and columns of databases I want monitored. Database relationships should also be tracked. KMR should also keep revision history so we can track how the data has changed.

As a KMR user, I need to be able to expand on the basic information provided from the initial database schema reference material. Business definitions of tables/columns should also be versioned so historical changes can be monitored.