Things needed for the Library WWW project
Status: These are my ideas, thoughts, and questions about
designing the library WWW service and are not Library
policy. I am not the author of some of the information.
- Development Plans
- Questions are -
- What do we want the service to be?
- How do we determine what the service should be?
- Can we design and mount an outstanding home page in the short
term?
- What definitive guidelines should be set for future development?
- What community planning should be encouraged and included?
- What are the priorities for building the service, both in
designing it and adding materials to it?
- How can individuals and units help?
- What abilities and resources are available? Resources include
computer programs.
- Should a development style guide be provided to workers?
- Technical Questions
- Questions are -
- Do we have the expertise to set up a Web Server now?
- Where should we mount a web home page?
- Can we mount a home page on a campus server?
- Would we have permission to use Library-specific CGI scripts on
the campus server?
- Expertise
- We need expertise in -
- Computer network systems
- Information management and presentation
- Hypertext systems
- Common Gateway Interface - CGI - applications
- Networking with other computer systems like the LAN and NOTIS
- Knowledge of Content Material
- We need knowledge of reference service processes,
patron needs, library collections, and subject materials.
Questions -
- What information would be neat?
- Call number arrangement
- Library maps
- Collection strengths
- Library History
- Library Planning
- What information is readily available?
- What would be worth creating?
- Materials already needed for library employees, for example,
certain kinds of computer training
- Materials needed for patrons
- Job Responsibilities Definition
-
- Will staff resources have to be reallocated to provide the time to
do a Web presence well?
- Will Managers agree this is an important issue?
JPF