It's not as bad as you think.
You see, I wrote a lot of the perl code used in this two other things I've been working on, and then mashed them together.
I have all the CD track information because I listen to a lot of CDs at work. The problem is that with over 150 CDs, the jewel boxes are a but unwieldy. So, I have them in two CaseLogic CD cases. The problem there is that I don't keep the CD liners in there because they make the cases too heavy (and I'm too lazy). See my problem? I have no idea what's on my CDs unless I take them out of the CD player and I'm lucky enough that the tracks are listed on the top.
My solution.
So I slowly went through each of my CDs and typed in all the information. Now I know what I'm listening to. I then used CD Coyote to export my CD information to a text file. A little text munging by my friend Perl and all of it goes in a GDBM database. The actual programming probably only took about 10 hours.
Hopefully someday, projects like DISCO will make this obsolete.
"This is sooo cool. How's it work?"
Well, there's this GDBM database that I wrote some perl routines to interact with to stay away from the guckiness of pretending a hash array is a relational database! If someone's really interested, maybe I'll give you the code.
"I still think you're a loser."
Think about this one: You've spent this much time actually reading this!
Time you could have spend doing something else:
Now who's the loser?
You see, eventually people will have spent more time playing with this page than I spent working on it. Then, the world, not I will have wasted time. Isn't the web great?
Jeff Boulter