Clear all

recommendation for storing automation metadata

Posts: 9
Topic starter
Joined: 2 years ago

Hi, my question is in regard to metadata that a DV engineer would use to generate programs to build and populate raw data vaults.  Databases have plenty of metadata themselves describing the source tables but we also need additional metadata to describe the hubs, links, satellites, etc, and the mappings from the input tables used to populate the defined data vault structures.  This additional metadata needs to be thought through and defined and stored somewhere.

My question is, what are folks mostly commonly using (what format) to store this supplemental metadata?  E.g. do data vault practitioners prefer describing data vault structures and mappings in XML, JSON, or database tables, etc?  There are tradeoffs with each approach.  In your experience what is working well and what is not?

Thanks for your help, Mike

17 Replies