[SCC_Active_Members] Some candidate deliverables

[H.M. Gladney]

In our January meeting, you asked for suggestions of SCC deliverables.  This
note is a response.  I do recognize that the topics that follow have, to
some extent, already been discussed by the SCC, but am unaware of any
plans/actions that might already "in play" with proposed target dates.

 

I suggest that we plan and act towards three phases of repository
infrastructure for the eventual CHM software museum.  In this, the first two
phases are to be interim measures that will serve three purposes: (1) to
hold such materials as are collected before a stable repository service is
created and put into service; (2) to hold working materials (drafts,
proposals, e-mail, .) generated by and for the use of the SCC; and (3) to
provide to the SCC and museum staff hands-on experience with a digital
repository in order to define and refine a requirements analysis for the
final CHM software museum.

The first interim service should be whatever can be put into service for the
exclusive use of the CHM SCC not later than the end of April 2005.  (If the
CHM already has something suitable, this could be used; as I recall, PLONE
was discussed in December.)  It should be used to hold both copies of
content collected for injection into the eventual publicly accessible CHM
repository, including versions of that content that are not yet ready to be
museum offerings, and also working materials of the SCC.  This service will
need to be a combination of a traditional paper-based collection and a
digital library service.  Any ad hoc methodology that is convenient (low
cost) should be used.

This service (and those that eventually replace it) require a custodian, or
perhaps two custodians-one for the service infrastructure and one for the
holdings.  One or two SCC members should be found/chosen as soon as possible
to undertake these responsibilities.

Among other things, this first interim service needs a catalog.  This could
be implemented as simply as an orderly text file of citations. The taxonomy
that was presented at the SCC January meeting could serve as the first
organizing principle for this catalog.

The second interim service would be primarily for use by the CHM staff and
volunteer corps. <outbind://9/#_ftn1> [1]  Its software base would be a
publicly available digital library software package that can be installed
and operated at very low expense. <outbind://9/#_ftn2> [2]  The CHM should
not expend any resource to improve this software base (if it should be
lacking functionality deemed needed) or to tailor it to be pleasing to
viewers, because such expenses would not improve the eventual CHM software
museum, which might be based on a different software package.  I.e., the CHM
SCC should choose and use a turnkey package.  This library should be in
service not later than November 2005.

The final CHM digital repository should be chosen very carefully.  We can
anticipate that considerable effort will be required to adapt whatever
package is the chosen starting point for CHM use, including writing a
significant number of software extensions and manuals for local (CHM) usage.
The choice should have been made by year-end 2005.  Requirements for
extensions and a plan for creating, testing, and putting them into service
should be sufficiently complete so that their implementation could start
bbbbbby mid-2006.  Concurrently, estimates should be made of the resources
that will be required, and the financing for this should be sought using the
CHM management methodology.  The target date for public service should be
chosen.  Tentatively, a small subset of the full service might start as
early as 2008; realistically, the beginning of 'complete' service cannot be
earlier than 3Q09. <outbind://9/#_ftn3> [3]



  _____  


 <outbind://9/#_ftnref1> [1]     Perhaps parts of it might be opened for
public service.  However, until we have a requirements statement for
publicly available CHM software collection access for the general public, we
cannot prudently consider this topic.

 <outbind://9/#_ftnref2> [2]     The Greenstone package from New Zealand is
an attractive base for this service.  See Witten, Ian H. David Bainbridge,
How to Build a Digital Library, Morgan Kaufmann, 2003. ISBN 1-55860-790-0

 <outbind://9/#_ftnref3> [3]     This depends on personal judgments of the
state of available software and of what CHM will eventually decide it
requires.  The dates suggested will surely be revised as requirements
analyses and planning proceed.b

 
Best wishes, Henry
 
H.M. Gladney, Ph.D.
Saratoga, California 95070
http://home.pacbell.net/hgladney
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: ../attachments/20050212/9c7ef48f/attachment.html