I reported a metadata issue yesterday, but my report still hasn’t appeared in the Support / Metadata section. Should I submit it again or wait a little longer ?
There shouldn’t be a delay.
If you didn’t get a conformational email I would resubmit.
Thanks, @Carl.
I didn’t receive a confirmation email.
Support Requests raising a metadata issue go directly to the tech support team who will respond via PM as necessary.
There is no confirmation email sent out automatically in this case.
However, there should be confirmation email sent out automatically in this case.
Roon Labs have told us that this system (for metadata issues) isn’t permanent or perfect but it is working as designed for now.
Thanks, @Geoff_Coupe. I’ll wait a bit, and if my report doesn’t appear in the appropriate section, I’ll submit it again.
No need - there won’t be a post appearing in the Support > Metadata category of the forum - the report has already been passed to the appropriate team when you first submitted your report and marked it as a metadata issue.
Ok this is new to me. What’s the purpose of Support > Metadata now, in this case?
Presumably a legacy holdover, or a catch-all when people don’t use the TypeForm submission process?
As Joel has retired, could this mean no one is covering this from Roon in an active open role on the forum?!
(Not a question to @Suedkiez )
1 Like
OK. Not being sure what will happen to my request, I’m posting a copy here just in case.
There is a mix of albums in the discography for the band « Siiilk ».
It also includes albums by a band named « siiilk. » (with a period).
Here is an image showing the unwanted albums inside the red rectangles.
I would appreciate it if a moderator could notify a metadata manager.
Thanks in advance. dp
I was told that such misattributions for small artists can’t be fixed because Roon Labs doesn’t have the resources
It’s sad… 
Yeah, but the fault is also with those who create them and Roon alone can’t fix the world.
If I understood the comment right, maybe there will be rearchitected solutions in the future, but I understand they can’t manually fix the probably millions of cases.
To be sure I’m not misrepresenting anything, here’s the reference:
1 Like
Understood, thank you.
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.
4 Likes
I should add that as we perfect the mechanics of this current system, we’ll then work to improve the user experience and expand our transparency. For now, the focus is on tightening the loop from report to correction.
4 Likes
Hello @connor, thanks for your message.
I haven’t received an email. Nothing in my spam folder; perhaps it was filtered out before reaching me?
Regarding Tidal, there is indeed an error, but it only affects one single:
It’s the same story on Qobuz, actually:
And on Deezer:
And on Amazon Music:
But not on Spotify; there, it’s correct:
