I mentioned in my post that I had built the tables of persons but it was too big too attach. I have copied it to a web server and can be seen at www.miegel.org/persons.sql.
Do we have to write a new tagger? The least effort solution would be to write an SQL select statement and a Perl script to fetch the data from the database, flatten it, and convert to freedb format. The users can do this themselves specifying exactly what they want in the TRACK, ALBUM tags etc. For example, one user may have a music player that reads the COMPOSER tag and another user may have a reader that does not recognize the COMPOSER tag. The latter user would therefore want the composer name to be included in every TRACK tag. A tweak to the Perl script would give a freedb file that meets the user's requirements. Of course, this is the 'least coding' solution. It is not hard to think of better user interfaces. Does the freebd database contain good coverage? I personally find about 95% of my classical music CDs are in the freedb database, so I find Pat's comments about only 'three on ones' to be very strange. I was planning on initially populating the database by having a smart program that extracts data from the freedb database, but Pat's comments suggest this will not give us good coverage?! Does the data belong in tags? We don't have to decide that. With the proposed database, a user can have the data put into tags so existing music players can find the data, or the user can write software to take the data directly from the database. Do we want to add columns to the SS database? Again, I would see no reason why that could not be done. However, I don't think the SS database should be the official repository of the data. 1) Although I am a SS owner, I do not think we should prevent other users from using the database, 2) the database is online, 3) we would need to add columns and tables to the SS database and that would require either a fork of the SS software or polute the software for those users that are not interested in classical music. Do we have to write a tag editor? I would think this would be a very useful tool. While writing a tag editor from scratch may be a lot of work, there are open source libraries available so we need only replace the code that reads the freedb data with code that submits a query thru JDBC and then looks at the user's options to see what data the user wants in the standard tags. In my view, getting a good initial set of data in the CD, compositions, and performances tables will be a little tricky. Any automated tool is likely to fail to match data that is really the same (we will find the compositions table contains Beethoven's 'Symphony No. 9', and another piece called 'symphony 9 in D minor', and another piece called 'The Choral Symphony', if the conversion tool does not have a lot of clever pattern matching. We will then need a tool to merge the rows). Nigel -- nwestbury ------------------------------------------------------------------------ nwestbury's Profile: http://forums.slimdevices.com/member.php?userid=3284 View this thread: http://forums.slimdevices.com/showthread.php?t=19858 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
