bitmap: please give me a shout either here or on MBS-6033 when the cors changes are ready for either beta or the main site, and i'll wire up my page to use that.
yvanzo: that canvas error is apparently harmless (happens for me and on circleci too) but need to check why it happens
also wrong channel
Vonter joined the channel
kepstin: will do, should have a PR ready for today that may end up in the next release
CatQuest
!m kepstin and bitmap :O
BrainzBot
You're doing good work, kepstin and bitmap :O!
Vonter_ joined the channel
Vonter has quit
hibiscuskazeneko joined the channel
MusicbrainzB0T joined the channel
MusicbrainzB0T1 has quit
Vonter_ has quit
Vonter joined the channel
Vonter has quit
Vonter joined the channel
tomasparks joined the channel
BCMM has quit
gr0uch0mars has quit
Rotab has quit
ZoeB has left the channel
hibiscuskazeneko has quit
Gazooo has quit
Gazooo joined the channel
xplt joined the channel
testtest joined the channel
testtest
Hi, can someone link me to a guide that shows how to delete a release?
yvanzo
hi testtest, just click on Remove under Editing in the right sidebar.
testtest
I pasted an MBID into the "Release Group" textbox (which the website UI says it supports), and instead of MusicBrainz doing the correct thing (referencing the MBID) it just straight up created the release group as the raw MBID.
Ah, I wish I could, but that link isn't present for me.
I see "Add release, Set cover art, Add annotation, Merge, Open Edits, Editing history"
Does anyone else have a suggestion on how I can remove this release group (https://musicbrainz.org/release-group/852f5b91-... Also, why does the MusicBrainz Web UI suggest pasting an MBID but then treat that MBID as a raw string?
testtest: If you just want to test the tools, I suggest you to use https://test.musicbrainz.org which is a sandbox.
testtest
yvanzo: I'm trying to cleanup a mistake I made. I've got about ~1,000 albums to add to MusicBrainz. I'm trying to add the first one right now. MB only has the cassette version of this album: https://musicbrainz.org/release-group/df369202-... I own the CD release and want to add it (along with the AcousticID). But I ended up adding 2 releases - one for the cassette, one for the CD.
yvanzo: I'm trying to fix that mistake. In doing that, I thought I'd create a Release Group and combine both the CD and the cassette into that Release Group. But when I made the Release Group, I pasted the MBID into the web UI's textbox (which the website says should work) and it instead created a release group with the name of the MBID.
ok, so MBID is the full URL, not the hash after ".../release/"?
It is usually easier to copy/paste URL than just MBID, but both works.
testtest
yvanzo: Gotcha, so now that I know that, how does one delete a Release Group?
If you check out the artist Tom T. Hall https://musicbrainz.org/artist/8d8e3514-06fc-48... , you'll see that there are two 1976 albums named "The Magnificent Music Machine". This is my fault because of the above.
testtest: Also, if you happen to add two "of the same" of something, please merge ra… what rdswift and yvanzo say. :)
testtest
Interesting - ok, hold on, I'll read that right now.
rdswift
Same with the duplicate release group that now has zero releases.
testtest
I see, ok, so MB prefers to merge items - even when those items are erroneously added and very quickly (within 60 seconds or so) caught - rather than delete.
And this is an organization-wide preference.
yvanzo
testtest: yes, because data is mirrored hourly.
testtest
I see. Ok, thanks for the help and the heads up.
yvanzo
You’re welcome!
testtest
Also, far be it from me to judge infrastructure I haven't worked on, but if the solution to data inconsistency is disallow deletions and instead just use merges, does that not feel like a pretty big design weakness that ought to be looked at more closely?
I'm sure there's a lot of complexity to how MusicBrainz actually runs their services, but man... I would have imagined the mirroring policy would be something that wouldn't dictate which actions an end user could perform.
yvanzo
testtest: deleting is still allowed when there is no potential merge target.
I mentioned hourly mirroring just as an example of how data can be quickly spread around.
Actually new entities can be referenced even more quickly.
testtest: so I don’t really see the design issue here, we just don’t want to have broken links whereas it could redirect to the appropriate target.
testtest
Thinking more deeply about the issue, I see your point.
hibiscuskazeneko has quit
You can control what links to things when you're inside the MusicBrainz universe, but if those links are embedded in places you don't control (i.e., metadata for FLAC files on someone's music player), you don't want those links to become broken. Hence the preference for merge instead of delete.
testtest has quit
reosarevok
Exactly :)
It's not that we never delete stuff (we often do, for example we auto-remove empty artists etc after a few days)
It's just if a redirect makes sense, it's better to merge and create one
If a redirect does not make sense (you added an artist who turned out not to exist after all or something) then letting it be removed is just fine
CatQuest
+100 reosarevok
hmm should the release group thingy or other recordings thing, catch that something *is* an mbid even if it isn't the appropriate one though? to prevent this? (also on a rare occasion when server is slow or user browser, sometimes pasting f.ex an mbid correctly als oresults in error (has happened to me a few times))
then again you know in some time there will be a release that is actulaly named an uuid :D
because people amiright?
reosarevok
I added a ticket for that, and yes, people areuright
CatQuest
haha i just read it in #meta. so you guys beat me to it. i feel pleased i'm on the right track atleast
