Data Lineage 104: Documenting data lineage
In the first three articles (Data Lineage 101, 102 and 103) we have discussed why we need data lineage, what data lineage actually is and what are the key legislative requirements for data lineage.
In the first three articles (Data Lineage 101, 102 and 103) we have discussed why we need data lineage, what data lineage actually is and what are the key legislative requirements for data lineage.
In ‘Data Lineage 102: Definition and key components’ we aligned the definition of data lineage and specified its key components from the viewpoint of data management. Now it is time to take a look at the requirements from the viewpoint of legislation.
In ‘Data Lineage 101: What’s so special about data lineage?’ we discussed why data lineage triggers such an interest among business, IT and data management professionals. Now it is time to take a deeper dive into what data lineage actually is.
During the past few years, I have noticed growing interest in data lineage. Data lineage has become a hot topic in the data management community.
One of our core duties as stewards of corporate resources is deciding how to deploy our company’s capital. Building and maintaining an asset portfolio and corresponding financing package that aligns with the ongoing mission of the company takes thoughtful preparation and analysis. Developing the standards, processes and tools that support long term, strategic decision making is an important step in achieving this rigor.