#metabrainz

/

      • ruaok
        CJ_: and weeksio on the new VM, I would assume.
      • 2016-01-06 00602, 2016

      • Mineo
        CJ_: no, there's a pretty large pull request by weeksio
      • 2016-01-06 00619, 2016

      • CJ_
        ruaok, Yes, I have spoken with weeksio but I was trying to understand the original configuration.
      • 2016-01-06 00634, 2016

      • ruaok
        original config was by Mineo, yes.
      • 2016-01-06 00648, 2016

      • reosarevok
        Gentlecat: messaging between editors is just one part of MBS-1801, no?
      • 2016-01-06 00652, 2016

      • CJ_
        Mineo, I believe that was mainly changes suggested by the IDE.
      • 2016-01-06 00622, 2016

      • Mineo
        CJ_: well, the original configuration was only there to get the data into solr in some form, it was not intended to do any fancy analysis
      • 2016-01-06 00623, 2016

      • reosarevok
        Right now we have that as "email this editor", but it should be possible in-site, same as other currently email-based communication
      • 2016-01-06 00628, 2016

      • Mineo
      • 2016-01-06 00631, 2016

      • CJ_
        Mineo, Do you have anything written about why you configured things as they are? I am trying to make sure I understand things before I change them. :)
      • 2016-01-06 00624, 2016

      • CJ_
        Mineo, Ah. That is not the commit I had seen previously. :)
      • 2016-01-06 00631, 2016

      • Freso
        I think it'd make sense to split out "site-based inter-user messaging" to be a subtask of MBS-1801. MBS-1801 is gargantuan enough as it is.
      • 2016-01-06 00655, 2016

      • Gentlecat
        I'm asking because it's not really all that simple
      • 2016-01-06 00633, 2016

      • ruaok
        what makes it hard?
      • 2016-01-06 00639, 2016

      • reosarevok
        I mean, isn't it the same as the others? Instead of (or additionally to) sending an email, we send the message to their inbox, same as we would with edit notes
      • 2016-01-06 00605, 2016

      • Gentlecat
        storing messages on the server, for example
      • 2016-01-06 00626, 2016

      • Gentlecat
        there's https://xmpp.org/extensions/xep-0136.html, but as far as I can see it's no implemented in servers that I looked at
      • 2016-01-06 00648, 2016

      • Gentlecat
        that means we have to implement something on top of this ourselves
      • 2016-01-06 00620, 2016

      • Gentlecat
        what makes things complicated is that we planned to be able to connect using desktop clients or whatever
      • 2016-01-06 00621, 2016

      • ruaok
        if desktop clients complicate this unnecessarily, we can drop this requirement. it is a nice to have.
      • 2016-01-06 00625, 2016

      • Gentlecat
        though it's not the only problem
      • 2016-01-06 00626, 2016

      • reosarevok would say the main point here is having something that works on the site, and that desktop clients and the like are very secondary and we can happily drop them
      • 2016-01-06 00650, 2016

      • ruaok
        as far as checking implementation details, please mail arc and ask him if he knows what could help us.
      • 2016-01-06 00652, 2016

      • reosarevok
        If people want something that reaches them outside of the MB site... well they have that right now with email, so it's not a huge issue IMO
      • 2016-01-06 00601, 2016

      • ruaok
        reosarevok: +1
      • 2016-01-06 00607, 2016

      • Gentlecat
        even then, if people connect to XMPP server only through the website, we still need a reliable way to archive all the messages
      • 2016-01-06 00625, 2016

      • ruaok
        arc suggested that this was a solved problem.
      • 2016-01-06 00644, 2016

      • Gentlecat
        ruaok: I've been talking to him a bit before about authentication
      • 2016-01-06 00658, 2016

      • Gentlecat
        I think we only just getting closer to figuring this out
      • 2016-01-06 00613, 2016

      • ruaok
        one step at a time. :)
      • 2016-01-06 00655, 2016

      • Gentlecat
        he suggested to use one of the new authentication mechanisms, which uses OAuth
      • 2016-01-06 00658, 2016

      • Gentlecat
      • 2016-01-06 00629, 2016

      • Gentlecat
        the problem is that none of the servers implemented it yet
      • 2016-01-06 00613, 2016

      • Mineo
        that seems to be an accurate description of most things xmpp :)
      • 2016-01-06 00639, 2016

      • Gentlecat
        though I'm still thinking that it might be better to just implement something simple for ourselves
      • 2016-01-06 00648, 2016

      • Gentlecat
        especially for notifications
      • 2016-01-06 00645, 2016

      • Gentlecat
        I'll keep digging more, will try to expand this googledoc
      • 2016-01-06 00613, 2016

      • Gentlecat
        and it would be nice to have a ticket for the actual messaging part to know what people expect
      • 2016-01-06 00609, 2016

      • Gentlecat
        we can implement a private chat for editors, but is that really going to be all that useful? considering that we prefer to communicate in the open
      • 2016-01-06 00634, 2016

      • reosarevok
        I think it's fine for it to be normal email-style messaging rather than live chat
      • 2016-01-06 00649, 2016

      • reosarevok
        I'd much rather have open live chat for entities if anything
      • 2016-01-06 00656, 2016

      • Gentlecat
        like reddit, for example?
      • 2016-01-06 00602, 2016

      • reosarevok
        But maybe just making IRC more visible would work for that
      • 2016-01-06 00611, 2016

      • reosarevok
        (webirc anyway)
      • 2016-01-06 00650, 2016

      • reosarevok goes check his reddit messages
      • 2016-01-06 00658, 2016

      • Gentlecat
        because I still don't understand what will people need to discuss privately on musicbrainz
      • 2016-01-06 00658, 2016

      • ruaok
        Gentlecat: feel free to break the ticket out into smaller tickets as appropriate.
      • 2016-01-06 00619, 2016

      • reosarevok
        Yeah, something like that
      • 2016-01-06 00639, 2016

      • ruaok
        then, once they are broken up a bit more, let's write up a blog post with the most salient questions from the tickets.
      • 2016-01-06 00642, 2016

      • Gentlecat
        ruaok: ok, I'll create another one
      • 2016-01-06 00651, 2016

      • ruaok
        that way people can give us feedback on what they think is important.
      • 2016-01-06 00608, 2016

      • ruaok
        and it will also show that you're making progress on a very important topic.
      • 2016-01-06 00610, 2016

      • Gentlecat
        don't think it's related to notifications, really
      • 2016-01-06 00623, 2016

      • reosarevok
        Gentlecat: in my history of messaging, the only really private-ish stuff has mostly involved autoeditor nominations
      • 2016-01-06 00600, 2016

      • Gentlecat
        reosarevok: right, that seems very specific
      • 2016-01-06 00609, 2016

      • ruaok
        are editor to editor and public vs private two separate topics?
      • 2016-01-06 00614, 2016

      • ruaok
        seems like it to me
      • 2016-01-06 00620, 2016

      • Gentlecat
        majority of it would probably related to the actual editing
      • 2016-01-06 00623, 2016

      • reosarevok
        But I think it's perfectly fine for users to use MB to talk about meeting in person or something without that necessarily involving a public post
      • 2016-01-06 00639, 2016

      • reosarevok
        (and it's a functionality we already provide with emails)
      • 2016-01-06 00658, 2016

      • reosarevok
        I don't think we need to make it do anything more fancy than what the mails do though
      • 2016-01-06 00631, 2016

      • Gentlecat
        yeah, and that's kind of getting into another question of whether we want to actually host and maintain all this additional infrastructure
      • 2016-01-06 00642, 2016

      • Gentlecat goes to create tickets
      • 2016-01-06 00621, 2016

      • ruaok
        Gentlecat: I think the hosting question has already been answered.
      • 2016-01-06 00634, 2016

      • Gentlecat
        I'll also cleanup the googledoc and post it again to update on where we are right now
      • 2016-01-06 00636, 2016

      • ruaok
        that was the layer vs XMPP debate.
      • 2016-01-06 00644, 2016

      • ruaok
        sounds good.
      • 2016-01-06 00639, 2016

      • Lotheric joined the channel
      • 2016-01-06 00612, 2016

      • gcilou has quit
      • 2016-01-06 00630, 2016

      • adhawkins has quit
      • 2016-01-06 00606, 2016

      • adhawkins joined the channel
      • 2016-01-06 00651, 2016

      • zag
        whoop! kodi just got all the extra tag support for musicbrainz
      • 2016-01-06 00652, 2016

      • zag
      • 2016-01-06 00619, 2016

      • Freso
        zag: Neat! :D
      • 2016-01-06 00652, 2016

      • zag
        need to enable "folksonomy" in tags, but looks good so far
      • 2016-01-06 00631, 2016

      • Freso
        Why though?
      • 2016-01-06 00648, 2016

      • zag
        I don't think picard writes those tags without it
      • 2016-01-06 00653, 2016

      • Freso
        Composer, conductor, lyricist, etc. are not dependent on "folksonomy".
      • 2016-01-06 00606, 2016

      • zag
        ahh my area of interest is the dj mixer stuff
      • 2016-01-06 00618, 2016

      • Freso
        Folksonomy tags are stuff like "hip hop, fix me, folk, seen live"
      • 2016-01-06 00618, 2016

      • zag
        thats good news though
      • 2016-01-06 00646, 2016

      • Freso
        (I would not be surprised if someone entity had those exact five tags.)
      • 2016-01-06 00651, 2016

      • Freso
        *some
      • 2016-01-06 00657, 2016

      • zag
        hmm ok, the option is very confusing for a new user. even the name is confusing ;)
      • 2016-01-06 00617, 2016

      • Freso
        I don't even see the option you're referring to. :/
      • 2016-01-06 00625, 2016

      • Freso
        Maybe it's been changed since last release?
      • 2016-01-06 00633, 2016

      • Freso
        (I run off the Git code.)
      • 2016-01-06 00645, 2016

      • Freso
        I only see folksonomy under Metadata, not in the Tabs tab.
      • 2016-01-06 00607, 2016

      • Freso
        And there it's "Use folksonomy tags as genre"
      • 2016-01-06 00654, 2016

      • zag
        yeh thats what confused me originally, since we have a lot of n00b users who are going to be expososed to this i need to be able to explain it simply
      • 2016-01-06 00600, 2016

      • Freso
        You will need to enable "Use track/recording relationships" (or whatever the English title is), as that's where a lot of those relationships will be at.
      • 2016-01-06 00615, 2016

      • Freso
        (Under Metadata.)
      • 2016-01-06 00619, 2016

      • zag
        yep got it, thanks
      • 2016-01-06 00653, 2016

      • Freso
        And enable "Use release relationships" for those cases where those info are on the release level. :=)
      • 2016-01-06 00656, 2016

      • Freso
        * :)
      • 2016-01-06 00601, 2016

      • zag
        Will write a guide later, here's the current Kodi/picard guide
      • 2016-01-06 00601, 2016

      • zag
      • 2016-01-06 00619, 2016

      • zag
        silly we have to recomend using a plugin to remove feat. though
      • 2016-01-06 00657, 2016

      • Freso
        zag: I agree. You should just leave it in place.
      • 2016-01-06 00614, 2016

      • zag
        Well our music video scraper fails on any file that features an artist, as it uses title match
      • 2016-01-06 00644, 2016

      • Freso
        Ah, "feat." shouldn't be in title at all.
      • 2016-01-06 00657, 2016

      • Freso
        "feat." should be part of the artist string.
      • 2016-01-06 00625, 2016

      • zag
        Ahh ok, yeh we deal with that using Artists processing
      • 2016-01-06 00649, 2016

      • zag
        its a nightmare as we have to deal with other taggers as well
      • 2016-01-06 00638, 2016

      • Freso
        Only because you don't deal with entities proper to begin with. :) If you said artist=MBID-fallback-ArtistName instead of artist="Artist Name"...
      • 2016-01-06 00605, 2016

      • Freso
        That would also suddenly make handling "One thing to say is that with the remove "feat." plugin it doesn't remove the multiple MBID's from the artist field." very easy.
      • 2016-01-06 00641, 2016

      • Freso
        And would allow all the artists to show up proper, regardless of artist name variations and feat./collab. constellations.
      • 2016-01-06 00607, 2016

      • Freso
        Esp. coupled with the new metadata you're ingesting (if you looked up that MBIDs for those metadata too), you'd be able to look at Dr. Dre in Kodi and see everything he's performed on, groups he's a member of, what he's composed, written lyrics for, mixed, produced, ...
      • 2016-01-06 00635, 2016

      • zag
        yep exactly
      • 2016-01-06 00648, 2016

      • Freso
        (Dr. Dre isn't the best example as that name is relatively unique and he doesn't really do a lot of name variation, but I know of some Danish rapper/producers that juggle multiple aliases that Kodi can't handle properly right now because Kodi handles names rather than MBIDs.)
      • 2016-01-06 00648, 2016

      • Freso
        Anyway, having Kodi use more data from the tags that Picard save is definitely a step in the right direction. So thank you for that, if you had any hand in it. :p
      • 2016-01-06 00602, 2016

      • zag
        Real coolness starts when we can scrape the musician credits (TMCL) and find the drummer of multiple bands
      • 2016-01-06 00618, 2016

      • Freso
        Yes. :)
      • 2016-01-06 00627, 2016

      • zag
        I'm just the tester ;) but prepare for 10 million users coming your way on picard forums hehe
      • 2016-01-06 00641, 2016

      • Freso
        Also, is mastering information saved under the ENGINEER tag?
      • 2016-01-06 00626, 2016

      • zag
        need to check, our coder was interested in classical music mainly
      • 2016-01-06 00648, 2016

      • Freso
        Classical music also gets mastered. :)
      • 2016-01-06 00613, 2016

      • Freso
        reosarevok: ping, read backlog :)
      • 2016-01-06 00632, 2016

      • Freso
        (In case there are other obvious tags that they've left out.)
      • 2016-01-06 00645, 2016

      • Freso
        Stuff like key and tempo might also be interesting for Kodi to parse.
      • 2016-01-06 00626, 2016

      • Freso
        Picard doesn't tag those though (maybe the AcousticBrainz plugin fetches that info though? Has the AB plugin been released yet?), but you might get those from other sources.
      • 2016-01-06 00603, 2016

      • Freso
        E.g., beets has a couple plugins that allows you to gather this information, incl. a fresh-out-of-the-oven AcousticBrainz plugin.
      • 2016-01-06 00648, 2016

      • Freso
        (Could be cool to see all "D mixolydian" tracks in ones collection. :p)
      • 2016-01-06 00648, 2016

      • zag
        one step at a time ;)
      • 2016-01-06 00629, 2016

      • gcilou joined the channel
      • 2016-01-06 00641, 2016

      • gcilou has quit
      • 2016-01-06 00629, 2016

      • UmkaDK joined the channel
      • 2016-01-06 00625, 2016

      • zas
        About Kodi & MB/Picard, be sure to use MBIDs as much as possible, relying on names is inherently broken anyway. Nice to see more work is done in this field :)
      • 2016-01-06 00612, 2016

      • reosarevok
        Freso, zag: will check in a few hours, busy ATM :)
      • 2016-01-06 00628, 2016

      • Gentlecat
      • 2016-01-06 00638, 2016

      • chirlu` wonders why reosarevok’s https://musicbrainz.org/edit/36717049 did not delete the URL.
      • 2016-01-06 00603, 2016

      • chirlu`
        I had to do https://musicbrainz.org/edit/36721755 to trigger deletion.
      • 2016-01-06 00602, 2016

      • gcilou joined the channel
      • 2016-01-06 00637, 2016

      • Gentlecat
        alastairp: maybe we should move this into a ticket and merge the changes https://github.com/metabrainz/acousticbrainz-serv…
      • 2016-01-06 00659, 2016

      • Gentlecat
        at least new stats will be generated correctly
      • 2016-01-06 00624, 2016

      • Gentlecat
        I don't know if you plan working on it, but that's definitely not on my radar
      • 2016-01-06 00604, 2016

      • Leo_Verto has quit
      • 2016-01-06 00614, 2016

      • regagain has quit
      • 2016-01-06 00622, 2016

      • yeeeargh has quit
      • 2016-01-06 00654, 2016

      • regagain joined the channel
      • 2016-01-06 00635, 2016

      • CallerNo6 has quit
      • 2016-01-06 00601, 2016

      • CallerNo6 joined the channel
      • 2016-01-06 00620, 2016

      • stanislas
        LordSputnik: What is a country id ?
      • 2016-01-06 00659, 2016

      • stanislas
        LordSputnik: Country seems not to be defined as some sort of a class.
      • 2016-01-06 00653, 2016

      • Leftmost
        Country hasn't been defined in the current schema, no.
      • 2016-01-06 00621, 2016

      • JonnyJD joined the channel
      • 2016-01-06 00640, 2016

      • alastairp
        I think I've asked this before: http://musicbrainz.org/release/a4b867d5-ae96-33b6… there's no way of getting recording artists without doing a query for each recording, right?
      • 2016-01-06 00624, 2016

      • alastairp
        Gentlecat: it's on my list
      • 2016-01-06 00632, 2016

      • UmkaDK has quit
      • 2016-01-06 00634, 2016

      • reosarevok
        chirlu`: not an issue I knew about at least. Ticket I guess :)