freedb

Note that every search result in FreeDB is identified by a unique ID, and that's all I'm storing until much later in the program.

a client component generates XML album descriptions with automatic FreeDB lookups that can be uploaded to the server for easier album entry.

I use the data returned from the FreeDB search to make an anonymous hash with the appropriate elements.

Note again that all search results are just string IDs that correspond to an album in the FreeDB database.

FreeDB is a volunteer effort organized to provide a free, unrestricted database of CD tracklists.

The %freedb_searches hash maps FreeDB fields to information about them, including ID3v2 tag elements.

The mapping between WebService: : FreeDB fields and ID3v2 tag elements is tentative, but it has worked very well for me.

I simply liked MP3: : Tag and WebService: : FreeDB better based on personal experience with them and for the reasons above.

Incidentally, I use "disc" instead of "disk" in variable names because that's what FreeDB uses.

Access CD information from freedb over internet.

Once results are returned from the FreeDB database, they are put in the %found_disks hash.

The %info2freedb hash maps FreeDB fields common across all tracks in a disc to ID3v2 fields.

Note that each "word" can contain spaces; the words are single search units as far as autotag. pl and FreeDB are concerned.

I used fuzzy string matching, FreeDB searches, ID3 versions 1 and 2, and lots of text-mode user interactions.

Fully compatible with FreeDB which automatically attains disc information over the Internet