2012-03-31 04:19:56 UTC
I am Saurav, and I have a idea proposal for MusicBrainz which can be done
as a GSoC project.
The idea is to incorporate the attribute 'genre' for the Music Data
available at MusicBrainz.
For this, the tag universe (the existing tag data) is used as a base.
The "Genre List" is taken from  http://musicgenreslist.com/ , which
is the 3rd
result for "Official List of Music Genres" (1st and 2nd being Wikipedia.com).
This arguably means that this page is the "most popular" all over the
it comes to people referring to Music Genres' List. Of course, genre
CAN be different on a more personal scale, but that is taken into consideration
by labelling an item to a particular genre solely on the basis of
This will become clear very soon.
Taking the list from , we now have a fixed list of genres. Also we
have the tag
universe, which will now be used to map items (artists, releases,
works) to their
respective genres. A particular entity will be assigned to a genre
if there is one in our genre-list) depending upon the most voted tag associated
with it. e.g. a Release group "Wish You Were Here" has the tags:
progressive rock 6
classic pop and rock 1
prog rock 1
psychedelic rock 1
should be public domain 1
So this recording will be assigned to genre:: Rock>>Prog-Rock/Art Rock
When enough information is not available for sub genre classification,
would be(e.g):: Rock
Note that the classification system will be intelligent (Rock, ROCK,
PROgresiv etc. will be identified correctly)
So much for 'existing' tags(and assignment of genres for them). Now
the case when
the user is entering new tags:
Case 1:: Entities which haven't been genre-fied as yet:
When a user edits, an auto-completion feature will show results from
and prompt him to enter a genre (this ensures that it is the users who
The user will choose one of the genres (and sub-genre too depending
upon how much he
knows). The user will also be able to enter additonal tags or vote on
existing tags, as before.
Case 2:: Entities which have been genre-fied before (by the user or
through our previously described scheme):
When the user edits, he will NOT be prompted for entering the genre.
He can only enter new
tags or vote on existing tags. The genre of the entity will change/not
how many votes the corresponding tags have and which is the currently
most preferred tag
(for genre). This ensures that the 'most-popular' tag is always chosen
for being called the
genre for the entity (and no additional 'power' is given to any one user).
e.g Suppose the tags for a particular entity (genre presently is pop)
were as follows:
Suppose now, two users voted for rock. The genre for the entity
changes to rock, as rock now
has 5 votes.
Note however that the genre classification depends only upon the tag
availability for an
entity (at least for the project in the summer). More work on this can
be looked into as
a future plan of action (having other attributes as well for entities
like beat-count, tempo
etc. which can be a more accurate measurer of genre). I am willing to
work in this even after summer.
-------------- next part --------------
An HTML attachment was scrubbed...