#musicbrainz

/

      • legoktm is now known as legoktm[SJS]
      • 2019-05-22 14241, 2019

      • timbl_ has quit
      • 2019-05-22 14258, 2019

      • timbl joined the channel
      • 2019-05-22 14223, 2019

      • timbl has quit
      • 2019-05-22 14211, 2019

      • xplt has quit
      • 2019-05-22 14205, 2019

      • oldtopman joined the channel
      • 2019-05-22 14206, 2019

      • oldtopman has quit
      • 2019-05-22 14206, 2019

      • oldtopman joined the channel
      • 2019-05-22 14212, 2019

      • Nyanko-sensei joined the channel
      • 2019-05-22 14208, 2019

      • D4RK-PH0ENiX has quit
      • 2019-05-22 14211, 2019

      • legoktm[SJS] is now known as legoktm
      • 2019-05-22 14210, 2019

      • kepstin
        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.
      • 2019-05-22 14211, 2019

      • BrainzBot
        MBS-6033: Allow CORS preflights https://tickets.metabrainz.org/browse/MBS-6033
      • 2019-05-22 14251, 2019

      • xplt joined the channel
      • 2019-05-22 14229, 2019

      • Nyanko-sensei has quit
      • 2019-05-22 14209, 2019

      • D4RK-PH0ENiX joined the channel
      • 2019-05-22 14219, 2019

      • xplt has quit
      • 2019-05-22 14217, 2019

      • samj1912 joined the channel
      • 2019-05-22 14234, 2019

      • kuno has quit
      • 2019-05-22 14209, 2019

      • samj1912 has quit
      • 2019-05-22 14228, 2019

      • Freso has quit
      • 2019-05-22 14253, 2019

      • Leftmost has quit
      • 2019-05-22 14219, 2019

      • kuno joined the channel
      • 2019-05-22 14238, 2019

      • Freso joined the channel
      • 2019-05-22 14245, 2019

      • samj1912 joined the channel
      • 2019-05-22 14230, 2019

      • Leftmost joined the channel
      • 2019-05-22 14201, 2019

      • Jybz joined the channel
      • 2019-05-22 14220, 2019

      • BestSteve has quit
      • 2019-05-22 14214, 2019

      • BestSteve joined the channel
      • 2019-05-22 14245, 2019

      • Jybz has quit
      • 2019-05-22 14201, 2019

      • gr0uch0mars joined the channel
      • 2019-05-22 14216, 2019

      • Jybz joined the channel
      • 2019-05-22 14252, 2019

      • samj1912 has quit
      • 2019-05-22 14228, 2019

      • Jybz has quit
      • 2019-05-22 14227, 2019

      • BCMM joined the channel
      • 2019-05-22 14201, 2019

      • Gazooo has quit
      • 2019-05-22 14201, 2019

      • hibiscuskazeneko joined the channel
      • 2019-05-22 14255, 2019

      • Gazooo joined the channel
      • 2019-05-22 14214, 2019

      • i7c has quit
      • 2019-05-22 14214, 2019

      • nioncode has quit
      • 2019-05-22 14214, 2019

      • i9c joined the channel
      • 2019-05-22 14247, 2019

      • i9c is now known as i7c
      • 2019-05-22 14237, 2019

      • nioncode joined the channel
      • 2019-05-22 14208, 2019

      • ZoeB joined the channel
      • 2019-05-22 14236, 2019

      • BCMM has quit
      • 2019-05-22 14210, 2019

      • Vovven_ is now known as Vovven
      • 2019-05-22 14236, 2019

      • Vonter_ has quit
      • 2019-05-22 14208, 2019

      • dolina_ is now known as dolina
      • 2019-05-22 14205, 2019

      • BCMM joined the channel
      • 2019-05-22 14207, 2019

      • hibiscuskazeneko has quit
      • 2019-05-22 14210, 2019

      • D4RK-PH0ENiX has quit
      • 2019-05-22 14211, 2019

      • D4RK-PH0ENiX joined the channel
      • 2019-05-22 14257, 2019

      • bitmap
        yvanzo: that canvas error is apparently harmless (happens for me and on circleci too) but need to check why it happens
      • 2019-05-22 14211, 2019

      • bitmap
        also wrong channel
      • 2019-05-22 14230, 2019

      • Vonter joined the channel
      • 2019-05-22 14249, 2019

      • bitmap
        kepstin: will do, should have a PR ready for today that may end up in the next release
      • 2019-05-22 14230, 2019

      • CatQuest
        !m kepstin and bitmap :O
      • 2019-05-22 14230, 2019

      • BrainzBot
        You're doing good work, kepstin and bitmap :O!
      • 2019-05-22 14209, 2019

      • Vonter_ joined the channel
      • 2019-05-22 14235, 2019

      • Vonter has quit
      • 2019-05-22 14200, 2019

      • hibiscuskazeneko joined the channel
      • 2019-05-22 14241, 2019

      • MusicbrainzB0T joined the channel
      • 2019-05-22 14215, 2019

      • MusicbrainzB0T1 has quit
      • 2019-05-22 14243, 2019

      • Vonter_ has quit
      • 2019-05-22 14239, 2019

      • Vonter joined the channel
      • 2019-05-22 14249, 2019

      • Vonter has quit
      • 2019-05-22 14238, 2019

      • Vonter joined the channel
      • 2019-05-22 14253, 2019

      • tomasparks joined the channel
      • 2019-05-22 14247, 2019

      • BCMM has quit
      • 2019-05-22 14242, 2019

      • gr0uch0mars has quit
      • 2019-05-22 14247, 2019

      • Rotab has quit
      • 2019-05-22 14200, 2019

      • ZoeB has left the channel
      • 2019-05-22 14252, 2019

      • hibiscuskazeneko has quit
      • 2019-05-22 14202, 2019

      • Gazooo has quit
      • 2019-05-22 14253, 2019

      • Gazooo joined the channel
      • 2019-05-22 14219, 2019

      • xplt joined the channel
      • 2019-05-22 14248, 2019

      • testtest joined the channel
      • 2019-05-22 14255, 2019

      • testtest
        Hi, can someone link me to a guide that shows how to delete a release?
      • 2019-05-22 14216, 2019

      • yvanzo
        hi testtest, just click on Remove under Editing in the right sidebar.
      • 2019-05-22 14211, 2019

      • 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.
      • 2019-05-22 14233, 2019

      • testtest
        Ah, I wish I could, but that link isn't present for me.
      • 2019-05-22 14203, 2019

      • testtest
        I see "Add release, Set cover art, Add annotation, Merge, Open Edits, Editing history"
      • 2019-05-22 14238, 2019

      • testtest
        The Release Group in question is here: https://musicbrainz.org/release-group/852f5b91-b0…
      • 2019-05-22 14224, 2019

      • testtest
        yvanzo, here's a screenshot of what I see under "Editing": https://imgur.com/a/PSnJham
      • 2019-05-22 14253, 2019

      • hibiscuskazeneko joined the channel
      • 2019-05-22 14226, 2019

      • lovesegfault joined the channel
      • 2019-05-22 14236, 2019

      • testtest
        Does anyone else have a suggestion on how I can remove this release group (https://musicbrainz.org/release-group/852f5b91-b0… Also, why does the MusicBrainz Web UI suggest pasting an MBID but then treat that MBID as a raw string?
      • 2019-05-22 14254, 2019

      • testtest
      • 2019-05-22 14258, 2019

      • yvanzo
        testtest: the link for deleting a release is on the release page: https://musicbrainz.org/release/2d7f7256-ad86-4ca…
      • 2019-05-22 14219, 2019

      • yvanzo
        testtest: Why do you want to remove it?
      • 2019-05-22 14241, 2019

      • yvanzo
        testtest: If you just want to test the tools, I suggest you to use https://test.musicbrainz.org which is a sandbox.
      • 2019-05-22 14254, 2019

      • 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-f5… 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.
      • 2019-05-22 14226, 2019

      • yvanzo
        testtest: Ok then just go to https://musicbrainz.org/release/2d7f7256-ad86-4ca… and paste https://musicbrainz.org/release-group/df369202-f5… into the Release Group field.
      • 2019-05-22 14230, 2019

      • testtest
        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.
      • 2019-05-22 14218, 2019

      • testtest
        ok, so MBID is the full URL, not the hash after ".../release/"?
      • 2019-05-22 14216, 2019

      • yvanzo
        testtest: No, but you did not paste an actual MBID, see: https://musicbrainz.org/release-group/bfe15a59-b7…
      • 2019-05-22 14251, 2019

      • yvanzo
        At least not a Release Group MBID.
      • 2019-05-22 14216, 2019

      • testtest
        oof. This stuff gets complicated.
      • 2019-05-22 14222, 2019

      • yvanzo
        You pasted a Release MBID, thus it was not recognized as an existing Release Group.
      • 2019-05-22 14200, 2019

      • testtest
        Is there a link that you can direct me to that more clearly explains the differences?
      • 2019-05-22 14217, 2019

      • yvanzo
        alright, to sum up: the MBID you pasted bfe15a59-b78a-44b5-a98b-00dc97893f59 is for release not for release group.
      • 2019-05-22 14235, 2019

      • yvanzo
      • 2019-05-22 14247, 2019

      • yvanzo
      • 2019-05-22 14256, 2019

      • testtest
        I see.
      • 2019-05-22 14208, 2019

      • testtest
        I understand now.
      • 2019-05-22 14220, 2019

      • yvanzo
        It is usually easier to copy/paste URL than just MBID, but both works.
      • 2019-05-22 14230, 2019

      • testtest
        yvanzo: Gotcha, so now that I know that, how does one delete a Release Group?
      • 2019-05-22 14228, 2019

      • testtest
        If you check out the artist Tom T. Hall https://musicbrainz.org/artist/8d8e3514-06fc-4801… , you'll see that there are two 1976 albums named "The Magnificent Music Machine". This is my fault because of the above.
      • 2019-05-22 14204, 2019

      • yvanzo
        testtest: you should just set the correct release group for that release, go to https://musicbrainz.org/release/2d7f7256-ad86-4ca… and paste https://musicbrainz.org/release-group/df369202-f5… into the Release Group field.
      • 2019-05-22 14211, 2019

      • testtest
        You've helped me merge the CD and Cassette release into this release group https://musicbrainz.org/release-group/df369202-f5… so now I want to delete the old, duplicate Release Group https://musicbrainz.org/release-group/f51afc4e-60…
      • 2019-05-22 14232, 2019

      • testtest
        I see, I see - ok
      • 2019-05-22 14223, 2019

      • testtest
        yvanzo: Fantastic! I've successfully cleaned up all the prior edits I did. This is great.
      • 2019-05-22 14213, 2019

      • yvanzo
        testtest: congrats!
      • 2019-05-22 14231, 2019

      • testtest
        https://musicbrainz.org/artist/8d8e3514-06fc-4801… now contains two empty Release Groups that will apparently be cleaned up on a few days.
      • 2019-05-22 14235, 2019

      • yvanzo
        The now empty release group will be automatically removed: https://musicbrainz.org/release-group/f51afc4e-60…
      • 2019-05-22 14242, 2019

      • testtest
        Yep, great.
      • 2019-05-22 14244, 2019

      • yvanzo
        right :)
      • 2019-05-22 14221, 2019

      • yvanzo
        testtest: should the two CD releases be the same in https://musicbrainz.org/release-group/df369202-f5…
      • 2019-05-22 14221, 2019

      • testtest
        And the Release Group with 3 releases has 2 correct ones and 1 duplicate. My guess is that 1 duplicate will also get purged after a few days?
      • 2019-05-22 14236, 2019

      • testtest
        yvanzo: yes, they are identical.
      • 2019-05-22 14243, 2019

      • rdswift
        Nope. It should be merged.
      • 2019-05-22 14253, 2019

      • yvanzo
        So, it is preferred to merge indeed, see https://musicbrainz.org/doc/Merge_Rather_Than_Del…
      • 2019-05-22 14204, 2019

      • Freso
        testtest: Also, if you happen to add two "of the same" of something, please merge ra… what rdswift and yvanzo say. :)
      • 2019-05-22 14215, 2019

      • testtest
        Interesting - ok, hold on, I'll read that right now.
      • 2019-05-22 14251, 2019

      • rdswift
        Same with the duplicate release group that now has zero releases.
      • 2019-05-22 14248, 2019

      • 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.
      • 2019-05-22 14203, 2019

      • testtest
        And this is an organization-wide preference.
      • 2019-05-22 14231, 2019

      • yvanzo
        testtest: yes, because data is mirrored hourly.
      • 2019-05-22 14201, 2019

      • testtest
        I see. Ok, thanks for the help and the heads up.
      • 2019-05-22 14222, 2019

      • yvanzo
        You’re welcome!
      • 2019-05-22 14213, 2019

      • 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?
      • 2019-05-22 14214, 2019

      • testtest
        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.
      • 2019-05-22 14233, 2019

      • yvanzo
        testtest: deleting is still allowed when there is no potential merge target.
      • 2019-05-22 14257, 2019

      • yvanzo
        I mentioned hourly mirroring just as an example of how data can be quickly spread around.
      • 2019-05-22 14252, 2019

      • yvanzo
        Actually new entities can be referenced even more quickly.
      • 2019-05-22 14212, 2019

      • yvanzo
        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.
      • 2019-05-22 14256, 2019

      • testtest
        Thinking more deeply about the issue, I see your point.
      • 2019-05-22 14246, 2019

      • hibiscuskazeneko has quit
      • 2019-05-22 14258, 2019

      • testtest
        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.
      • 2019-05-22 14236, 2019

      • testtest has quit
      • 2019-05-22 14239, 2019

      • reosarevok
        Exactly :)
      • 2019-05-22 14201, 2019

      • reosarevok
        It's not that we never delete stuff (we often do, for example we auto-remove empty artists etc after a few days)
      • 2019-05-22 14210, 2019

      • reosarevok
        It's just if a redirect makes sense, it's better to merge and create one
      • 2019-05-22 14240, 2019

      • reosarevok
        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
      • 2019-05-22 14217, 2019

      • CatQuest
        +100 reosarevok
      • 2019-05-22 14248, 2019

      • CatQuest
        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))
      • 2019-05-22 14211, 2019

      • CatQuest
        then again you know in some time there will be a release that is actulaly named an uuid :D
      • 2019-05-22 14237, 2019

      • CatQuest
        because people amiright?
      • 2019-05-22 14207, 2019

      • reosarevok
        I added a ticket for that, and yes, people areuright
      • 2019-05-22 14230, 2019

      • 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