A simplified, view only UI should be deployed for data consumers, analysts, and report developers who do not otherwise operate within the CP4D environment. The interface should be web based and light weight in nature with a flexible search function to allow users to navigate to information more easily about the data assets whether starting from a term or from the asset name directly and then to easily branch to the various other associated objects such as other business terms or related assets. Below are some proposed features/functions that should be considered.
1. The UI will be built as a Web based wrapper utilizing the existing WKC capabilities to store, gather and report the data dictionary information.
2. The UI should provide access to a robust, faceted and context aware search engine to understand multiple facets of information assets such as name and location, business term assigned, descriptive keywords assigned, linage and hierarchy of the assets in the dictionary.
3. For average users, search the data catalog by business terminology or any portion of description or other associated keywords and return information on all sources of data within the dictionary that match those criteria.
4. For technical users, search by database identification (assets) and return the technical structure of the asset including metadata needed to document/construct the asset.
5. The UI should return sufficient information for the user to understand the asset (table/column) that is associated to the keywords and the ability to display additional information. The additional information should reveal all keywords, descriptions, and other information about the asset as well as the assets position in the hierarchy of data (linage). For technical users the detail should link to the overall structure of the asset within its hierarchy such as links to other tables in the same schema or database structure.
6. The UI should also provide easy to use reporting/export capabilities so that data catalog information can be exported in bulk for use in other IT tools and IT projects. For technical users the export function should create technical metadata or near DDL for assets at the database, schema or table levels.
7. The UI should include “completeness” reporting as well as simple “where used” reporting. There should also be full data linage information recorded for each asset. The UI should be capable of displaying the assets position within the overall data linage hierarchy for that data element.
8. The UI should contain information identifying source system and owner information to aid the end user in identifying and understanding the information provided. Technical connection details may also be provided as an aide to the end user in obtaining access to data via regular enterprise channels and processes. No username/password information will be revealed by the UI.
9. The basic UI should operate without overhead of security authentication so any end user can access information where freely available on assets in a lightweight manner. The system should be extended to carry flags on specific assets which are restricted to control access to this information where appropriate. Access to restricted fields will be controlled by direct calls to AD/LDAP and not require users to be registered uses of the CP4D system itself. End users, except for Data Stewards, would not need access to any CP4D functions and therefore can operate without registration or access to CP4D.
10. The UI should be capable of displaying information related to the Data Stewards estimation of the rating of the data source for “appropriate use”. This is defined as a measure of the data quality contained in the location.
11. The UI will preserve the current functions for Data Stewards to access detailed information on data assets such as Data quality measures from within the current CP4D UI without interruption. Specific data quality details will not be a part of this new UI.
12. The UI will not provide direct access to any data and not return any sample data. The UI will only return metadata related to the asset and its location. No access to Data Virtualization will be provided. Access to details of Data Quality will not be provided by this UI. Those functions will be maintained by Data Steward secure access to the existing CP4D UI and not available to users of the new UI.
Hi Robert, thank you for the detailed enhancement request. Within our Data and AI portfolio, we are planning to introduce a separate Data Product exchange portal to which WKC can publish assets to data consumers, and their access to data can be blocked. The target timing is within the next 6 to 12 months, and it'll be introduced in Saas first.
Regards,
Susanna Tai