#musicbrainz

that's nice

I also saw that some bots started converting from ' to ’

oh?

that's hard to do correctly, I wouldn't think anyone would run a bot for that...

I know there are some people doing it

like here: http://musicbrainz.org/artist/9e57e406-4fb1-40d...

i.e. others like (http://musicbrainz.org/artist/3826a6e0-9ea5-400...) might be (auto-)converted soon?

coopsh: there is no autoconversion being done.

heh, bogdan isn't a bot

http://musicbrainz.org/edit/13841221 says 'auto-edit'

man, you know what would have helped my find that faster? an edit search ;)

that's why I'm confused

that just means the edit was automatically applied instead of being voted on

ah, ok

it also means that we'll have a mixup the next couple of years?

a mixup?

coopsh: we'll probably have mixed punctuation styles forever.

yay, my artist credit parsing and displaying should now work on all possible artist credits, and display them in the same way as the musicbrainz site itself.

does musicbrainz warn if one edits/adds data and uses a 0x27 apostrophe (')?

no

coopsh: nope

wouldn't that be a good idea? ;)

potentially once the devs don't have lots of real bugs to fix :P

I don't see the point of a warning if we don't require it, it'll just annoy people who don't have the patience to enter them

if you convert u+2019 to u+0027 it'd make sense, but I imagine it'd piss people off if it did it anytime you edit something with u+0027

what if people _add_ something w/ u+0027?

right now we let people use u+0027 but people who care about those characters are allowed to change them

that's what I figured you meant

We could have an userscript that screams at you when it finds one

For the people who do care

potentially if we provide a nice way of entering the unicode ones then we can be more strict about not entering u0027

Is there an easy way to create new works for every recording in a release? Just like the composer relationship could be applied to all tracks of a release under Mason? And just like we can apply a performance relationship to all recordings in a release now? I can't see how to do this for a 20 track release in less than 60 time-consuming edits right now...

maybe a 'auto-convert-to-u+2019' button ;)

zexpe: it is in development

apparently only opera supports that tag now though :P

How surprising

Something that *works* in Opera… and it's an annoyance

hehe

you can still enable it in firefox, if you use about:config

hmm. apparently I need to make a separate version of my artist credit rendering template that's usable in places where plain text is required; It's not nice if page titles contain <a> elements :)

reosarevok: as in soon? is there an MBS # for this? and are there any tricks such that it can be currently done in less than 3 edits per track?

As in soon (it's in test.mb.org now

Cool, thanks

And for tricks… not really

Best to wait then...

I mean, there is a script for creating a work and relating it to the recording in one click from the recording page

But it still requires adding the relationship to each work, one by one

So I'd just wait

And this development will cut the number edits down to 1?

Enjoy you all

will do

is there a fast way to fix all apostrphoes for this release-group: http://musicbrainz.org/release-group/88c59b55-2... ?

coopsh: nope.

zexpe: replying to myself: the new "relate to works" option in test.musicbrainz.org does indeed cut 60 manual edits down to 1 that creates 20 auto-edits for new works and 40 new relationships to be approved. Can't wait to see this roll out live...

the userscript I promised: http://paste.pocoo.org/show/414427/ :P

lol

you should make that apply to the entire internet.

:)

haha

hmm. I guess I should do the release group parser next.

this app's usefulness will be legendary: it does a webservice query on musicbrainz.org, then renders a page that's as close as possible to what the original musicbrainz page looked like ;)

and here I thought I was trying to make an ISRC submission helper.

hello everyone

i have a question about musicbrainz database

is there anyone?

just ask ;)

be careful using ascii apostrophes though

:D

i created a database and created tables with createtable.sql, and imported musicbrainz database

but there are some errors and some tables are empty

ERROR: new row for relation "url" violates check constraint "url_edits_pending_check" CONTEXT: COPY url, line 180147: "909043 33f5699f-ac58-4136-a51a-18c90c6b709f http://en.wikipedia.org/wiki/The_End_of_Days \N 0 -1 201..."

and relation table is empty

here is the line's content: 20318842f8dabd-bf2b-486d-aa57-4ebea9e011fe3474391777585585971\N222120282000919\N\N0-1\N

oh, sorry

1 minute

90904333f5699f-ac58-4136-a51a-18c90c6b709fhttp:... 10:15:57.205857+00

all errors are like this: ERROR: new row for relation "xxx" violates check constraint "xxx_edits_pending_check"

i asked my first question for not being in this situation :)

there is no one who answered my question. :/

is there a way to add a track with tracknumber 0?

buremba: well, it *is* saturday... maybe someone who knows something about that stuff notices it in an hour or few and answers; if not, ask again sometime :)

coopsh: why?

(pregap track?)

yes, a hidden track

coopsh: i didn't change anything in db

coopsh: we don't currently have support for pregap tracks. What you can do right now is add it as a standalone recording, and add a link to that recording in the release's annotation.

kepstin: you mean the database has errors, so you must change these lines, right?

buremba: I don't know anything about your issue, I'm talking about something unrelated.

kepstin: ok, now should I fix errors by myself or wait someone who know db?

because i want to keep original :/