![]() |
|||||
| | | | | | | | |||||
Research: Deliverables: D3.4 Information Gateways HandbookThe handbook and deliverables report are available online at:
Peer reviews of the handbook are also available:
AbstractThe Desire Information Gateways Handbook is designed to support libraries and other organisations interested in setting up large-scale information gateways on the Internet. It offers a step by step guide and points to tools, examples and documentation, which can support the process. The handbook is divided into three sections to reflect the managerial, information and technical issues that building a gateway raises. Section 1: Strategic Issues Section 1 of the handbook is aimed at the people responsible for strategic management - funders and project managers who will initiate the set up of a gateway and who will steer its direction over time. It aims to give an overview of the key issues involved in gateway projects, giving a rationale for these projects. It covers the important decisions that need to be made when setting up a new gateway (for example, staff effort, skills and costs) but also deals with logistics for managing an existing gateway. Section 2: Information Issues Section 2 of the handbook is aimed at gateway staff responsible for information management - the subject specialists and information professionals who will consider the content and organisation of the information within the gateway. It aims to cover the important decisions that need to be made when setting up a new gateway (such as choosing a metadata format, designing a use interface, writing a selection policy) but also covers issues that arise in the day-to-day running of an existing gateway (such as cataloguing, resource discovery and publicity and promotion). Section 3: Technical Issues Section 3 of this handbook is aimed at gateway staff responsible for technical implementation - Internet specialists who will manage the hardware and software and implement new technical features. It aims to cover the important decisions that need to be made when setting up a new gateway (such as setting up the system and implementing the user interface) but also covers issues that arise in the day-to-day running of an existing gateway (such as running a link checker). |
|
Contact | © 1998-2000 DESIRE Consortium | Disclaimer | Search Last updated: |