Hi everyone,
We wanted to provide some context here so users aren’t left to speculate about the machinery of metadata escalation.
First off, there were a few systematic tweaks to make cloud metadata corrections sustainable after Joel’s departure from Roon.
At this time:
Every metadata report we receive via our Typeform automatically generates an internal ticket for review with our entire data team.
Users receive an email confirming their submission was received and letting know that our team will follow up directly only as necessary if we require further information.
The data team reviews the proper course of action and escalates to external partners as necessary. They can also apply pressure to external partners directly for overdue fixes.
You’ll notice this new format is somewhat opaque to users. This is not the result of a divestment of resources; quite the opposite. The data team now has formal delegation to handle these requests in real-time and we’re rapidly shortening the correction cadence with our metadata partners. More importantly, our documentation trail is precise and complete, and we’re equipping our partners to make corrections faster.
So, paradoxically, this decreased visibility is a symptom of us correcting things faster. Metadata reports are a firehose, not a trickle, and that volume is better served by escalating straight to the data team than by working each case through the forums.
@Dirk-Pitt, your report was received and ticketed for review by the team yesterday morning. It’s in the queue currently. They’ll reach out if they require additional context. The botched performer equivalency is coming from Tidal, from what we can see, so this will require escalation to their catalog team on our end.
We’ll confirm the confirmation email trigger is active for submissions still, but please check spam folder to ensure it wasn’t flagged there.
Thanks everyone and happy to answer any questions.