#188 Controversial Opinion: You Must Register Your Use Case With the Data Producer - Mesh Musings 42

<p><a href="https://www.patreon.com/datameshradio" rel="noopener noreferrer" target="_blank">Data Mesh Radio Patreon</a> - get access to interviews well before they are released</p><p>Episode list and links to all available episode transcripts (most interviews from #32 on) <a href="https://docs.google.com/spreadsheets/d/1ZmCIinVgIm0xjIVFpL9jMtCiOlBQ7LbvLmtmb0FKcQc/edit?usp=sharing" rel="noopener noreferrer" target="_blank">here</a></p><p>Provided as a free resource by DataStax <a href="https://www.datastax.com/products/datastax-astra?utm_source=DataMeshRadio" rel="noopener noreferrer" target="_blank">AstraDB</a>; George Trujillo's contact info: email (<a href="mailto:george.trujillo@datastax.com" rel="noopener noreferrer" target="_blank">george.trujillo@datastax.com</a>) and <a href="https://www.linkedin.com/in/georgetrujillo/" rel="noopener noreferrer" target="_blank">LinkedIn</a></p><p>I share my strongly held belief that every data product consumer MUST register their use case with the producer and why it is so crucial and important. I sum up with these points:</p><ol><li>Data isn't ever going to be self-describing, at least not deep, context rich data and it definitely won't be as we focus on data democratization. So, you need to register your use case to make sure you and the producer are on the same page for what is truly being shared</li><li>Data producers don't know what data consumers want - and especially don't know what potential data consumers want - without more information/conversation. Data producers kinda suck at doing that right now so help them out and improve the information flow. Who knows, they might have something way better for ya</li><li>You might actually be able to get at a heck of a lot more useful information if the producer 1) understands your use case and knows they can give you access to the PII/sensitive stuff because your use case is fine on ethical/legal/regulatory checks and/or 2) you are taking on the risk around if you violate ethical/legal/regulatory bounds. </li><li>You need