#musicbrainz-devel

JesseW: http://tickets.musicbrainz.org/browse/MBS-8004

looking

thanks

I noticed you say in #mb that it should be trivial, so we can look forward you implementing that being the first thing in may's schema change, right? ;)

by May? Hm, quite possibily.

What would the deadline for getting that in by be?

the deadline for the schema change scripts is generally a month before

ok, so by April Fool's Day.

(since we have to finalise what's included so we can tell customers what to expect)

JesseW: However, having it ready earlier is by no means a bad thing.

:-)

the actual ui stuff, well, the earlier the better but I'm sure we've merged stuff the day before the schema change before :P

not that that's ever a good idea XD

btw, do you think that the attribute editing patch is ready? As I mentioned on bitbucket, it seems fine to me.

as far as I know, yes

yay!

I'd love to have more of the descriptions populated (and displayed, but that's separate tickets)

well, populating the descriptions will happen once we have a way to populate them that doesn't involve manually writing sql and getting someone to run it :P

nikki: yes, that's why I'm happy to hear that the attribute editing patch is ready. :-)

as you had previously told me about that precondition

How do I control the display of lines like: [debug] Path is "/collection/edit" when running the tests?

JesseW: turn off CATALYST_DEBUG

ah, makes sense, thanks

There appears to be no tests for adding an Event to a Collection.

I should probably submit some. :-)

Does the WS support doing that?

IIRC no, we deliberately didn't add that so we wouldn't screw it up

didn't add support to the WS, or didn't add the tests? <big grin>

both? :P

heh

ok, well I'll add some tests to t::MusicBrainz::Server::Controller::WS::1::Collection

er, sorry, not there

to t::MusicBrainz::Server::Data::Collection

that's what I meant

obviously didn't add to the tests :P the WS part was the deliberate lack of addition though

and yeah, data::collection tests would be good

nods.

I noticed the lack when I accidentally completely broke adding events, and the tests didn't notice.

hm -- the database also appear to not care that two collections have the same gid...

oh, no I misread it -- they differ in the last digit...

it might be kind to future readers make them differ a *bit* more obviously than that (esp as the difference is d vs b)...

morning :)

does the JSON API have the same syntax and capabilities as the XML?

i'm not seeing the search syntax and what not in the docs

just simple URL samples

am i just adding fmt json?

The query syntax should be the same, yes.

working this morning on knocking out a complete ruby wrapper for the json API

while currently spinning Ray Charles Greatest hits.. such a good sunday record.

just got done with carrol king - tapestry :)

https://github.com/travisdmathis/MusicBrainz-JSON got the guts up.. starting the coding now..

hope to have it done in a couple days.. shouldn't take me to long

there's not that many end points

I don't get why you need an abstraction for the JSON API though. But oh well.

Freso: you'll have to make some kind of abstraction for external services, otherwise it becomes a mess

it's nice to have something ready to use

is there no way to search for an artists releases by format?

axilla: There is.

i only want to return a search for vinyl

i dont see it in the API docs

"format"

since i've struggeled with that exact problem one or two days ago: you need to search for the specific format. e.g. "12" Vinyl" instead of just "vinyl"

mind that you have to escape the " after the 12 for lucene to use is correctly

for example: http://musicbrainz.org/ws/2/release/?query=rele...

yuck

i work with a lot of API's, and not gonna lie, this is one of the hardest most confusing i've ever tried to work with.

BRAINZ.release(:query => "Junta", :format => "Viny 12\" Vinyl")

the first option i get back is a CD

:(

axilla: What search query does that produce?

(Just paste the URL.)

You might also want to make the :format take a list/array: :format => ("Vinyl 12\"", "Vinyl")

(There's no 'Vinyl 12" Vinyl' format.)

using this API makes me want to gouge out my eyes.. whats with the format of release: AND artist: AND ?

why not like every other API.. format=blah&release=blah&

spaces :(

how would you do disjunction or field grouping if all you have is "&"?

there are many ways..

you can pass a query string

something like field1=value&field2=value&field3=value

at work our RESTful API receives JSON so you can pass as much data as you like and then spits out JSON.

axilla: You can try out search queries on https://musicbrainz.org/search - the WS is using "Indexed search with advanced query syntax", so be sure to pick that.

That will probably be easier than sending WS requests while trying to get the hang of the query language.

What's a recommended way to make UUIDs for test data?

uuidgen?