#metabrainz

chirlu`: what is the current use of memcached (on jiji) and redis (on teto, soon on jiji too) ?

i mean what kind of data is stored in those ? we could have dedicated redis instances based on the kind of data to cache, so it will be easier to tune redis config to fit the actual needs.

zas: Redis stores user sessions mostly, and information like when someone last was notified of new edit notes.

Memcached only caches data that is in the main database.

I set up the sandbox to use Redis instead of memcached for that, seems to be working.

Hm, now it says “Not connected to any server”. Will need to find out how to make it automatically reconnect …

OK, fixed (I think). Feel free to test – it should act the same as before.

what was the result of the genre discussion we had? and where is that on the development timeline?

(I’m more interested in the answer to the second question)

at the summit?

a French artist named "Le Dom" ... sort name.. "Dom, Le" ?

darwin: probably

bleh, so many artists with no info online to add to this compilation :/

like.. 22 tracks.. 10 artists to add :/

ruaok: yeah, at the summit. I seem to recall that a consensus was made. I want to see it implemented :)

alastairp: I guess that's in the eternal pile of bitmap stuff

(but not sure how high)

yeah :D

Received a new create event, just so you know.

LordSputnik pushed 1 commits to bookbrainz-data-js: https://github.com/bookbrainz/bookbrainz-data-j...

am I missing where one puts in real name while adding an artist?

I would do it, but the dialogue is mad confusing

darwin: not sure what you mean by "real time"

New pull request "Update codeclimate-test-reporter to version 0.2.1 🚀" by greenkeeperio-bot: https://github.com/bookbrainz/bookbrainz-data-j...

"real name" ? like foobarbaz is named "joe smith"

darwin: ok, in that case you don't add the real name when creating the artist. Instead, after the artist is created, you can add it as an alias (or if they perform using multiple names, you should create a separate artist for the real name and link them together)

isn't it a pretty common thing to want to add the real name of an artist who performs as an alias?

I'd suspect that's the most common case?

my chance of "going back" and doing it is about zero, adding an artist is already the most time consuming thing I d

do while editing

like, I go here : https://soundcloud.com/juksbowl

the only info is : 1) artist nickname 2) full name 3) location

right now, I add 1, 3, but not 2. it seems insane.

darwin: well, the alias system is fairly complicated since it handles far more than just "real names".

so there's no way to add it from the add artist dialogue, in summary? :/

because "adding the real name of an artist while adding them" seems like... well... really basic case :/

well, except that it's more common for artists to be performing using their own names, where the field isn't needed at all.

but feel free to file a feature request for the ability to add aliases in that dialoge

it seems like it could be generally useful.

just... not a very high priority, there's many bigger issues being worked on.

in that order?

we can add 1-3 on the form, and not 4

can we add everything in freesound to musicbrainz yet?

soundbrainz

ok, well, there goes another artist whose real name I know, added without their real name

darwin: i don't disagree that the ability to add aliases when creating an artist would be useful. Unfortunately, it's not super high priority (there's other ways to do it), and developer time is very limited

kinda boggled how this isn't something everyone-who-ever-adds-an-artist is missing, but /shrug

it's not even immediately apparent to me what extra dialogues I'd go through to add it, if I was ok with the extra clicks, which I'm mostly not?

It might make sense as a google code-in task for volunteers, but it could be a bit too complicated for that :/

darwin: this is a mostly-volunteer project. If you want something fixed really badly, you have to put some effort into trying to help out, rather than just saying you're entitled to having a particular feature.

up there with track remixer for info I have and just drop on the ground

hrm, on the one hand I greatly appreciate the refresher in how volunteer projects work.. on the other hand I am already volunteering my effort by caring enough to add artists in the first place, so while a great answer, /shrug

track remixer should be added using the release relationship editor after adding the release; more artist information should be added by navigating to the artist page and using the tabs available on there.

and we appreciate all the data you can add, for sure

(I mean, people in here who have paid someone to contribute data to mb, raise your hand.. *raises hand* etc..)

(the form of my commentary really is "it's weird how fundamental this seems to me and apparently wasn't to the creator of the original UI", not a demand..)

hey, we didn't even have the pop-up "add artist" dialogue a year ago

you used to have to open a new tab and do it separately

the ui has been steadily improving

yeah, it used to be the #1 thing preventing me from adding releases to musicbrainz, heh, certainly much better to have it inline.

I think the biggest work-in-progress editing UI improvement planned is integrating the release relationship editor into the main release editor, which would solve your complaint about having to work harder to add track relationships like remixer.

ah, is there a ticket where I can see the progress there? that one is hyoooge for me, I could right an add-remix-relationships bot with that functionality in the editor seeding

*write

but right now devs are very much focused on making the search not break, there's some major issues where the site is regularly taken completely down due to search failure :)

(well, not completely, but it does break most editing features)

yeah.. I haven't actually personally encountered it but I've been hearing about it

like I said, my commentary is a more general one of surprise that the feature was originally created without what to me seems a fundamental thing, not a real harsh critique of the overal priorities of participants, heh!

yeah, it's just that the aliases weren't on the standalone 'add artist' page at https://musicbrainz.org/artist/create either, and the pop-up is basically just a copy of the standalone page.

reworking the backend scripts to allow doing aliases there would have been a lot more work

ah, *that* makes sense. I would assume it was on the actual "add artist" page. But I guess I didn't check, and unfortunately it's not there either :/

(in particular, tech details: the current "add artist" page creates a single edit; if it had aliases, it would have to submit a batch of multiple edits to a new server endpoint)

right, and the problem with the remix thing is it has to create an entity and then a relationship on it, iirc

which is not something the current tracklist editor supports, or something?

yes, except that the release editor already is able to handle multiple edits

but on the tracklist tab?

so it's just a matter of integrating the UI code there, mostly.

or is it ultimately one submit or etc.

it would probably be a new tab after recordings, named "relationships" or so

alias being on artist adds is already requested, and we want that

that would contain a copy of the editor seen at e.g. http://musicbrainz.org/release/1479da76-156b-4d...

so actually that makes a lot more sense now and I feel less confused, if add artist is a single submit everywhere on the site, and never enables you to submit real name because real name is an alias, that actually makes sense why : it's not trivial.

Add artist doesn't create only one edit anyway, not as long as you add any URLs or rels from there

But it still would need code to submit aliases from there, yes :) So, it's doable, but not fully trivial and nobody has worked on it yet

oh, forgot about that

The urls & rels feature still seems new to me :)

reosarevok: you happen to know the ticket number for that?

I miss having nikki magically show up with ticket links :(

hrm, what is this locale for an alias?

locale is the language/country where the alias is used; it's useful for artists that have name transliterations or translations or alternate names used in different languages or countries

I'm searching, in the meantime, ideas for http://tickets.musicbrainz.org/browse/MBS-8292 ? :p

Oh, there we go. kepstin http://tickets.musicbrainz.org/browse/MBS-3108

reosarevok: I still think we should drop artist names completely and only have aliases (and drop artist credit names in favour of aliases too)

That's http://tickets.musicbrainz.org/browse/MBS-7830! :p

it's even a linked ticket, lol

and then rename the alias entity "name" ?

yeah; in the simple case you'd get a single open alias field to fill in with the artist's primary name, but have the ability to add more aliases for other locales, real names, etc.

in that grand far-off future :)

ruaok: ?

alastairp: I think he thought about genres and ran away

Yeah, we were supposed to meet but I went to the wrong bar...

alastairp: en serio? wrong bar?

we were at Ale & Hop just last week. :)

LordSputnik: The event you linked as an error also has a restriction. Events with restrictions are not accessible via the public Facebook Graph API. Freso had a similar issue for an event he had trouble with. Maybe I should add a snippet that returns an error if the API returns the "error" for restricted events.

Source: http://stackoverflow.com/a/23078364

ruaok: sorry! I thought "bar with Rob, must be black lab"

ooops

And it wasn't until we had ordered a round that I thought perhaps theyre not here