I posted a bunch of messages there several months ago about this enhanced tagging problem (mostly classical) and began to work very hard on it.
After a lot of tries and errors, I managed to get two interesting things (I hope): 1. a "generic data model" represented by an XML schema (but it could be anything else) inspired by state of the art info source (allmusic, discogs, amazon). 2. a generic Perl library (object model) to manipulate the modelized data (in fact, the xml file). This work is on stand by since two months for personal reasons, but as I rely on it to manage my 2.000+ discs collection it will evolve as soon as I can work again on it. Reading your messages, I told myself it could be the right time to talk about it and open it to the community. This work can be used as a starting point for some kind of ideal solution to a common problem or just to feed the debate. For the curious, I posted details in the end of the message. Comments welcome. ============ PS: Right now, the modelized data are: Album, Disc, Track, Work/Song, Composer, Credit (credit can be anything from performer, singer, oboist, band, liner notes author...), Notes, Rating, Releases, Performance (and I forget others). Data like Credit or Composer can be associated with an album, a disc or a track to optimize data input. In Composer object you find birth and death dates, styles, period, in Performances you can find recording date/place, performers, In Work you can find catalog numbers, name, instruments, period, style, composing date, first played date, etc. The model is exhaustive but is designed to be used fully or partially (it's suitable for the simple artist/song/album pop scheme). PPS: >From an historical point of view, I tried to use the "standard tags", then "advanced standard tags", then I realized that only "specific personal tags" used by scripts to populate "advanced standard tags" could do the trick. Then, I realized that if I want my "specific personal tags" to be used for something else (web page generation, music collection management software, etc.), it would be clever to isolate these "specific personal tags" from the media file. Following these scheme, I chose an album oriented XML file where each XML file associated with an album is located in the album directory. But the data model is not specific to this serialization design and could fit a relational database or an xls spreadsheet file. -- vrobin ------------------------------------------------------------------------ vrobin's Profile: http://forums.slimdevices.com/member.php?userid=11705 View this thread: http://forums.slimdevices.com/showthread.php?t=43851 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
