Differences between Data Flows, Lineage, Provenance and Traceability
[Full article published here due to lack of table functionality in LinkedIn ]
So a question that keeps raising its head in different guises “I've been told I'm on the hook for lineage, what should we do?”. Now strictly the question has normally found its way into Technology’s hands before someone has an opinion of which tool would solve this - aka the “How”. Unfortunately the “What” isn't really known, and worse yet the “Why” often isn't clearly articulated outside of “because the regulator needs it”.
So for this article I wanted to broach a perspective on how all of these parts tie together. Moreover by the end of the article we should have some working definitions that can be leveraged to provide a clear language of data movement concepts that can be enabled to help answer the “Why”.
To read the rest of the article click here.
So the questions I would like to pose to are:
- Are there any major missing scenarios that would be helpful to add to support understanding of Lineage vs Provenance vs Flows?
- Do the terms, scenarios and proposed definitions help clarify?
If you have any comments please use this post on LinkedIn for the comments.
Senior Principal Data Architect specializing in Enterprise Data Modeling and Architecture at Atlassian
3yCould you clarify what "regulatory lineage" means?
Product at Salesforce | Life Sciences Cloud
5yHow does Data Mapping come into play here, if at all?
FinTech Leader | Software and Product Engineering | AWS Certified | Management Consulting
7yWell done article. Too often industry terminology and meaning gets garbled and interchanged when used in practice especially is high visibility subjects. Good to checkpoint every now and then - thanks for sharing!
Retired
7yGreat article. I sense that many people think BCBS requirements stop at Regulatory Lineage. 'Alignment of meaning' is, I think, a bigger challenge .... and a bigger prize!