What I am
thinking of is several key volenteers positioned so as
to cover the major geographic areas who would be willing to set
up the necessary software and equipment to handle as many
different media types as possible, and provide a service to
nearby collectors to turn media into images, and to turn images
into media. Working with others in the project, the images
could be transmitted and shared so that any particuylar system
disk can be accessed from anywhere.
That much makes sense to me. I've been steadily collecting various relevant
odds and ends for the past couple of years with a view to doing just that -
various drives, controllers, tape units etc.
In order to spread this around as much as possible, we could probably do with
some "style guide" documents produced by some of the list gurus as to what
hardware works with what etc. (e.g. summarising things like the responses to
my recent question about hooking an 8" floppy drive up to a PC). That will
hopefully encourage more people to participate.
I agree - however, although platform specifc hardware will be a necessity for
some data types, I would also like to encourage platforn independance where
possible - it doesn't work too well if you are the key guy in your area, and you
can't make a disk someone needs - ImageDisk goes part way to solving this,
but there's still lots of things it can't do - we might want to include the
Catweasel
in our list of standard tools (or a similar device we might design ourselves
in our list of standard tools).
(There's certainly been a lot of knowledge shared
on this list in the past
about recovering old tapes too - it'd be nice to see that written up somewhere
"central")
Hmmm, it's not really a FAQ, but there's perhaps scope for something like a
"classiccmp.org knowledge base" containing info like this?
wiki?
= How to make
the archive available
Another tricky question, which has two major components, legality
and accessability.
I still think the key here is distribution. Allow people who have specialist
knowledge in a particular area to run their own little corner of the web as
they see fit - but they also "publish" what they've made available through
some defined mechanism. In addition, they present some unified way of
searching across *all* participating sites for content.
To extend that concept a little further (thinking on my feet here), how's
about we say that each "published" bit of data can be marked with different
levels:
"Offline" (say pending copyright issue resolution!)
Free for download (i.e. available to all users)
Available for mirror (to specific peers)
Available for mirror (to anyone wishing to make a mirror of the item)
Obvious benefits:
1) The "specialists" in any given area retain control over what they have
available, the format that it's in, and the "look and feel" of whatever
frills
surround the actual data.
Agreed to some extent, however I want to see the content distributed - perhaps
everyone directly involved in the project should maintain a private mirror of the
other parts.
Theres also the issue that someone who is great at collecting and archiving
material doesn have the ability to host a site (dial-up etc.) - So I can see that
one site might host multiple peoples contributions. But these are things that
would be worked out by the individuals involved.
2) There's no unwieldy central repository, with
corresponding high cost of
maintenance.
By "central repository", I don't (necessarily) mean a huge website and/or
FTP
with everything contained on it - but I would like to see a central resource where
people can begin a search for a specific need.To me this seems one of the
major benefits of a group project - concentration of information.
3) Mirroring is more controllable.
4) Searching (from a user POV) can be flexible and tailored to certain
pre-defined "classes" of content.
5) Copyright is at least a little less of an issue; if someone publishes
something that violates copyright, it's far more likely to come down on their
own head than jeaporising the distributed archive as a whole.
6) Dictating a "common archival format" that everyone agrees on probably
isn't possible, for various reasons. Look at what happened with Sellam's
efforts. However, dictating a common set of different content types (disk
image, documentation scan etc.), and the metadata fields that they can be
searched for with, is a heck of a lot easier!
It would be advantagous to agree on formats where it is appropriate, but
only when so, and It may make sense to use multiple formats in some
cases - for example, having Catweasel images of disks that can only be
made on a specific platform might avoid the chicken-and-egg thing where
you want to help someone, but you don't have the system, and he doesn't
have a bootable disk to launch the resident client.
7) Admin is a lot easier, as every participating
site owner is an admin of
the stuff that *they* make available, rather than having one person (or a
team) trying to look after everything - Al can probably comment on what a
headache this is!
Downsides:
1) Probably needs a web interface at least for the searching (but that's
not to stop someone making the actual data available over FTP or whatever, and
the search interface code could be produced in a variety of languages - PHP,
ASP etc. - to provide flexibility)
The only real complaint I've heard about a web interface is that it loses the
file dates - IMHO an os file date is a fragile information vessel at best - much
better to record relavent dates in the metadata associated with the archive.
2) The actual database of "what's
where" probably still needs to be
central, because distributing that across multiple sites (ala DNS) is likely
impractical, plus the majority of websites probably do have some server-side
scripting ability, but not necessarily any kind of coherent database support)
Yes, exactly what I was trying to state a couple of paragraphs back
Dave
--
dave06a (at) Dave Dunfield
dunfield (dot) Firmware development services & tools:
www.dunfield.com
com Collector of vintage computing equipment:
http://www.classiccmp.org/dunfield/index.html