#musicbrainz

A separate table of 'Collections, each with a unique collection id. Add two fields to each album referring to that collection and it's position within the collection. If the field is empty, the album is not part of a collection

that requires a schema change though

No. It requires two fields and an addition to the schema. It breaks nothing

Either that or a third table linking albums to collections, which does not modify the albums table

there are people paying for access to the live data feed - if we add stuff, they all have to update too, so it does break things

not only that, the next server release is a non-schema change one, and then after that, work begins on implementing the new schema that's been in the works for aaages

hi aCiD2

what I really mean is, what do you suggest we can do *now*?

Is there a free format text field anywhere that can be used to link stuff?

Munger: yes

1 sec, I'll find you an example of where I've done it

there are annotations, but those can't be automatically converted later on

e.g Set #33444:Vol 2 of 10

I mean a field that is not currenlty used anywhere else

err... why would we have fields we don't use?

Munger: No. But two examples of how else it has been done: 1) http://wiki.musicbrainz.org/Series/MozartComple... and http://musicbrainz.org/release/4d5b539f-6d7e-4e...

Example 2, different way: http://musicbrainz.org/release/3e419764-eb67-41...

I dunno. Sometimes fields fall out of use and don't get pysically dropped

Whooaa there. There *is* a concept of a collection.

where?

in the schema there isn't

On that page there is

"Collection: Add release to collection"

that's something completely different

nothing to do with series

That is a personal collection, *your* personal collection :)

that's your personal collection, e.g. what you own

it's juts a list of mb releases you have

OIC. For a moment I thought we were discussing something that had already been implemented :-)

brianfreud: What does this mean? "Tracks 7 and 9 specify the quarter note at 184."

navap: tempo

fast

oh, doh

Is it possible to have a placeholder release that represents the collection as a whole, whereby the tracks on the release represent volumes within the collection?

no

don't make fake releases :)

It isn't really 'fake'. It is just a conceptual grouping that gives you something to link to. e.g. 'The Blues Collection' is a release with a very clear annotation that it is a collection rather than a specific disc. At least then releases can be linked to it until such a time as the schema can properly accomodate it

That removes the problem of linking collections where all the albums have not yet been entered

It wasn't released as such => it's a fake.

It would be easier, and cleaner to just throw all the links into an annotation.

Or, maintain a wiki page.

What is Rapport?

s/maintain/start Of course, maintaining would be much better :p

A tagging application for the mac? I dunno, most of those emails I just glance through and hit archive in about 3 seconds :p

Ah.

Okay, 'nutther question...

Is there a way to get track-artist-relations in a release WS request?

Right now, it seems I have to get track-artist rels in individual WS calls for the tracks.

Hah. Amazon has not solved it either ---- http://www.amazon.com/Blues-Collection-John-Lee...

navap, http://www.tuneupmedia.com/ A spendid addition to iTunes

Munger: Once you start editing data on mb, you realize it's really not that authoritive when it comes to data. Specially when it comes to imports.

I don't use iTunes, it's about as bad as wmp in my books :(

I'm a proud foobar user :p

pbryan: I don't think so.

If you have an iPod/iPhone, there is really no way around iTunes. It has it's nice points

that would violate our granularity ideas for our web service.

pbryan: That kind of limitation is everywhere in mb. For example, track edits aren't shown under the release itself, only under each individeal track.

ruaok: Time to allow for boxcaring of requests?

NO!

ruaok: Time to allow for bursting requests if I authenticate?

no.

:'(

the granularity of the WS is great the way it is.

make another request.

Granularity is hampered by 10-requests-in-10-seconds rule.

wail.

Hmm?

IOW, "Why don't you cry about it?" ;)

really, if you can't live with the WS rate limiting, set up your own server and blast it to smithereens.

the rate limiting ensures that we have a public resource for everyone.

Okay.

that said, I do want to enable a system to give higher priority to those who have donated.

maybe allow 20 requests in 10 seconds.

so you'd be better off in that case.

but I think I need to ensure NGS gets out the door before I work on that.

ruaok: off-topic, but the next time you're in LA, i insist that you stick around long enough to accompany me here: http://www.wurstkucherestaurant.com/

uhm. ok. :)

yum. sounds good to me. :)

they faux german is pretty sad tho.

their

ruaok: check out the menu, it's fantastic i was there last night, we had siz sausages, beer fries, sides (grilled onions w/ peppers, house-made sauerkraut), house made made ketchup with chipotle, and too many other dipping sauces to mention. house made mustard too

yum.

* six sausages

faux german? i wouldn't know, but the food rocks. our bill for teh evening $66.00, and the owner came by our table and comped us more beer.

quite decent. :)

yeah, this place is fantastic. i *insist* that we go there on your next trip down

ruaok: they serve late night too :)

down? LA is *up* from SD :-p

and you can get, sausages to go, to grill at home

LotR: ruaok lives in SLO most times which is north of LA

heh, serves me right for trying to be a smartass :)

hahahahaha

I made nom indian cooking

CatCat: wonderful!

aCiD2: ping?

pong!

when you setup you git-svn pull of svn's trunk, do you ever make changes to that branch?

including merging any branches to it?

I think so? I do git svn clone, then merge into that branch

I think that is a the core of the problems we're having.

How else can we get changes out?

I've resorted to merging with --squash now

I think if we make master the git-svn pull and only ever make changes to feature branches we should be ok.

then update and dcommit from branches, never from master.

that avoids the rebase problem.

So let's do an example, I have master (from git-svn clone) and feature-X (branched off master)

feature-X is complete, what would we do then?

Are you saying we switch to feature-X and dcommit from that?

from the feature-X branch, do a fetch and a dcommit.

yes

I didn't know you could even do that

if should you need a new feature branch off a more recent master.

master can always be updated from svn if you never make changes to it.

and if I make to branches from the same parent, what about them?

thats tricky too.

you should never work on a branch that has earlier branches off it.

no, but from what i've heard so far, this doesn't really work with more than 1 feature branch at a time, does it?

or, is that why you suggest doing git svn fetch first

why not?

if you need a new feature branch, you fetch/rebase master.

I suppose it works fine if they are completely isolated branches

then branch off it and start hacking.

But how does this help problems with people who don't use svn?

like whom? it allows git users to use svn just fine.

like me and brian

thats where step two comes in.

brian relies on git branches, as he is 100% git - does this not break for him?

I don't think so.

step 2: we need to identify owners of features.

How do I ever update master then, for brian to bring more changes in?

so, say I develop the music news branch.

its critical, to avoid loops in the workflow, that only the feature owner commit changes for a feature.

so, in order to not 'contaminate' your workflow, you only pull from brian into a clean feature branch.

hello, does anybody know the name of singer and song of the following music video clip I am trying to describe: First you see the president of america having a speech. Then he tears apart his rubber mask and a black rapper comes out of this mask. He is doing his rapping until the refrain. The refrain is song by a cute girl and the main text of the refrain is "get to superstar" accompagned by bass tunes. (sorry for the bad english)