#musicbrainz

/

      • balrog joined the channel
      • 2020-06-06 15836, 2020

      • Hexadigital has quit
      • 2020-06-06 15832, 2020

      • Hexadigital joined the channel
      • 2020-06-06 15850, 2020

      • supersandro2000 has quit
      • 2020-06-06 15858, 2020

      • supersandro20000 joined the channel
      • 2020-06-06 15849, 2020

      • supersandro20000 has quit
      • 2020-06-06 15807, 2020

      • supersandro2000 joined the channel
      • 2020-06-06 15839, 2020

      • d4rkie has quit
      • 2020-06-06 15801, 2020

      • D4RK-PH0ENiX joined the channel
      • 2020-06-06 15800, 2020

      • Joah joined the channel
      • 2020-06-06 15854, 2020

      • trolley has quit
      • 2020-06-06 15829, 2020

      • trolley joined the channel
      • 2020-06-06 15837, 2020

      • Vacuity joined the channel
      • 2020-06-06 15815, 2020

      • Vacuity_ has quit
      • 2020-06-06 15822, 2020

      • Joah has quit
      • 2020-06-06 15828, 2020

      • MusicbrainzB0T1 joined the channel
      • 2020-06-06 15811, 2020

      • MusicbrainzB0T has quit
      • 2020-06-06 15803, 2020

      • PileOfDirt joined the channel
      • 2020-06-06 15802, 2020

      • MRiddickW has quit
      • 2020-06-06 15830, 2020

      • MRiddickW joined the channel
      • 2020-06-06 15837, 2020

      • RustyFork joined the channel
      • 2020-06-06 15839, 2020

      • plutes has quit
      • 2020-06-06 15857, 2020

      • albertus1 joined the channel
      • 2020-06-06 15835, 2020

      • JasmineSummer joined the channel
      • 2020-06-06 15833, 2020

      • JasmineSummer has quit
      • 2020-06-06 15802, 2020

      • Gazooo has quit
      • 2020-06-06 15842, 2020

      • Gazooo joined the channel
      • 2020-06-06 15826, 2020

      • CallerNo6 has quit
      • 2020-06-06 15849, 2020

      • xplt joined the channel
      • 2020-06-06 15810, 2020

      • plutes joined the channel
      • 2020-06-06 15819, 2020

      • JoeLlama joined the channel
      • 2020-06-06 15814, 2020

      • CallerNo6 joined the channel
      • 2020-06-06 15814, 2020

      • CallerNo6 has quit
      • 2020-06-06 15814, 2020

      • CallerNo6 joined the channel
      • 2020-06-06 15824, 2020

      • MRiddickW has quit
      • 2020-06-06 15802, 2020

      • JoeLlama has quit
      • 2020-06-06 15846, 2020

      • Joah joined the channel
      • 2020-06-06 15808, 2020

      • Joah has quit
      • 2020-06-06 15829, 2020

      • dseomn has quit
      • 2020-06-06 15829, 2020

      • MRiddickW joined the channel
      • 2020-06-06 15855, 2020

      • dseomn joined the channel
      • 2020-06-06 15810, 2020

      • Rotab
      • 2020-06-06 15813, 2020

      • Rotab
        a disambiguation and a half :p
      • 2020-06-06 15819, 2020

      • darkstardev13 joined the channel
      • 2020-06-06 15839, 2020

      • AJ_Z0 has quit
      • 2020-06-06 15835, 2020

      • AJ_Z0 joined the channel
      • 2020-06-06 15815, 2020

      • Zastai joined the channel
      • 2020-06-06 15803, 2020

      • JoeLlama joined the channel
      • 2020-06-06 15807, 2020

      • chrysn
        I'm having trouble looking up things by their Amazon IDs. Both when using the indexed search with advanced query syntax frontend and the API (eg. using python-musicbrainzngs), I find some, but not others.
      • 2020-06-06 15808, 2020

      • chrysn
        Example: https://musicbrainz.org/search?query=asin%3AB06X1… comes up empty, but https://musicbrainz.org/release/c151419a-f7d8-4be… shows the queried ASIN B06X15V4D6 in the list as the `DE` (German) ASIN.
      • 2020-06-06 15849, 2020

      • chrysn
        I've tried some variations of querying for `asin:"DE: B06X15V4D6"` and similar, but didn't find a prefix.
      • 2020-06-06 15821, 2020

      • chrysn
        Is there some trick here that I could use?
      • 2020-06-06 15810, 2020

      • chrysn
        The next best thing that'd come to mind would be to construct the (hopefully canonical) Amazon URI for a German ASIN, look that up, and walk back the relationships
      • 2020-06-06 15815, 2020

      • chrysn
      • 2020-06-06 15827, 2020

      • chrysn
        but that sounds needlessly complicated when there is already a query-by-ASIN feature.
      • 2020-06-06 15838, 2020

      • JoeLlama has quit
      • 2020-06-06 15845, 2020

      • PileOfDirt has quit
      • 2020-06-06 15838, 2020

      • oldtopman has quit
      • 2020-06-06 15837, 2020

      • oldtopman joined the channel
      • 2020-06-06 15852, 2020

      • Zastai
        problem seems to be that only one ASI gets stored on the release itself
      • 2020-06-06 15805, 2020

      • Zastai
      • 2020-06-06 15831, 2020

      • Zastai
      • 2020-06-06 15842, 2020

      • Zastai
        only the UK ASIN is stored on the release.
      • 2020-06-06 15839, 2020

      • Zastai
        might be worth logging a ticket for this. I think the assumption is/was that an ASIN is the same across Amazons for a single release
      • 2020-06-06 15832, 2020

      • Zastai
        it's a reasonable assumption, and I'd be inclined to think at least one of the ASINs on that release does not belong there, but on another release in the same RG
      • 2020-06-06 15843, 2020

      • Zastai
        but that does not mean searching for them should not work
      • 2020-06-06 15842, 2020

      • exmortus joined the channel
      • 2020-06-06 15857, 2020

      • dseomn has quit
      • 2020-06-06 15816, 2020

      • dseomn joined the channel
      • 2020-06-06 15832, 2020

      • plutes has quit
      • 2020-06-06 15831, 2020

      • d4rkie joined the channel
      • 2020-06-06 15808, 2020

      • D4RK-PH0ENiX has quit
      • 2020-06-06 15820, 2020

      • MRiddickW has quit
      • 2020-06-06 15809, 2020

      • Zastai
        approved
      • 2020-06-06 15821, 2020

      • Jormangeud has quit
      • 2020-06-06 15828, 2020

      • Jormangeud joined the channel
      • 2020-06-06 15824, 2020

      • atsampson has quit
      • 2020-06-06 15846, 2020

      • atsampson joined the channel
      • 2020-06-06 15814, 2020

      • evelyn
        hmm I created an artist but autocorrect gubbed the name: https://musicbrainz.org/artist/0031a23d-e15d-402c… I managed to change the main name and that was automatically applied (and it's done it for one recording automatically), but it seems that changing the name for the other two is going to take 4 days :(
      • 2020-06-06 15843, 2020

      • Joah joined the channel
      • 2020-06-06 15852, 2020

      • evelyn
        I don't really understand how the first edit of the recording artist applied automatically, but the other two didn't.
      • 2020-06-06 15853, 2020

      • evelyn
        The artist and recordings are definitely not depended on by other entries on the database either
      • 2020-06-06 15844, 2020

      • oldtopman has quit
      • 2020-06-06 15856, 2020

      • rdswift
        I've approved them for you.
      • 2020-06-06 15809, 2020

      • evelyn
        ok, thanks! it still seems to show it for one of them though: https://musicbrainz.org/release-group/f476c5eb-53…
      • 2020-06-06 15840, 2020

      • evelyn
        (I tried setting another edit for that one but not sure if that is the solution)
      • 2020-06-06 15814, 2020

      • evelyn
        I think I must be getting mixed up between changing the name of the group itself and changing the recording artist for individual groups after the fact
      • 2020-06-06 15850, 2020

      • evelyn
        Does an edit need to be made to each release group, release, and any recordings?
      • 2020-06-06 15810, 2020

      • evelyn
        ooh thanks
      • 2020-06-06 15817, 2020

      • rdswift
        I think they all say Can Cala now.
      • 2020-06-06 15820, 2020

      • rdswift
        I'm guessing that when you changed the artist's name on the artist record, you didn't check the Artist Credits section to automatically update the name on the related records.
      • 2020-06-06 15844, 2020

      • evelyn
        Yeah :/ I guess it's not that awkward because they've only set three singles though
      • 2020-06-06 15852, 2020

      • plutes joined the channel
      • 2020-06-06 15816, 2020

      • evelyn
        hmm I've made two more edits on the recordings, not sure if that is the solution: https://musicbrainz.org/artist/0031a23d-e15d-402c…
      • 2020-06-06 15822, 2020

      • oldtopman joined the channel
      • 2020-06-06 15800, 2020

      • ren0v0 has quit
      • 2020-06-06 15828, 2020

      • rdswift
        I think they have all be approved now.
      • 2020-06-06 15836, 2020

      • evelyn
        thanks a lot! that has done the trick
      • 2020-06-06 15847, 2020

      • evelyn
        I will make sure to check that box in future
      • 2020-06-06 15832, 2020

      • evelyn
        is there a way for me to remove the erroneous alias?
      • 2020-06-06 15807, 2020

      • rdswift
        The easiest way (I think) is when you update the artist credits on the tracks, make sure to check the box on the recordings page to update the recordings as well.
      • 2020-06-06 15843, 2020

      • evelyn
        actually, I think it is not an alias, it is an orphan artist credit. but I can't find anywhere where it is still referenced
      • 2020-06-06 15859, 2020

      • ren0v0 joined the channel
      • 2020-06-06 15858, 2020

      • rdswift
        Where are you seeing it (link)?
      • 2020-06-06 15852, 2020

      • rdswift
        There was one case where there was still an artist credit of Clan Cala on one track on one of the releases. I removed the "Credited As" so that it used the artist's name, and then cascaded that to the associated recording.
      • 2020-06-06 15834, 2020

      • evelyn
        ah, I'm not seeing it anymore - I think it might be an issue on my end
      • 2020-06-06 15804, 2020

      • evelyn
        it was in the 'aliases' tab, but I think it was probably my browser caching it (although I definitiely saw the changes you approved)
      • 2020-06-06 15805, 2020

      • rdswift
        You can see what I did at https://musicbrainz.org/edit/70438386
      • 2020-06-06 15817, 2020

      • rdswift
        You actually still had one track with the Clan Cala alias, which was why you were probably seeing it. My edit fixed that.
      • 2020-06-06 15819, 2020

      • evelyn
        yup, I see what you've done. much appreciated!
      • 2020-06-06 15810, 2020

      • rdswift
        No problem. Thanks for entering the information in the first place.
      • 2020-06-06 15840, 2020

      • evelyn
        hmm new question incoming
      • 2020-06-06 15850, 2020

      • evelyn
        so I understand it is best to merge rather than delete: https://musicbrainz.org/doc/Merge_Rather_Than_Del…
      • 2020-06-06 15819, 2020

      • evelyn
        so, I'm making a new release. To make it easier, I decided to base this new release on the release with the erroneous track titles.
      • 2020-06-06 15801, 2020

      • evelyn
        However, this creates a situation where it uses the erroneous recordings. Therefore, I am presented with the option where I can update the recording title to match the track title.
      • 2020-06-06 15850, 2020

      • evelyn
        What exactly does this do? It seems to me that it will change the titles of the recordings that I'm using (of the old release). It is not adding new recordings. Is that desirable? Should I add new recordings and then merge thereafter?
      • 2020-06-06 15825, 2020

      • darkstardev13 has quit
      • 2020-06-06 15846, 2020

      • evelyn
        Similarly there is an option when selecting the old release group to copy the release title to the release group.
      • 2020-06-06 15828, 2020

      • levine
        evelyn: Does this answer your question? https://musicbrainz.org/doc/Style/Recording#Title If not, could you provide some more context? What release is it?
      • 2020-06-06 15804, 2020

      • d4rkie has quit
      • 2020-06-06 15846, 2020

      • evelyn
      • 2020-06-06 15858, 2020

      • D4RK-PH0ENiX joined the channel
      • 2020-06-06 15803, 2020

      • evelyn
        there are spelling mistakes in the titles and it's formatted horribly (nothing like the bandcamp page)
      • 2020-06-06 15819, 2020

      • evelyn
        So I'm adding a new release with corrected titles.
      • 2020-06-06 15846, 2020

      • levine
        evelyn: Can't you correct the release, instead of adding a new one?
      • 2020-06-06 15859, 2020

      • levine
        Ah, or do you mean add another actual release, like digital?
      • 2020-06-06 15813, 2020

      • evelyn
        the last time Idid that I got a comment saying I should Merge_Rather_Than_Delete
      • 2020-06-06 15821, 2020

      • evelyn
      • 2020-06-06 15857, 2020

      • evelyn
        or maybe I misunderstood...
      • 2020-06-06 15857, 2020

      • levine
        Sounds like a misunderstanding. Of course you can correct misspelled tracklists etc.