Data contract implementation best practices

jar
Contributor

Hi all.

We've written some .yml files for our data products in a UC-enabled workspace (dev and prod). We've constructed a directory identical to the one containing the scripts which ultimately creates these products and put them there, initially for governance but we plan to use them programmatically as well in e.g., our workflows.

I've tried to do some reading on whether this is best practice, or what best practice even is for the implementation of data contracts. If anyone would care to share their experience and/or knowledge on the matter, it would be much appreciated!

Best,

Johan.