#musicbrainz

/

      • Nyanko-sensei joined the channel
      • Nyanko-sensei joined the channel
      • JesseW joined the channel
      • leollrj_new joined the channel
      • The_Freso joined the channel
      • FresoFenderson joined the channel
      • JoeLlama joined the channel
      • Nyanko-sensei
        FresoFenderson: I meant yindesu
      • JoeLlama joined the channel
      • HibiscusKazeneko joined the channel
      • STalKer-X joined the channel
      • HibiscusKazeneko joined the channel
      • CallerNo6 joined the channel
      • DarkLinkXXXX joined the channel
      • DarkLinkXXXX
        Do you have any workflow suggestions for tagging in bulk? Right now I'm tagging one artist at a time so I more easily correct common mistakes, but this is going to take awhile.
      • derwin
        DarkLinkXXXX: I'm not sure what you're asking
      • it depends on what you're tagging, too.
      • Mr_D34n joined the channel
      • DarkLinkXXXX
        A large collection of music, much of which I have no familiarity with.
      • Lotheric_ joined the channel
      • Freso
        DarkLinkXXXX: You could use beets, I guess.
      • ruaok joined the channel
      • KillDaBOB
        darklinkxxx: one artist at a time is the way to go when first tagging a large collection. like you said, it cuts down on mistakes.
      • once you’ve been through it once, things are a hell of a lot easier and faster in the future.
      • ruaok_ joined the channel
      • ruaok joined the channel
      • jesus2099 joined the channel
      • Nyanko-sensei joined the channel
      • Nyanko-sensei joined the channel
      • _5moufl joined the channel
      • swartwulf joined the channel
      • Freso|koume joined the channel
      • murk_ joined the channel
      • reosarevok joined the channel
      • chungy joined the channel
      • ruaok joined the channel
      • Freso[koume] joined the channel
      • Nyanko-sensei joined the channel
      • robmorrissey joined the channel
      • jesus2099 joined the channel
      • jesus2099
        Lotheric_: did you find the ISRC user scripts ?
      • it’s actually a page by nikki
      • and a user script to allow that page to understand full release copy/paste bunch of ISRC
      • LordSputnik joined the channel
      • LordSputnik
        chirlu`: I undid the edit on the summit page where you added CB to the list of consumer oriented sites - it's quite a different concept to MBo and mbjs and I can't see us talking much about it in that discussion
      • feel free to add it somewhere else if you'd like to talk about it though :)
      • reosarevok
        LordSputnik: I'm not sure it's thought of much differently though
      • Part of the current view seems to be "a place where people can access a MB-lite and review things"
      • LordSputnik
        really?
      • I thought it was just a place for showing releases and storing reviews
      • reosarevok
        Well, basically, having *three* sites sounds confusing as hell
      • Which is I think why some people were thinking of it as such
      • But dunno
      • I have no particular opinion on the matter
      • reosarevok shrugs
      • LordSputnik
        well maybe that could be part of the discussion, I'll add it back in
      • chirlu`: ADDED IT BACK IN, APOLOGIES ;)
      • woah caps
      • luks
        reviews are very user-oriented feature, so it kind of makes sense
      • LordSputnik has left the channel
      • LordSputnik1 joined the channel
      • LordSputnik1 has left the channel
      • kepstin-laptop__ joined the channel
      • Freso|koume
        In case Ben/LordSputnik reads backlog ever, ruaok, Roman, and I did talk briefly about looking into merging the existing MBo code into CB.
      • ruaok_ joined the channel
      • kepstin-laptop ponders the logistics of bringing metalized bags filled with nitrogen gas and food products onto airplanes
      • kepstin_ joined the channel
      • dave_ joined the channel
      • rubin110 joined the channel
      • srotta joined the channel
      • chungy_ joined the channel
      • demosdemon_ joined the channel
      • leonardo joined the channel
      • djpretzel joined the channel
      • Freso joined the channel
      • misterswag joined the channel
      • Jinx joined the channel
      • srotta_ joined the channel
      • rubin110_ joined the channel
      • thescotsman joined the channel
      • Jinx joined the channel
      • blast_hardcheese joined the channel
      • ruaok_ joined the channel
      • ruaok_ joined the channel
      • hawke1 joined the channel
      • CallerNo6 joined the channel
      • JesseW joined the channel
      • robmorrissey joined the channel
      • JoeLlama joined the channel
      • regagain joined the channel
      • hawke2 joined the channel
      • hawke1
        Any chance I could get https://www.wikidata.org/wiki/Q2398350 imported into areas, if it’s not already?
      • Junior_ joined the channel
      • v6lur joined the channel
      • simukis_ joined the channel
      • Bob___ joined the channel
      • rjbell4
        Really simple question: I haven't added to MB in a long time, and even reading the docs, I cannot figure out how to add the ASIN link (for cover art) using the new interface for a release that I just added
      • hawke1
        'edit release' and then paste the URL in links on the first tab of the release editor
      • (And then upload the cover art to the cover art archive instead of using Amazon artwork directly. ;-)
      • KillDaBOB
        or find better artwork than what Amazon has. they frequently have crap artwork.
      • it’s a rare case where Amazon has the best artwork one can find.
      • rjbell4
        Thanks
      • CallerNo6 can't remember what the argument for expanding "vol." is
      • hawke1
        Because it’s inconsistent among releases
      • So you’ll have “vol. 1”, “Volume 2”, “vol. III”
      • drsaunde
        often its inconsistent within the same release also
      • hawke1
        If you expand them so they’re consistent, you could in theory parse the volume number from the title. In practice, nobody would ever bother and our data is fairly inconsistent about that so it’s not particularly helpful.
      • simukis_1 joined the channel
      • CallerNo6 joined the channel
      • CallerNo6 reads the abbreviation style rationale
      • CallerNo6
        "we should make entries as unambiguous as possible for easy manipulation at a later date" supports the machine-readable theory. meh.
      • if we have (ideally) the series number, release language and cover art stored, what's the ambiguity?
      • I do understand why people would want to present series in a consistent way, at least within a particular series.
      • but kudos to abbreviation style for having a rationale!
      • JoeLlama joined the channel
      • hawke1
        :-)
      • I don’t think I agree with that rationale, because in practice no one will ever do that, and any attempt to do so would break as much as it fixed.
      • CallerNo6
        agreed
      • (that might apply to a lot of CSG too)
      • (at least, historically)
      • chungy joined the channel
      • hawke1
        Yep.
      • CallerNo6
        is "feat." also primarily about machine readability?
      • hawke1
        I feel like it’s basically a waste of time trying to get that stuff machine-readable, because unless you’re doing it already no one will notice that it doesn’t work properly or won’t work for the use-case you never actually planned for.
      • But maybe there have been times in the past where it’s been useful?
      • I’m not sure, but I assume so. Perhaps more about picking one and sticking to it since labels are consistently-inconsistent about "feat."
      • CallerNo6
        I guess in general I can see the logic in treating some words as more than strings.
      • leolrrj joined the channel
      • If I'm going to take the position that "artist intent" is a rare thing, then I should also take the position that every guideline that overrides "as on cover" should have a solid rationale.
      • warp
        I think it's more about having some consistency in the data (and thereby some consistency in your music library or whatever else you use MB for), not machine-readability.
      • CallerNo6
        warp, so more about presentation?
      • warp
        CallerNo6: I think many of these guidelines have been around for a loooooooong time. when musicbrainz started you had freedb with their "Something (disc 1)" and "SOMETHING [DISC 2]", and the goal with MB was to avoid that shitshow.
      • CallerNo6
        my dream cotm would be "add rationales to all style guidelines" :-)
      • warp
        CallerNo6: did you ever see the old 1-page style guidelines? they're before my time, but someone (maybe nikki or ruaok) unearthed them when restructuring the guidelines for NGS.
      • CallerNo6
        I think I may have, when oldwiki was still exposed.
      • my other dream is to do a super-fancy-transcluded single page style guide :-)
      • warp
      • nothing about expanding abbreviations yet at that point.
      • thescotsman has left the channel
      • CallerNo6
        look how little and cute they were
      • hawke1
        So narrow. :-)
      • robmorrissey joined the channel
      • CallerNo6
        they grow up so fast
      • kepstin-laptop__ joined the channel
      • hawke1
        I know this has been asked before, but is there a way to copy a discID instead of just moving it?
      • reosarevok
        No, as far as I know
      • hawke1
        Dang.
      • robmorrissey joined the channel
      • robmorrissey joined the channel
      • CallerNo6 joined the channel