Has anyone extended their metadata tracking to API...
# getting-startedh
high-hospital-85984
09/25/2020, 4:37 PMHas anyone extended their metadata tracking to APIs, either third or first party? As this seems to require a new entity etc, I’d be interested to know how you modelled it? Thanks!
b
bumpy-keyboard-50565
09/25/2020, 5:55 PMWe do plan to add that new entity in the near future (it's on our roadmap). We're doing that internally inside of LinkedIn.
a
acceptable-architect-70237
09/25/2020, 6:55 PMCan you explain a little more about what's your use case of
metadata trackingb
bumpy-keyboard-50565
09/25/2020, 7:58 PMActually that's a good point. I automatically assume @high-hospital-85984 meant cataloging. Maybe he meant something else.
h
high-hospital-85984
09/26/2020, 7:29 AMSorry for being unclear. We’re mostly interested in cataloging and lineage. So for example we extract our surveymonkey responses from their API and load it into our warehouse, and we want to keep track of where the data in the given table came from
high-hospital-85984
09/26/2020, 7:30 AMBut good to see that it’s on the roadmap!
b
bumpy-keyboard-50565
09/26/2020, 11:33 AMGot it. Yeah that's very similar to our internal use case. @kind-restaurant-94053 FYI