We have quite a few examples of this in the Knowledge Base:
And in the Aristotle.Cloud user guide examples: Collections | Data Lineage Examples - Aristotle.Cloud
At the moment, we only support Data Lineage being done at a Dataset level using provenance records and these can be used to specify a source data set, with associated information.
We are currently undergoing development of an extension to Aristotle based on feedback from several clients to support linkages at the Distribution and logical path levels to allow for direct linkage between data tables.
In response to your summary questions:
-
How do we best represent data flow across tables across different data platforms?
- At the moment, using the provenance records for datasets. In future this can be done between tables as well.
-
Confirm that logical_path is the best place to document the physical column name of a physical distribution? (we’ve always done it this way, but someone’s tried to tell me otherwise recently)
- Yes, the logical_path is where I would recommend storing the column name information. This field is designed to map between a field in a data file (column name, XML element name, etc…) to a data element – so this is the perfect place for the column name to go.
-
How best to locate whether a physical table is actually documented in Aristotle when all I know right now is the physical name?
- All custom fields are searchable using the search in Aristotle, so if the Physical name is stored against the item, searching for it should return the right results in search for this.
- Also, because we’ve not added the ability to capture alternative names Services Australia can start using this to define and record Physical Names against distributions. In an upcoming update, we are also going to be adding the ability to search and filter based on alternative names in the updated browse pages as well.
🐜 Alternative Name Types are now available for all users!