#metabrainz

hi. I might wander in after lunch

^ we could do that in MB

Gentlecat: ^

Use that instead. :p

SELECT type, COUNT(*) FROM edit WHERE status = 1 GROUP BY type ORDER BY COUNT(*) DESC;

bitmap ^

Freso: what do you mean?

reosarevok, https://en.wiktionary.org/wiki/jaunty

https://pastee.org/954ue ^ chirlu`'s query

Gentlecat: That link allows you to edit the document directly, doesn't it?

only allows me to suggest

Huh.

Freso: works now, thanks

reosarevok: 90 is $EDIT_RELATIONSHIP_CREATE

314 is Add cover art.

The next are Add release, Add release label.

relevant: https://wiki.musicbrainz.org/User:LordSputnik/B...

:P another issue BB has got sorted

(metrics)

What are 31 and 34?

That'd be all the ones >1000.

With 32 and 53, it'd be all the ones >500.

(And the entire top 10.)

Eh, no. Just the first 10 lines. My bad.

could check if the cover art is already in CAA maybe?

/query Leftmost

...

SELECT extract_path_value(edit.data, 'link_type/id') AS rt, link_type.link_phrase, edit.status, COUNT(*) FROM edit, link_type WHERE edit.type = 90 AND extract_path_value(edit.data, 'link_type/id')::int = link_type.id AND edit.id BETWEEN 33000000 AND 34000000 GROUP BY rt, link_type.link_phrase, edit.status;

bitmap ^ (untested, but compiles)

bitmap, new attempt with a CTE and a smaller sample: WITH foo AS (SELECT extract_path_value(edit.data, 'link_type/id')::int AS rt, edit.status FROM edit WHERE edit.type = 90 AND edit.id BETWEEN 33900000 AND 34000000) SELECT foo.rt, link_type.link_phrase, foo.status, COUNT(*) FROM foo, link_type WHERE foo.rt = link_type.id GROUP BY foo.rt, link_type.link_phrase, foo.status ORDER BY COUNT(*) DESC;

let's see

uhm

I got a ping here but I can't see who/where

So, in summary: 31756 edits were applied, 17 were voted down, 108 got cancelled.

2 failed for technical reasons.

That’s 0.05% of the add-relationship edits voted down, 0.34% cancelled.

0.006% failed.

bitmap, without autoedits and a larger sample: WITH foo AS (SELECT extract_path_value(edit.data, 'link_type/id')::int AS rt, edit.status FROM edit WHERE edit.type = 90 AND edit.autoedit = 1 AND edit.id BETWEEN 33000000 AND 34000000) SELECT foo.rt, link_type.link_phrase, foo.status, COUNT(*) FROM foo, link_type WHERE foo.rt = link_type.id GROUP BY foo.rt, link_type.link_phrase, foo.status ORDER BY link_type.link_phrase, COUNT(*) DE

SC;

bitmap: Oops, autoedit = 0, not = 1.

So, excluding autoedits we have 257 edits voted down and 1314 cancelled vs. 199388 accepted.

i.e. 0.78% of all edits were either voted down or cancelled.

*all add-relationship

LordSputnik: do you actually have a problem with the ticket or was it 100% trolling? :p

legoktm: Ping?

Why not store DB-specific info in a table in individual projects, with editor ID (from MeB) as the key?

Then when the user logs in via MeB, we somehow get the user ID, and the specific site gets the specific info?

LordSputnik: But how are the specific sites notified about removals? The user will never log in again.

does that mean that we actually don't have to use oauth2 internally?

chirlu`: can check the same table

Gentlecat: What table?

user table in MeB database

maybe LordSputnik meant something else

OAuth could be avoided internally if you can access the MeB user table directly in all internal projects

But I think we might as well stick with OAuth

The benefit of storing site-specific data with the sites is that it's potentially less work to implement that than a way of storing and accessing that data on MeB

LordSputnik: we basically do already

Other people are more than welcome to assist in adding to the notes too. Just let me know your Google id thingies.

come on you people, https://twitter.com/hashtag/mbsummit15?src=hash is looking like a ghost town.

http://tickets.musicbrainz.org/browse/CB-191 <3

alastairp: ^ :D

hah, only once we actually have search by recording

what do you think we are? competent?

I don't expect it to be done anytime soon.

also, discussions at the conference regarding messybrainz is making me re-think some stuff

especially around merging ids

Gentlecat has far too many things to do now that he's been employed.

zas: I've fixed http://tickets.musicbrainz.org/browse/PICARD-770 - now need to work out how to integrate it with Picard

Leftmost: relationship/identifier system planning later? Can also work out a rough design for the relationship editor

LordSputnik, sure.

Actually, please help with the summit notes. I'm losing track too often.

me?

Freso: where are they?

LordSputnik: http://chatlogs.metabrainz.org/brainzbot/metabr...

reosarevok: nah I don't have a problem, I deleted the comment ;)

LordSputnik: Credentials?

"If you are here by mistake, click your browser's back button."

That's really profound.

ruaok: http://tickets.musicbrainz.org/browse/OTHER-208 - reply to last comment?

"Alastairp: Gentlecat did work and his work kind of worked and then it was heavily tested and it kind of didn’t work anymore."

sounds accurate

ruchiranga

Oh, hi ruchiranga :)

We're just talking about your GSoC project.

Do you still have a sandbox/test server up?

If anyone has ideas for good, small-ish and/or easy-ish things for newbies to pick up on, please add them to https://wiki.musicbrainz.org/User:Freso/Google_...

Pagination!

Freso: pong

legoktm: we're out at dinner. We had a question about wikimedia SSO

alastairp: what's the question? :)

legoktm: we wanted to know how you dealt with users removing their account

At wikimedia

Now that you have single sign on

We don't allow people to delete their accounts

Some legal reason or something.

We do rename accounts to gibberish if people want to leave

How do you deal with communication between projects for login and preferences storage?

oh, right. I remember something about that