Earlier today (yesterday? Shouldn't we be using those cute swatch beats to
count time already?) it was said that a group of voluntary editors would
manually correct the entries every day. Naturally this solution is far less
than perfect for a variety of reasons, the risk of running out of volunteers
not being the least of them.
I eventually thought about a way to have thousands of volunteers. We use the
users, by implementing a simple voting algorithm. It will certainly
complicate the schema and the code a little bit, but I think it pays.
Suppose my player shows a song name as "New Iork, New York". My player will
have an "edit" option, letting me submit a correction. This correction is
stored as an "<alternative track name>", along with a count. From time to
time a daemon checks the votes for each track and "promote" <alternative> to
<track name>.
If I am no mistaken, the lyrics server worked that way (letting people
correct the lyrics of a song someone else had submitted).
In a global system, I think the data will naturally tend to its correct
form. Naturally this system is open to abuse (it is easy to create a script
to vote). But I think we can devise some protection along the way.
cheers
Paulo