Issue Details (XML | Word | Printable)

Key: MBS-5089
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Normal Normal
Assignee: Ian McEwen
Reporter: Wieland Hoffmann
Votes: 0
Watchers: 0
Operations

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

Statistics: "unique" number of ISWCs is higher than "all" number of ISWCs

Created: 04/Aug/12 07:29 PM   Updated: 01/Oct/12 01:25 PM   Resolved: 01/Oct/12 01:25 PM
Component/s: None
Affects Version/s: Bug fixes, 2012-07-23
Fix Version/s: 2012-10-01


 Description  « Hide

It's currently

ISWCs (all / unique): 27,676 / 27,716



Sort Order: Ascending order - Click to sort in descending order
Ian McEwen added a comment - 04/Aug/12 10:01 PM

I think these may be named incorrectly in light of the change to multiple ISWCs

count.iswc.all (the 'all' stat) has:

SELECT COUNT(DISTINCT work) FROM iswc

and count.iswc (the 'unique' stat) has:

SELECT COUNT(DISTINCT iswc) FROM iswc

One option is to change these to be displayed as "number of works with an ISWC" and "number of unique ISWCs", and keep the data collection as it is.

Interestingly, the isrc equivalents seem to be calculated differently, which is why they don't have this problem. The other option for these is to move to that, where the .all stat has, instead:

SELECT COUNT(*) from iswc
.

Thoughts?


Wieland Hoffmann added a comment - 05/Aug/12 11:01 AM

Interestingly, the isrc equivalents seem to be calculated differently, which is why they don't have this problem. The other option for these is to move to that, where the .all stat has, instead:

SELECT COUNT from iswc

.

Thoughts?

I prefer that.


Ian McEwen added a comment - 05/Sep/12 08:12 PM