: What strategies are there to document data lineage and keep it updated with a minimum amount of maintenance? Quickly communicating data lineage to other stakeholders in our organization has become
Quickly communicating data lineage to other stakeholders in our organization has become increasingly difficult as we scale.
What are effective strategies to address this and keep it maintained?
An example would be customer data that is stored in a data warehouse, processed in various ways, and used for analysis and reporting. The audience would be members of the business intelligence and analytics teams as well as product managers. The data lineage can change as developers add or modify the code.
More posts by @Vandalay250
: How to get past the cringe factor of reviewing my earliest writing attempts? I’m currently working on a novel that I’m remodelling from an old fanfiction novel I wrote around 6 years ago.
: Fantasy Series - YA or Adult protagonist? I plan on writing a fantasy series at some point. Based on what I've read, my automatic assumption was that the protagonist of such a series would
1 Comments
Sorted by latest first Latest Oldest Best
As your question is fairly general, this answer is too.
I'd insert the ETL process itself into the target database. As you have on-site developers this will have to be included in your extraction development. Best add a bit of architecture description and versioning as well to serve the level of understanding of your consumers.
When going after this I'd include a similar step in the actual extraction run process; even a straightforward run-date and field for comments can be worth gold when attempting to generate trends a year hence.
Terms of Use Privacy policy Contact About Cancellation policy © selfpublishingguru.com2024 All Rights reserved.