I have the story -- I suspect this is a rather com...
# advice-metadata-modeling
w
I have the story -- I suspect this is a rather common one -- where in Days of Yore a nice big shared sql database was setup for a startup and everyone used it for everything. As time has passed many tables were added but no one knows who owns which table anymore (or they "know", but disagree!) nor does anyone know who is using which table. I understand how to use DataHub model who owns a table. I'm unsure how to model "yeah this isn't great but these 3 other teams are also using that table directly and not via an api or other intermediary". I found
CUSTOMER
which sounds reasonably close, but that is marked as deprecated: https://github.com/datahub-project/datahub/blob/master/metadata-models/src/main/pegasus/com/linkedin/common/OwnershipType.pdl
g
Owner seems like the wrong place to put some of that info. If I'm understanding correctly, you want to surface: the following teams are the heavy users of some dataset. for that kind of info, the usage aspects might be better place to add new metadata: https://github.com/datahub-project/datahub/tree/master/metadata-models/src/main/pegasus/com/linkedin/usage
w
the following teams are the heavy users of some dataset.
Correct.
usage aspects might be better place to add new metadata:
What that be custom metadata as described in https://datahubproject.io/docs/metadata-models-custom/ ?