#musicbrainz

Anyone hear about the upcoming Joss Whedon series?

chefkoch_ is now known as chefkoch

I use irssi and Pidgin.

pbryan: irssi.

which part?

> This would mean N:M mapping between releases and IDs.

which ids does "IDs" refer to?

current Album IDs

so, why does the relationship between the release and the release events needs to change?

I'm trying to understand why this is:

Release ID, because the same ID is also used for other releases:

(second line is quoted too)

well, that depends on your definition of release

for me, if it's a different product, it's a different release

because it has a different barcode.

there are rare cases when a single release has multiple labels/catalog numbers

which is why there is the release_label table in my schema

but for most releases it's single barcode, single label, single catalog number

so a release is what we currently have in table "release"

and the table "album" is really a mix of everything

the album table is clearly conflated. :)

are you talking about the one on http://wiki.musicbrainz.org/LukasLalinsky/Relea... ?

ya

yes

ok

I see the instance described by a release event as a "product".

a release is really a... super class.

a release can have multiple countries, can't it?

(as well, I mean, not in that schemathingy)

not complete without a deriving class.

nikki: yes, but that get's too confusing

I had a release_event table there, too

with date/country pairs

but I removed it

I still don't understand. I should probably think about it in the morning...

I don't know if it helps, but here is the example from the mail in the ngs-playground server

release group - http://89.103.90.126:5000/release-group/c1adac5...

release - http://89.103.90.126:5000/release/7bc8207b-a276...

and you can see two medium objects on the release page

which maps exactly the schema from the mail

and the data are from http://musicbrainz.org/release/c1adac5d-a176-49... and http://musicbrainz.org/release/6816265d-f0ea-4c...

'release' is a real-world release

oh. yeah

the current mb release is something else

is 'album' the release group though?

yes

yay I understood it

I still don't like that discs can't have catalogue numbers :/

I think I'm starting to understand. I think our concepts of release groups are a bit different.

chefkoch_ is now known as chefkoch

the model is almost identical to what SoundUnwound has

except they have the release group objects hidden

heh. they also bitched about us not having release groups. :)

ok, I'm grokking your schema again.

they basically pick one release and use it instead of the release group object

in the UI layer, that is

I don't think it's stored in their DB that way

now I'm trying to trace how ids change from one schema to the other.

so, in your plan, most single cd releases would be converted to a release-group.

if you had album ID X, accessible on album/X, it will be accessible on release-group/X

and 70% - 90% would remind unchanged?

single disc MB releases with no other versions will be completely unchanged

ok.

multi disc releases or different versios will be merged

but of course, the IDs are still valid

old ids will always resolve to the release group?

yes

ok, thats not too bad.

I'm trying to put myself into the shoes of our customers.

the only other option I see is to make them "Medium IDs"

and I'm trying to think how much effort it will be to migrate.

I think that is what I was thinking about.

so instead of pointing the ID of "The Wall (disc 1)" to The Wall, they would point to the first CD of The Wall

is your server up all the time?

I'd like to stick the beeb/cloudspeakers on this and take a closer look.

nope, it's my desktop machine

ah. are there some predictable hours?

(when it might be up?)

always except for nights here

it's in my bedroom and it's quite noisy :)

suppose they'll be up at the same sort of times then

that should work well enough.

heh. I should tell the soundunwound guys. they'd probably be pleased with this solution

ok, I think I'm caught up now.

I was clearly confused with the ID migration bit.

and with this system, if all the old ids resolve, migration to the new system should be pretty easy actually.

luks: so you wanna tackle release groups and tt at the same time?

ruaok: I'm still not sure, but after trying to do something on the TT branch, it seemed like a waste of time to work in something we know it's suboptimal and it's going to be replaced soon

yeah, I can see that.

I'll ponder it some more.

chefkoch_ is now known as chefkoch

yvesr_ is now known as yvesr

hmm...

if a release doesn't actually have a barcode printed on it anywhere, but I can find one for it, should I enter it or not?

sumpin is better than nothin

unless sumpin is a kick in the ass

heh

Or AIDS

Or Faux.

it's just that there's no way I could possibly prove that the barcode is right, because I know the release never had one printed on it

Sure your release isn't missing extra packaging?

yes

I've seen barcodes applied to cheap ass plastic warp

wrap. sorry, warp.

it was brand-new and sealed when I got it and all the others I've seen on yahoo auctions are the same

navap_ is now known as navap

chefkoch_ is now known as chefkoch

jason_emmett has joined #MusicBrainz

He's dreaming of yoooooou

chefkoch_ is now known as chefkoch

That's a scaring thought!

chefkoch_ is now known as chefkoch

I'm about to go to the bathroom. I'll think of jason_emmett once I'm there.

Be careful.

futilius_ is now known as futilius

Bah. I was going for a "It's dangerous to go alone" above, but couldn't think of an object. Me, dammit. ME.

snigger at your/you're fail

bar!

Bazil!