Issue Details (XML | Word | Printable)

Key: MBS-379
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Normal Normal
Assignee: Lukáลก Lalinský
Reporter: voiceinsideyou
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
MusicBrainz Server

Release search shows incorrect # tracks.

Created: 27/Jan/10 06:10 AM   Updated: 23/May/11 07:40 PM   Resolved: 23/May/11 07:40 PM
Component/s: Search
Affects Version/s: NGS - Beta 1
Fix Version/s: Hot fixes, 2011-05-23


 Description  « Hide

I'm not sure if this is to do with Search or the Server (correct me please), but the Search server on NGS Beta 1 shows incorrect # tracks for multi disc releases. e.g.

http://test.musicbrainz.org/search?query=Luminous+Groove&type=release

The top release should really show 91 tracks, but it seems to have picked the figure from disc 3 (20 tracks).

It also highlights that release search should probably also have a column for # of discs. Perhaps a joint column with both figures (for saving screen real estate) would be a good idea. Of course there's the wider issue that results like http://test.musicbrainz.org/search?query=downward+spiral&type=release are not very useful now without any disambiguation by cat#, date etc, but that's probably a bigger issue best dealt with elsewhere.



Sort Order: Ascending order - Click to sort in descending order
Paul Taylor added a comment - 27/Jan/10 10:03 AM

Assuming this release does contains two mediums (I'm sure it does but on my older db it doesn't and test is broken at the moment) this is a bug on the Server because the correct data is being returned from search, need to use track-count field in medium-list. I think the release frontend was written before we had added this new track-count field into the MMD.

i.e
http://localhost:8080/?type=release&query=reid:9cbf7040-dbdc-403c-940f-7562d9712514&fmt=json

returns:
{"release-list":{"offset":0,"count":1,"release":[{"score":"100","id":"9cbf7040-dbdc-403c-940f-7562d9712514","title":"To Venus and Back","status":"official","text-representation":{"language":"eng","script":"latn"},"artist-credit":{"name-credit":[{"artist":{"id":"c0b2500e-0cef-4130-869d-732b23ed9df5","name":"Tori Amos","sort-name":"Amos, Tori"}}]},"release-group":{"type":"album"},"date":"1999-09-20","country":"de","medium-list":{"count":2,"track-count":24,"medium":[{"disc-list":{"count":2},"track-list":{"count":11}},{"disc-list":{"count":4},"track-list":{"count":13}}]}}]}}

I agree there should be a #discs column


Paul Taylor added a comment - 27/Jan/10 10:03 AM

see above comment


voiceinsideyou added a comment - 27/Jan/10 12:01 PM

Thanks Paul. Did you have any thoughts about the disambiguation issue now that every Release /Event/ is now a Release? I note that the type, date and country is included in the JSON, but not displayed currently, even though it is on pre-NGS MB Server. It'd possibly also be best to display the consolidated format, e.g. 5xCD or whatever, like on the release page, if possible - that however doesn't seem to be in the JSON output with the medium-list :/


Paul Taylor added a comment - 27/Jan/10 01:38 PM

Chad, I agree that these columns should be there, but this should probably be raised as a separate issue.

The JSON does return the number of mediums and the format (Ive checked my code and it just happens in my example the medium does not have the format defined)