Kelly Leavitt wrote:
Here are my intended methods. If anyone has any
comments, please speak up.
That sounds good - it's about as comprehensive as you'll likely to get without
recording the actual flux transitions on the disk.
You could potentially store the disk catalogue (directory listing) in the
database too, outside of the disk images. That might be handy for searching /
comparing [1], although it's not vital - and it would require you to have
tools to read the directory information from the imagedisk / catweasel archive
formats at the point of inserting the images into the database.
[1] less of an issue for commercial software, but it's useful if you have a
lot of 'working' disks containing homebrew software and the like.
Some other things you might want to capture:
When you got each disk
Who you got it from
Some sort of 'batch' number
The latter can tie together disks that came in the same pile / haul / box and
can be useful if you find something interesting on one disk and want to
investigate others from the same batch to see what they contain.
Actually, I'd have a think about what sort of 'media type' fields would be
useful, such that you can have an archive which copes with other disk sizes
rather than just 8" - that way other people can add media once the archive
goes online.
cheers
Jules