2023-05-22 - Autogenerated History Rules Iteration¶
Problem¶
If a Data Magician forgets to specify a business effective date for their dropped data files (the landing rule), and those files contain multiple change records for the same id/key then we can’t identify the sequence that the changes occurred.
Solution¶
Identify potential effective date column from most commonly known field patterns and include in autorule.
Leverage the Magic¶
This is a magical feature in that Data Magicians can drop a file and we will attempt to identify the business date in the data and automatically create and apply the correct effective date rule.
ADI¶
Whoot!, another piece of magic that removes any need for the Data Magician to understand complex data architecture or do extra effort.
Customer¶
Yaasss!, the filedrop feature just seems to manage any file like magic.
Magician Partner¶
Identify potential effective date column from most common known (double check there aren’t more) and include in auto rule. Simplifies the pattern and supports the next interface which will be the data contract etc “Effective Date” “Start Date” “Effective From” “Effective Begin Date” “Effective Start Date” “Effective Timeframe” “Validity Start Date” “Date From” “Effective Period” “Active Start Date” These column names are typically used to store the date when a particular record became effective or valid. They are commonly used in databases that store time-sensitive data, such as human resources, financial records, or inventory management systems. By keeping track of the effective date of each record, these databases can provide accurate historical data and facilitate auditing and reporting.
Last Refreshed¶
Doc Refreshed: 2024-03-02