Since Kevin and Tod were interested in the data, I've uploaded to the web. You can download either the Access database or the tab-delimited data export from here: http://www.lib.ncsu.edu/staff/ejlynema/lc/ I noted on the page that this data is only available for public domain use within the US (according to my understanding of the copyright). So I guess if you wanted to use it outside of the US, you'd need to contact LC regarding permission. Maybe someone else can correct me if I'm wrong on that. I noticed the the tab-delimited export doesn't include the column headers, so you may need to look at the database to figure out what's going on. It's pretty self-explanatory, except the last column of data represents the level within the hierarchy for the call number range. Let me know if anybody has questions. -emily Kevin S. Clarke wrote: > I'd be interested in seeing it. > > Thanks, > Kevin > > > On 9/26/07, Emily Lynema <[log in to unmask]> wrote: > >>I also have the LC data. Right now it's in an Access database that >>includes the start and end of each call number range, and its level in >>the hierarchy. Which, of course, can become a number of other data >>formats as desired. :) I've exported it as delimited text to parse into >>XML via Perl in the past (unfortunately that XML format is proprietary >>and not useful to others). >> >>I don't have it posted for download anywhere, but could do if folks are >>interested. >> >>-emily >> >> >>>------------------------------ >>> >>>Date: Mon, 24 Sep 2007 20:18:40 -0400 >>>From: Ed Summers <[log in to unmask]> >>>Subject: Re: LC class scheme in XML or spreadsheet? >>> >>>It's funny this subject just came up on one of the open-library >>>discussion lists this week [1]. A whiles ago now Rob Sanderson, Brian >>>Rhea (University of Liverpool) and I pulled down the LC Classification >>>Outline pdf files, converted them to text, wrote a python munger to >>>convert the text into what ended up being a SKOS RDF file. We made the >>>code available [2] and you can see the resulting SKOS (which needs >>>some URI work) [3]. >>> >>>It's kind of a work in progress (still). I wanted to get to the point >>>that the rdf file was leveraged in a little python library (possibly >>>as a pickled data structure) for easily validating LC numbers and >>>looking them up in the outline. >>> >>>I'd be interested in any feedback. >>> >>>//Ed >>> >>>[1] http://mail.archive.org/pipermail/ol-lib/2007-September/000069.html >>>[2] http://inkdroid.org/svn/lcco-skos/trunk/rdfizer/ >>>[3] http://inkdroid.org/tmp/lcco.rdf >>> >>>------------------------------ >>> >>>End of CODE4LIB Digest - 21 Sep 2007 to 24 Sep 2007 (#2007-184) >>>*************************************************************** >> >>-- >>Emily Lynema >>Systems Librarian for Digital Projects >>Information Technology, NCSU Libraries >>919-513-8031 >>[log in to unmask] >> -- Emily Lynema Systems Librarian for Digital Projects Information Technology, NCSU Libraries 919-513-8031 [log in to unmask]