Closed mandy-chessell closed 2 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.
Egeria's open metadata labs use python notebooks to drive sequences of REST API calls to Egeria's runtime platform called the OMAG Server Platform. There is one function called
printAssetUniverse
that needs work. This function is designed to provide a data scientist with detailed information about an Asset (such as a file or a database). This includes name, description, its location, content, classification, profile information, comments and other feedback, who owns it, etc.At the moment the function just returns the basic information and prints out the Json from the REST API call like this:
The counts at the end indicate what other information is potentially available. This is a small example of an asset, but the information returned could be very extensive.
We are looking for a function that extracts as much information as is avalable and displays it in a useful way to help a data scientist decide if this asset is going to be useful.
This link gives some background on what can be stored about an asset. https://egeria.odpi.org/open-metadata-publication/website/cataloging-assets/
The call to printAssetUniverse is in the inderstanding-an-asset.ipynb in the asset-management-labs: https://egeria.odpi.org/open-metadata-resources/open-metadata-labs/