From aek@bitsavers.org Tue Mar  6 15:21:26 2007
From: aek@bitsavers.org
To: test-drb@ccmp.vtda.org
Subject: bitsavers RSS beta
Date: Tue, 06 Mar 2007 13:21:26 -0800
Message-ID: <45EDDB56.5000108@bitsavers.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1777046205823018520=="

--===============1777046205823018520==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

 > Personally I find I sometimes get lost in the archive (via the web interfa=
ce)
 > though as a filename often doesn't obviously correspond to a document titl=
e.

The file naming has evolved over the 7+ years. In general, anything new is be=
ing
added with <manual part number> <title> <date>

This started on a system with 32 character file names, so <title> was ruthles=
sly
truncated, and as you noticed, <title> wasn't always the document title.

The worst problem with the current arrangement is file renaming and rearrange=
ment
of the heirarchy. I'm not sure if the mirrors reflect these rearrangements.

In general though, it seems to serve it's purpose, so I'm not inclined to spe=
nd
a lot of time adding database functionality to it.

I've been working on a MUCH harder problem on how to organize the CHM digital=
 holdings,
of which the bitsavers archive is a fairly tiny part.

--===============1777046205823018520==--