TECHNICAL ANNEX

Title: OPAC Network in Europe (ONE)

Project Number:LIB-ONE/2-3099

WORK PROGRAMME

TABLE OF CONTENTS

PART I. GENERAL PROJECT OVERVIEW	10

1.	PARTICIPANTS AND THEIR ROLE WITHIN THE PROJECT	10

2.	SUMMARY OF THE PROJECT	16

3.	OBJECTIVES OF ONE	25

3.1 SERVICE OBJECTIVES	25

3.2 TECHNICAL OBJECTIVES	26

3.3 RESEARCH OBJECTIVES	27

3.4 STANDARDISATION OBJECTIVES	27

4.	CONTRIBUTIONS TO THE OBJECTIVES OF THE LIBRARY PROGRAMME	28

5. WORKPLAN OF THE PROJECT	42

5.1	1000	PROJECT MANAGEMENT AND ADMINISTRATION	45

5.1.1 WP1100	Project management and administration	45

5.1.1.1 Task 1101 to 1105. Project management and administration	49

5.1.1.2 Task 1111 to 1115 Work Area management	49

5.1.1.3 Tasks 1121 to 1125. Writing progress reports and edited reports	50

5.1.1.4 Task 1130. Writing the final report	50

5.1.1.5 Task 1141 to 1145. Project meetings	50

5.1.2 WP1200	"Use and usability" working area management and administration	51

5.1.2.1 Tasks 1201 to 1205	Working area management and administration	54

5.1.2.2	Task 1210	Negotiations on service contracts	54

5.1.3 WP1300	"Software development" working area management and administration	54

5.1.3.1	Tasks 1301 to 1305	Working Area Management and administration	56

5.1.4 WP1400	Dissemination and Exploitation Working Area management and administration	56

5.1.4.1	Tasks 1401 to 1405	Working Area management and administration	58

5.1.5 WP1500	Quality Assurance	59

5.1.5.1 Tasks 1501 tp 1505. WP1500 management	61

5.1.5.2	Tasks 1510 Define methods and measures for Quality Control	61

5.1.5.3 Tasks 1521 to 1525. Quality control	61

5.2	2000	REQUIREMENTS AND SPECIFICATION	61

5.2.1 WP2100	SR software evaluation	62

5.2.1.1	Task 2100	WP2100 management	64

5.2.1.2	Task 2110	Definition of evaluation forms	64

5.2.1.3	Task 2120	SRPM Software evaluation	64

5.2.1.4	Task 2130	Client Software evaluation	65

5.2.1.5	Task 2140	Communication stack evaluation	65

5.2.1.6	Task 2150	Choice of software basis for SRPM in ONE	66

5.2.2 WP2200	Specification of services to be offered	66

5.2.2.1	Task 2200	WP2200 Management	68

5.2.2.2	Task 2210	Services in partners' systems	68

5.2.3 WP2300	SRPM requirements and specifications	69

5.2.3.1	Task 2301 to T2303	WP2300 management	71

5.2.3.2	Task 2310	Common SRPM Requirements	71

5.2.3.3	Task 2321 and T2322	Common SRPM specifications	72

5.2.3.4	Task 2330	Local system SR specification	72

5.2.3.5	Task 2341 and 2342 Specification of communication stacks	73

5.2.4 WP2400	EXPLAIN requirements and specifications	73

5.2.4.1	Task 2401 and T2402	WP2400 management	75

5.2.4.2	Task 2410	General EXPLAIN requirements	75

5.2.4.3	Task 2420	General EXPLAIN specifications	76

5.2.5 WP2500	API and Toolbox	76

5.2.5.1	Task 2501 and T2502	WP2500 management	79

5.2.5.2	Task 2510	API specification	79

5.2.5.3	Task 2520	Toolbox requirements	80

5.2.5.4	Task 2530	Toolbox specifications	80

5.2.6 WP2600	NEP Requirement and Specification	81

5.2.6.1	Task 2600 WP2600 management	82

5.2.6.2	Task 2610 NEP Requirements	83

5.2.6.3	Task 2620 NEP Specifications	83

5.2.7 WP2700	Stand-alone client requirements and specification	83

5.2.7.1	Task 2700 WP2700 management	85

5.2.7.2	Task 2710 Stand-alone client Requirements	85

5.2.7.3	Task 2720 Stand-alone client Specifications	86

5.3	3000	DESIGN OF SOFTWARE	87

5.3.1 WP3100	Design of SRPM	87

5.3.1.1	Task 3101 to T3103	WP3100 management	89

5.3.1.2	Task 3110	Common SRPM version 1 design	89

5.3.1.3	Task 3120	Common SRPM version 2 design	90

5.3.1.4	Task 3130	Local system SR-design, version 1	90

5.3.1.5	Task 3140	Local system SR-design, version 2	91

5.3.1.6	Task 3150	NEP design, version 1	91

5.3.1.7	Task 3160	NEP design, version 2	91

5.3.1.8	Task 3171 to 3172	Stack design and installation	92

5.3.2 WP3200	Stand-alone client, Generic user assistance and EXPLAIN design	92

5.3.2.1	Task 3201 and 3202	WP3200 management	94

5.3.2.2	Task 3210	Stand-alone client design	94

5.3.2.3	Task 3221 and 3222	Design of EXPLAIN in NEP	94

5.3.2.4	Task 3231 and 3232 Design of EXPLAIN in local systems	95

5.2.3.5	Task 3240 Generic user assistance design	95

5.3.3 WP3300	Design of API and Toolbox	96

5.3.3.1	Task 3301 to 3303	WP3300 management	98

5.3.3.2	Task 3310	Design of API	98

5.3.3.3	Task 3321 and 3322	Design of Toolbox	98

5.4	IMPLEMENTATION	100

5.4.1 WP4100	Implementation of SRPM	100

5.4.1.1	Task 4101 to 4103	WP4100 management	102

5.4.1.2	Task 4110	Common SRPM Version 1 implementation	102

5.4.1.3	Task 4120	Common SRPM Version 2 implementation	102

5.4.1.4	Task 4130	Local system SR-implementation, Version 1	103

5.4.1.5	Task 4140	Local system SR-implementation, Version 2	103

5.4.1.6	Task 4150	NEP implementation, Version 1	104

5.4.1.7	Task 4160	NEP implementation, Version	104

5.4.2 WP4200	Stand-alone client, Generic user assistance, and EXPLAIN implementation	105

5.4.2.1	Task 4200	WP4200 management	107

5.4.2.2	Task 4210	Implementation of Stand-alone client	107

5.4.2.3	Task 4220	Implementation of EXPLAIN in NEP Version 2	107

5.4.2.4	Task 4230	Implementation of EXPLAIN in local systems, Version 2	107

5.4.2.5	Task 4240	Implementation of generic user assistance	108

5.4.3 WP4300	Implementation of API and Toolbox	108

5.4.3.1	Task 4301 to 4303	WP4300 management	110

5.4.3.2	Task 4310	Implementation of API	110

5.4.3.3	Task 4321to 4323 Implemetation of Toolbox	111

5.5	5000	TESTING AND OPERATIONS	112

5.5.1 WP5100	Interoperability testing	112

5.5.1.1	Task 5101 to 5105	WP5100 management	114

5.5.1.2	Task 5110	Definition of interoperability test suite for existing systems	114

5.5.1.3	Task 5120	Interoperability testing of existing systems	115

5.5.1.4	Task 5130	Documentation of the test results	115

5.5.1.5	Task 5140	Definition of interoperability test suite for Version 1	116

5.5.1.6	Task 5150	Interoperability testing of version 1 of systems	116

5.5.1.7	Task 5160	Definition of interoperability test suite for Version 2	116

5.5.1.8	Task 5170	Interoperability testing of version 2 of systems	117

5.5.1.9	Task 5180	Documentation of interoperability testing	117

5.5.2 WP5200	Application interworking	118

5.5.2.1	Task 5201 to 5202	WP5200 management	119

5.5.2.2	Task 5210	Creating test environment	120

5.5.2.3	Task 5220	Application interworking tests	120

5.5.3 WP5300	Organisation and administration of trial service	121

5.5.2.1	Task 5301 to T5303	WP5300 management	123

5.5.2.2	Task 5310	Planning trial service, version 1	123

5.5.2.3	Task 5320	Planning trial service, version 2	123

5.5.2.4	Task 5331 and 5332	Choosing, and preparing, users for participation in testing	124

5.5.4 WP5400	User testing (trial service)	124

5.5.4.1	Task 5401 to 5403	WP5400 management	127

5.5.4.2	Task 5411 to 5412	Porting software	128

5.5.4.3	Task 5421 to 5423	User training	128

5.5.4.4	Task 5431 to 5433	User support	128

5.5.4.5	Task 5441 to 5442	Technical Support	129

5.5.4.6	Task 5450 Analysis of search results (based on session logs)	129

5.5.4.7	Task 5460 Analysis of errors and error situations (based on session logs)	129

5.5.4.8	Task 5470 Analysis of user reactions and experiences	130

5.6	6000	USER INTERFACE	131

5.6.1 WP6100	User interface	131

5.6.1.1	Task 6101 to 6103	WP6100 management	133

5.6.1.2	Task 6110 Defining forms for describing local user interfaces	133

5.6.1.3	Task 6120 Local user interface analysis (search possibilities, present possibilities, help functions, sort, etc.)	133

5.6.1.4	Task 6130 Requirements for user assistance (all types of users)	134

5.6.1.5	Task 6140 Specification of generic user assistance	134

5.6.1.6	Task 6150 Mapping generic user assistance services to EXPLAIN	135

5.7	DISSEMINATION AND EXPLOITATION	136

5.7.1 WP7100	Dissemination and exploitation	136

5.7.1.1	Task 7101 to 7105	WP7100 management	139

5.7.1.2	Task 7110	Dissemination plan	140

5.7.1.3	Task 7121 to 7125	Dissemination of information	140

5.7.1.4	Task 7130 Exploitations plan	141

5.7.1.5	Task 7141 to 7143	Porting common software	141

5.7.1.6	Task 7151 to 7153 Maintenance of common software	142

5.7.1.7	Task 7160 Preparation for exploitation activities	142

5.8	8000	STANDARDISATION	143

5.8.1 WP8100	Study of standards with amendments	143

5.8.1.1	Task 8101 to 8105	WP8100 management	145

5.8.1.2	Task 8110	Study of SR and proposed enhancements	145

5.8.1.3	Task 8120	Study of Z39.50 Version 3	146

5.8.1.4	Task 8130	Study of TOSI	146

5.8.1.5	Task 8140 Study of mOSI	146

5.8.1.6	Task 8150	Update of ISP ALD11	147

5.8.1.7	Task 8160 Proposal for standard enhancements	147

5.8.1.8	Task 8171 to 8175 Participation in standardisation bodies	147

5.9	9000	DOCUMENTATION	149

5.9.1 WP9100	User documentation	149

5.9.1.1	Task 9101 to 9105	WP 9100 management	151

5.9.1.2	Task 9110	Defining rules and forms for documentation (all types)	151

5.9.1.3	Task 9121 to 9124	User documentation (for use of SR module)	152

5.9.1.4	Task 9131 to 9134	Installation documentation	152

5.9.1.5	Task 9141 to 9144	System operation documentation	153

5.9.1.6	Task 9151 to 9155	Software documentation	154

PART I. GENERAL PROJECT OVERVIEW

Project Nr.	LIB-ONE/2-3099

Title/acronym	OPAC Network in Europe/ONE

Project duration	30 months

Participants	Role

Oslo College - BRODD (N)	C

British Library (BL) (UK)	P

Danish Library Centre (DBC) (DK)	P

Die Deutsche Bibliothek (DDB) (D)	P

- Pica (ass. to DDB) (NL)	A

Joanneum Research (JR) (A)	P

- Die Steiermärkische (LB) (A) Landesbibliothek (ass. to JR) A

- Steiermärkische Landesmuseum, bibliothek (ass. to JR) A

(LMJ) (A)

Royal Library - LIBRIS (S)	P

National Library (NB) (N)	P

- BIBSYS (ass. to NB) (N)	A

- University Library of Oslo (ass. to NB) (N)	A

Satellites International Ltd. (SIL) (UK)	P

- National Museum (NM) (DK) (ass. to SIL)	A

Helsinki University Library , TKAY (SF)	P

1.	PARTICIPANTS AND THEIR ROLE WITHIN THE PROJECT

There are 15 partners in the ONE project. Of these 9 are full partners and 6 associated partners.

The full partners will participate both in development and testing of the software. They will also participate in the trial service.

The associated partners fall in two categories. The first of these consists of institutions developing, maintaining and operating national library services and databases (BIBSYS, Pica, UBO). These partners will participate in developing and testing software equal to the full partners.

The other category consists of libraries giving access to their systems (LB, LMJ, NM). These partners will be test places for the commonly developed software.

All associated partners will participate in the trial service.

In the following acronyms will be used for the partners according to this list:

BIBSYS	BIBSYS Norway

BRODD	Oslo College - department of journalism, library and information science - unit BRODD

BL	British Library

DBC	Danish Library Centre

DDB	Die Deutsche Bibliothek

JR	Joanneum Research

LB	Die Steiermärkische Landesbibliothek

LIBRIS	Royal Library of Sweden, LIBRIS department

LMJ	Steiermärkische Landesmuseum Joanneum

NB	National Library of Norway

NM	Danish national Museum, The library

Pica	Centrum voor Bibliotheekautomatisering

SIL	Satellite International Limited

TKAY	Helsinki University Library - TKAY

UBO	University of Oslo Library

Contact names and addresses

The contact persons are sorted according to acronym for institution, but the coordinating institution is mentioned first.

Oslo College - department of journalism, library and information science - section BRODD

Dælenenggaten 26

0567 Oslo

NORWAY

Contact person: Liv A. Holm

tel.: +47-22-35-02-66

fax.: +47-22-35-12-60

email: Liv.A.Holm@BIBHS.NO

Michael Preminger

tel.: +47-22-35-02-66

fax.: +47-22-35-12-60

email: Michael@pclan.bibhs.no

BIBSYS

7034 Trondheim

NORWAY

Contact person: Ole Husby

tel.:+47-73-59-29-59

fax.:+47-73-59-68-48

email: Ole.Husby@BIBSYS.no

Roar Fosshaug

fax.:+47-73-59-68-48

email: Roar.Fosshaug@bibsys.no

British Library (BL)

2 Sheraton Street

London W1V 4BH

UK

Contact person: Neil Smith

tel.: +44-71-323-7043

fax.: +44-71-323-7336

email: Neil.Smith@BL.UK

Joyce Williams

tel.: +44-171-412-7071

fax.: +44-171-412-7336

email: Joyce.Williams@bl.uk

Annette Cooper

Tel: +44 71-323 7189

FAX: +44 71-323 7336

E-mail: Annette.Cooper@bl.uk

Danish Library Centre (DBC)

Tempovej 7-11

2750 Ballerup

DENMARK

Contact person: Poul Henrik Jørgensen

tel.: +45-44-97-40-00

fax.: +45-44-97-14-85

email: phj@find2.denet.dk

Morten Holmqvist

tel.: +45-44-97-40-00

fax.: +45.44.68.53.13

email: netrom@find2.denet.dk

Die Deutsche Bibliothek (DDB)

DV/DBV-OSI II

Zeppelinallee 4-8

60325 Frankfurt

GERMANY

Contact person: Bernd Luchner

tel.: +49-69-75-66-724

fax.: +49-69-75-66-709

email:luchner@dbf.uni-frankfurt.d400.de

Joanneum Research - Institute for Information Management (JR)

Hans-Sachs Gasse 14/3

A-8010 Graz

AUSTRIA

Contact person: Walter Koch

tel.: +43-316-83-53-59-0

fax.: +43-316-83-53-59-75

email: Koch@Joanneum.ada.at

Die Steiermärkische Landesbibliothek (LB)

Partnerostfach 861

A-8011 Graz

AUSTRIA

Contact person: Franz Joseph Desput

tel.: +43-316-80-16-46-00

fax.: +43-316-80-16-46-33

email: Desput@IMA010.Joanneum.ac.at

Royal Library (LIBRIS)

LIBRIS

Box 5039

102 41 Stockholm

SWEDEN

Contact person: Göran Skogmar

tel.: +46-8-783.39.05

fax.: +46-8-783.39.30

email:skogmar@libris.kb.se

Mayre Lehtilä-Olsson

tel.: +46-8-783.39.05

fax.: +46-8-783.39.30

email: Mayre.Lehtila-Olsson@libris.kb.se

Steiermärkische Landesmuseum Joanneum (LMJ)

Raubergasse 10

A-8010 Graz

AUSTRIA

Contact person: Walter Postl

tel.:+43-8017-4741

fax.:+43-8017-4800

email: Postl@IMA010.Joanneum.ac.at

National Library of Norway (NB)

Bygdø allé 21

0262 Oslo

NORWAY

Contact person: Torbjørn Navelsaker

tel.: +47-22-55-33-70

fax.: +47-22-55-38-95

email: Torbjorn.Navelsaker@rbt.NO

Danish National Museum, The library (NM)

Frederiksholms Kanal 12

DK-1220 Copenhagen

DENMARK

Contact person: Berit Elgaard

tel.: +45-33-47-38-83

fax.: +45-33-47-33-07

email: bib-be@palais.natmus.min.dk

Niels Bergmann

fax.: +45-33-47-33-07

email:bib-nb@palais.natmus.min.dk

Pica

Postbox 876

NL-2300 AW Leiden

THE NETHERLANDS

Contact person: Makx Dekkers

tel.: +31-71-257-257

fax.: +31-71-223-119

email: Dekkers@Pica.NL

Jan-Metten van der Meer

tel.: +31-71-257-257

fax.: +31-71-223-119

email: Meer@pica.nl

Satellite International Limited (SIL)

The Paddock

Hambridge Road

Newbury

Berks RG14 5TQ

UK

Contact person: Robert Bull

tel.: +44-635-46-254

fax.: +44-635-38-785

email: bull@sun001.SIL.com

Helsinki University Library (TKAY)

TKAY

P.Box 26 (Teollisuuskatu 23)

FIN - 00014 University of Helsinki

FINLAND

Contact person: Antti Soini

tel.: +358-0-708.42.94

fax.: +358-0-753.95.14

email: Antti.Soini@HELSINKI.FI

Juha Hakala

tel.: +358-0-708.42.93

fax.: +358-0-753.95.14

email: Juha.Hakala@HELSINKI.FI

University of Oslo Library (UBO)

Drammensveien 42

0242 Oslo

NORWAY

Contact person: Øivind Berg

tel: +47-22-85-92-27

fax: +47-22-85-90-50

email: Oivind.Berg@UB.UIO.NO

Torstein Tjelta

tel.: +47-22-85-91-34

fax: +47-22-85-90-50

email: Torstein.Tjelta@UB.UIO.NO

2.	SUMMARY OF THE PROJECT

The ONE project is a cooperative project involving national library facilities in Austria, Denmark, Finland, Germany, the Netherlands, Norway, Sweden and UK.

The major service objectives of the project are to:

*	link the users of these facilities to the information resources available in the catalogues run by the participants.

*	establish a service infrastructure for searching in Europe which can be extended to include resources worldwide through the Internet, and can be further expanded to allow ordering of publications found through searching.

*	define the functional requirements for search services in a European context with special attention for on-line explain facilities

*	establish a trial service between the users and databases of the participants involving a wide range of users.

*	allow the participants to formulate and test their strategies to provide trans-national services on the basis of the outcome of the trial service

On the technical level, the major objectives are to:

*	implement the international standards for catalogue access, ISO/SR and Z39.50 in the different technical environments of the participants with special emphasis on the interworking between protocol services provided in both the OSI and the Internet protocol environments.

*	produce a set of software tools intended to be portable to a range of system platforms; these tools will take the form of software libraries providing an API for communication functions and a toolbox for additional functions such as conversion between different formats for bibliographic records and character conversions.

*	integrate this set of software tools in the participants' systems insofar as the tools meet the requirements of the participants; within the project, installation will be restricted to UNIX platforms.

*	develop and install a Neutral Entry Point software package on a multi-user UNIX platform which can be used as a dial-in facility for terminal-based access.

*	develop and install a PC-client (Windows-based), and a UNIX-MOTIF client, package.

All development within the project will aim at POSIX compliance. Special care will be given to produce high-quality, cost-effective and well-documented software with a wide applicability.

Experiences built in the project will lead to recommendations to define the requirements for international services and legal and financial arrangements between central organisations. Also, the project will point out requirements for further development of the standards and associated communication profiles implemented.

3.	OBJECTIVES OF ONE

The main aim of the project is to link users to information by linking together library systems via open systems' network, and through the implementation of such network to enhance the international standards for intersystem communication.

The aim of the project is divided into four groups as follows:

1.	Service objectives

2.	Technical objectives

3.	Research objectives

4.	Standardisation objectives

3.1	SERVICE OBJECTIVES

The service objectives of the project is to link users to information. The type of users who will benefit from the ONE network are:

-	library staff

-	researchers and scientists

-	library patrons

The main service outcome of the project will be:

*	the library users of the participating institutions will be linked to the information resources available in the catalogues run by the participants.

*	a service infrastructure for searching in Europe will have been established which can be extended to include resources worldwide through the Internet, and can be further expanded to allow ordering of publications found through searching.

*	the functional requirements for search services in a European context with special attention for on-line explain facilities will be defined

*	a trial service between the users and databases of the participants involving a wide range of users will have been carried out and the results analysed.

*	the participants will be in a position to formulate and test their strategies to provide trans-national services on the basis of the outcome of the trial service

3.2 TECHNICAL OBJECTIVES

The technical objectives of ONE are:

-	to link together existing SR/Z39.50 implementations in the participating institutions

-	to enhance existing SR/Z39.50 implementations in the participating institutions

-	to develop an SR/Z39.50 kernel and a "neutral" client package with the complete set of protocol services defined

-	to define, and implement, different network stacks to run the SR/Z39.50 kernel on;

the participating systems are using different stacks for the lower network layers. The mechanism for switching between the use of different stacks depending on which systems communicate, will be developed.

-	to define interoperability test suite for the enhanced ISO standard 10163.

-	to develop a toolkit for functions such as MARC conversion, character conversion, CCL- RPN translation etc.

The main technical outcome of the project will be:

*	Operational implementations of SR/Z39.50 protocol services including the protocol services added to the base standard

*	Reliable, high-quality software packages for network communication between library- and information systems

*	A Neutral Entry Point and a Stand-alone Client package with the full set of SR/Z39.50 protocol services implemented

*	Communication between SR/Z39.50-implementations on different platforms and in different network environments.

*	Interoperational Test Suite for the full SR/Z39.50-standard

*	Testing of the profile ALD11 (SR/Z39.50 in connection oriented mode)

All software developed in the project will, if possible, be enhancements of existing software packages. These enhancements will for instance be implementations of amendments to the standards.

3.3 RESEARCH OBJECTIVES

The research objective is to investigate the need for generic user assistance in library systems and how these needs can be mapped to requirements for an EXPLAIN protocol service. The research objective also includes how the generic user assistance can be implemented in different environments.

The main research outcome of the project will be a well defined EXPLAIN protocol service and generic user help mapped to the EXPLAIN protocol service.

The problems of different character sets will be addressed.

3.4 STANDARDISATION OBJECTIVES

The standardisation objective of the project is to influence the development of SR/Z39.50 through experience in communication between the participating systems, and through participation in the standardisation bodies.

The main standardisation outcome of the project will be enhancement proposals to the SR/Z39.50-standard and/or to the lists of registered values used in communication between library systems.

The International Standardised Profile (ISP) for Search and Retrieve (SR) using connection- oriented ACSE, ALD11 is defined for the SR standard version 1. Many enhancements are proposed for the SR standard (see section 6.3) and therefore either an update of ALD11 concerning the additional protocol services defined, or a new profile will be needed. The outcome of the project will be a basis for such an update or new profile.

4.	CONTRIBUTIONS TO THE OBJECTIVES OF THE LIBRARY PROGRAMME

The project contributes to Action Line II through the development of new networked library services by implementing and testing services necessary to use the ISO SR/Z39.50 protocol in a wider environment. In specific the project addresses:

Theme 9: Retrieval function - interconnected OPACs

The project contributes to all the specific objectives of Action Line II and the wanted key results as it:

-	establishes operational links between different library catalogue systems, and thereby the systems' users, offering access through the enhanced SR/Z39.50 protocol over international networks

-	fosters the use of international standards and European profiles

-	provides a testbed for other library systems implementing the SR/Z39.50-protocol and its enhancements.

The project contributes to the general objective by developing an Interoperability Test Suite for the enhanced SR/Z39.50 protocol.

The project has its main body under Action Line II as its main goal is to implement and test all the standardised SR/Z39.50 protocol services both for the SR/Z39.50 Origin and for the SR/Z39.50 Target. However, by implementing the addenda to the ISO standards ISO 10162 and ISO 10163, the library users will be able to use the results of the project in their daily work and thus the project will contribute to the specific objectives in Action Line III:

-	through the use of these network protocol services, stimulate the demands for new services

-	through the use of these network protocol services, extend the access and availability of bibliographic information

5. WORKPLAN OF THE PROJECT

The project work will concentrate on two main tasks:

-	to establish a network of library system servers in Europe

-	to improve the end-user assistance in such a network

Work Areas

The ONE project is split into four Working Areas (WA):

1	Management and Quality Assurence (5 Work Packages)

2	Use and Usability (9 Work Packages)

3	Software Development (7 Work Packeages)

4	Dissemination of Information and Results (5 Work Packages)

Each Work Area is managed by a Work Area manager (WAM). The WAM is responsible for the Work Packages in his Work Area.

The objective of Work Area 1 is to ensure high quality on all deliverables and an efficient management.

The Work Packages in Work Area 1 are:

WP1100	Project management and administration

WP1200	"Use and usability" working area management and administration

WP1300	"Software development" working area management and administration

WP1400	"Dissemination" working area management and administration

WP1500	Quality Assurance

The objective of Work Area 2 is to define requirements and specification for services and software.

It is also an objective for this Work Area to ensure the use of the software developments in the project.

This Working Area also includes the interoperability testing.

The Work packages in Work Area 2 are:

WP2200	Specification of services to be offered

WP2300	SRPM requirements and specifications

WP2400	EXPLAIN requirements and specifications

WP2500	API and Toolbox

WP2600	NEP Requirement and Specification

WP2700	Stand-alone client requirements and specification

WP5100	Interoperability testing

WP5200	Application interworking

WP6100	User interface

The objective of Work Area 3 is to coordinate the development of the different software modules in the project and to ensure that these modules are satisfactorly tested before released for the Trial Service.

The Work Packages in Work Area 3 are:

WP2100	SR software evaluation

WP3100	Design of SRPM

WP3200	Stand-alone client, Generic user assistance and EXPLAIN design

WP3300	Design of API and Toolbox

WP4100	Implementation of SRPM

WP4200	Stand-alone client, Generic user assistance, and EXPLAIN implementation

WP4300	Implementation of API and Toolbox

The objective of Work Area 4 is to coordinate all tasks connected with dissemination of information.

The Work packages in Work Area 4 are:

WP5300	Organisation and administration of trial service

WP5400	User testing (trial service)

WP7100	Dissemination and exploitation

WP8100	Study of standards with amendments

WP9100	User documentation

Phases

The ONE project is split into five technically and chronologically well defined phases.

Phase 1, lasting 6 months, is a study, evaluation and requirement phase. The relevant standards will be studied. The available software packages for SR/Z39.50 will be evaluated and a basis for ONE-software will be chosen. Requirements for ONE-software will be defined. For some modules it will be requirements for version 1, for others requirements for the full version. Specification for some modules will also be prepared in phase 1.

Phase 2, lasting 6 months, is a design and implementation phase for the first version of the ONE software.

Phase 3, lasting 4 months, is a requirement and specification phase for the final version of the ONE software. In phase 3 the trial service starts. The end-users will be able to use version 1 of the ONE software.

Phase 4, lasting 6 months, is the design and development phase for the final version of the ONE software.

Phase 5, lasting 8 months, is the trial service phase. The last part of the phase will be used for analysing the results of the trial service.

Platforms for ONE software

The common software origin and client development will first be on the UNIX system V operating system with BSD additions such as sockets. Where possible, compliance towards the POSIX standard will be adhered to. Later, the software may be "ported" to other platforms such as RS6000 AIX.

The API and Toolbox functions will be written in standard ANSI C code to promote portability to other platforms such as PCs. Where X-Window user interfaces are developed, the OSF-Motif interface will be used which offers greater portability than proprietary user interfaces.

The NEP standalone client will be written for UNIX/OSF-Motif and for the PC/Microsoft Windows platform.

There are many other possibilities for local system and NEP platforms, particularly with the many variants of PCs and associated operating systems that will appear in the next few years. It will not be possible for all such platforms to be ported to, but this may be the subject of exploitation for project partners in the future.

Work Package numbering structure

Below follows the description of the Work Packages (WP) and Tasks. For each WP it is noted which WA it belongs to. In order to have well defined phases, some logical tasks (which lasts for two or more phases) are split into sequencial tasks, one for each phase.

The WPs are grouped as follows:

1000	PROJECT MANAGEMENT AND ADMINISTRATION

2000	REQUIREMENTS AND SPECIFICATION

3000	DESIGN OF SOFTWARE

4000	IMPLEMENTATION

5000	TESTING AND OPERATIONS

6000	USER INTERFACE

7000	DISSEMINATION AND EXPLOITATION

8000	STANDARDISATION

9000	DOCUMENTATION

The sequence of work

The work is structured in the following way:

Analysis - requirements - specification - design - implementation - trial service

This structure is repeated for each of the two versions of the software.

The project work starts with anylysis of existing software packages, user interfaces and user needs. Then requirements for services and user assistance are identified.

The next step is the specification of the requirements for implementation, i.e. which requirements can be met and which can not. Then the design of the software modules take place, and finally the implementation (coding) of the software modules.

When the modules have been implemented and syntax tested, the trial service will be started.

Since most of the software will be developed in two stages (version 1 and version 2), the results of the specification, design and implementation of version 1, will influence the requirements for the full version (version 2). After the implementation of version 1, we will therefore again have a requirement and specification phase. This is followed by the design and implementation of the full version.

The software modules will be developed in steps in order to start end-user testing at an early stage. A limited user testing will start in phase 3, while the full trial service takes place in Phase 5.

The last part of the last phase is dedicated to analysis of the trial service.

5.1	1000	PROJECT MANAGEMENT AND ADMINISTRATION

5.1.1 WP1100	Project management and administration

Name and number of work package

The name of Work Package 1100 is:

Project management and administration.

Working Area

This WP is 1 of 5 in Work Area Management and Quality Assurance.

Partner

Responsible for the WP: BRODD

Other partners that will participate in this WP:

All Partners will be participate in one or more of the tasks.

As Coordinator BRODD is responsible for formal liason and reporting to the Commission.

Partners assume responsibility for management of their designated work packages correponding overall project management tasks.

Objectives

The ONE project management structure is designed to

-	meet the requirements for effective and efficient steering of all project activities according to the workplan

-	make efficient decision-making possible

-	monitor progress, and take corrective action if necessary

-	make a rapid information flow and full internal and external concentration and assessment possible

WP 100 is subdivided into the following tasks:

Task 1101 to 1105:	Project management and administration - Phase 1 to Phase 5

Task 1111 to 1115:	Work Area management - Phase 1 to Phase 5

Task 1121 to 1125:	Writing progress reports and edited reports - Phase 1 to Phase 5

Task 1130:	Writing the final report

Task 1141 to 1141:	Participation in project meetings, Phase 1 to Phase 5

Prerequisites:

None.

Approach:

The administrative management of the project will build on a hierarchical structure.

The Work Package Managers will manage their WPs and control the use of resources and time. They will use time sheets for report on the use of resources, and monthly report to the WAM of the progress of the work. Deviation from project plans will thus be discovered early.

The Work Area Managers will supervise the work, and use of resources, in their Work Area and give bi-monthly reports to the Project Manager.

All reimboursment is handled by the Project Manager and her Accounting Department. Reimboursments for project travels must be claimed within 3 weeks after the end of the travel.

The technical management of the project will also be based on the hierarchical structure PM - WAM - WPM. However, the PM will also have direct contact with all members of the Project Team, and thus keep informed about technical solutions chosen, and participate in the discussions leading to choices of technical solutions.

Start and completion dates

This work package will run from the start to the end of the project (from month 0 to month 30).

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 1101:	Partners: BRODD, BL, DBC, DDB, JR, LIBRIS, NB, SIL, TKAY

|-------------->

Task 1102:	Partners: BRODD, BL, DBC, DDB, JR, LIBRIS, NB, SIL, TKAY

|-------------->

Task 1103:	Partners: BRODD, BL, DBC, DDB, JR, LIBRIS, NB, SIL, TKAY

|-------->

Task 1104:	Partners: BRODD, BL, DBC, DDB, JR, LIBRIS, NB, SIL, TKAY

|-------------->

Task 1105:	Partners: BRODD, BL, DBC, DDB, JR, LIBRIS, NB, SIL, TKAY

|--------------------->

Task 1111:	Partners: BRODD

|-------------->

Task 1112:	Partners: BRODD

|-------------->

Task 1113:	Partners: BRODD

|--------->

Task 1114:	Partners: BRODD

|-------------->

Task 1115:	Partners: BRODD

|--------------------->

Task 1121:	Partners: BRODD

|-------------->

Task 1122:	Partners: BRODD

|-------------->

Task 1123:	Partners: BRODD

|--------->

Task 1124:	Partners: BRODD

|-------------->

Task 1125:	Partners: BRODD

|--------------------->

Task 1130:	Partners: all

|--------------->

Task 1141:	Partners: all

|-------------->

Task 1142:	Partners: all

|-------------->

Task 1143:	Partners: all

|--------->

Task 1144:	Partners: all

|-------------->

Task 1145:	Partners: all

|---------------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

---------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.1 WP 1100 Time table and deliverables

5.1.1.1 Task 1101 to 1105. Project management and administration

Objectives

The objectives of these tasks are:

-	coordinate WP 1100

-	organising the information flow

-	keeping contact with project managers of work areas, work packages and CEC project officer

-	maintaining the project schedule

-	writing bi-monthly management reports

-	organising and chairing project management group meetings

The objective is also to prepare for and participate in the Project Management group meetings.

Approach

The work will consist of the day-to-day work of the ONE project manager. For all partners it consists of preparing for and participating in the project management group meetings.

Microsoft Project v. 3.0 will be used to supervise the progress of the project and the use of resources .

Deliverables

1100/A	Project Plan and Project Guideline

1100/B	Bi-monthly management reports

1100/C	Management review

5.1.1.2 Task 1111 to 1115 Work Area management

Objectives

The objective of these tasks is to coordinate and manage the Working Area.

Approach

The WPs in this Working Area are Management WPs of the other Working Areas. The Work Area Managers (WAM) will coordinate the work in the different Work Areas. If delays are suspected in a WP, the WAMs are informed in order to take precautions for other, dependant WPs, or if possible, can prevent the delay.

The WAMs will also jointly supervise the budget.

Deliverables

Progress reports according to the project reporting procedures.

5.1.1.3 Tasks 1121 to 1125. Writing progress reports and edited reports

Objectives

A progress report will be written at the conclusion of each phase. Two edited reports will be made, the first after Phase 2 and the second after Phase 4. For the content and structure of the reports see chapter 12.1.

Approach

The progress reports will be written and discussed at the 2nd, 3rd, 4th, 5th and 6th project management group meeting. A draft of the progress report will be ready before the project management group meeting.

Deliverables

1121:	Progress report (1)	(month 6)

1122/A:	Progress report (2)	(month 12)

1123:	Progress report (3)	(month 16)

1124/A:	Progress report (4)	(month 22)

1125:	Progress report (5)	(month 30)

1122/B:	Edited report (1)	(month 14)

1124/B:	Edited report (2)	(month 21)

5.1.1.4 Task 1130. Writing the final report

Objectives

The objective is to write the ONE final report and an Edited final report.

Approach

The ONE final report will be written by the project management group, with the project manager as editor, during the last month of the ONE project.

The edited report will be written by the project manager.

Deliverables

1130/A:	Final report	(month 30)

1130/B:	Edited final report	(month 30)

5.1.1.5 Task 1141 to 1145. Project meetings

Objectives

The objective of these tasks is to ensure that all partners have the opportunity to participate in the description of requirements and specifications.

The objective is further to ensure that all partners have the possibility to partake in decisions in the project.

Approach

The Project Management Group will have one-day meetings at the start of the project and close to the end of each phase.

The Project Team will have plenary meetings at the start of the project and close to the end of each phase. In addition one plenary meeting will be held in the middle of phase 2.

In addition to the plenary meetings, some sub-groups will need meetings. Some of these will be held in connection with the plenary meetings, but some will be held between plenary meetings in order to have the progression needed for the project.

Deliverables

1141/A	Minutes from PMG, 1.meeting

1141/B	Minutes from PMG, 2.meeting

1141/C	Minutes from PT, 1. pleanary meeting

1141/D	Minutes from PT, 2. plenary meeting

1142/A	Minutes from PMG, 3. meeting

1142/B	Minutes from PT, 3. pleanary meeting

1142/C	Minutes from PT, 4. plenary meeting

1143/A	Minutes from PMG, 4. meeting

1143/B	Minutes from PT, 5. pleanary meeting

1144/A	Minutes from PMG, 5. meeting

1144/B	Minutes from PT, 6. pleanary meeting

1145/A	Minutes from PMG, 6. meeting

1145/B	Minutes from PT, 7. pleanary meeting

5.1.2 WP1200	"Use and usability" working area management and administration

Name and number of Work Package

The name of Work Package 1200 is: "Use and usability" working area management and administration

Working Area

This WP is 1 of 5 in Work Area Management and Quality Assurance.

Partner

Responsible for the WP: BL

Other partners that will participate in this WP:

BIBSYS, BL, DBC, DDB, JR, LB, LIBRIS, LMJ, NM, Pica, TKAY, UBO

Objectives

The objective of this WP is to manage the Working Area Use and Usability. This Working Area consists of 9 Work Packages, each with a coordinator.

The Tasks in this WP are:

Task 1201 to 1205:	Working Area management and administration - Phase 1 to Phase 5

Task 1210:	Negotiations on service contracts

Prerequisits

The results of WP 2200 is a prerequisite for Task 1210.

For the full overview of task dependancies, see Appendix II.

Approach

The management of the 15 Work Packages within this Work Area will be undertaken by regular contact between the four Work Area Managers and the Project Manager on the one hand and between the Work Area Manager and the Work Package Co-ordinators. The Work Area Manager will consult with the Work Package Co-ordinators on the individual Work Package plans, and will receive regular progress and exception reports from the Co-ordinators.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 1201:	Partners: BL

|---------------->

Task 1202:	Partners: BL

|---------------->

Task 1203:	Partners: BL

|---------->

Task 1204:	Partners: BL

|---------------->

Task 1205:	Partners: BL

|--------------------->

Task 1210:	Partners: BL, BIBSYS, DBC, DDB, JR, LB, LIBRIS, LMJ, NM, Pica, TKAY, UBO

|---------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

---------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.2 WP 1200 Time table and deliverables

5.1.2.1 Tasks 1201 to 1205	Working area management and administration

Objectives

The objective of these tasks is to coordinate and manage the WPs in this Working Area. It is to ensure the optimal use of resources, that deadlines are met and that the results meet the quality requirements.

Approach

Each WP and work in each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. WP progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.1.2.2	Task 1210	Negotiations on service contracts

Objectives

The objective of this task is to identify which databases/systems at each partner institution that will be offered as server systems, and negotiate conditions for users at partner institutions to connect to these in the Trial Service period.

Conditions for use of the services after the Trial Service must be negotiated outside this project.

Approach

A standard service agreement will be drawn up to which will be appended schedules for individual ONE partners. The individual schedules will take into account any particular requirements such as charging mechanism and costs of the various partners.

The Partners will meet and negotiate project service contracts in order to minimalise the cost of using the server systems in the trial service.

Deliverables

1210/A	Service agreements with signed schedules for each partner.

1210/B	Short report describing the various service terms and conditions agreed upon

5.1.3 WP1300	"Software development" working area management and administration

Name and number of Work Package

The name of Work Package 1300 is:"Software development" working area management and administration

Working Area

This WP is 1 of 5 in Work Area Management and quality Assurance.

Partner

Responsible for the WP: SIL

Objectives

The objective for this WP is to perform overall co-ordination of milestones involving the development of software within ONE and to ensure that all software development takes place according to the time schedule.

There are 7 Work packages in this Working Area, each has a coordinator.

The WP is divided into the following tasks:

Tasks 1301 to 1305:	Working Area Management and administration, Phase 1 to Phase 5

Prerequisits

None.

Approach

Each Work Package will be carefully monitored to ensure that the objectives are met within budget and timescale. Progress of work and the use of resources will be reported according to the project reporting procedures.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 1301:	Partners: SIL

|---------------->

Task 1302:	Partners: SIL

|---------------->

Task 1303:	Partners: SIL

|---------->

Task 1304:	Partners: SIL

|-------------->

Task 1305:	Partners: SIL

|--------------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

---------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.3 WP 1300 Time table and deliverables

5.1.3.1	Tasks 1301 to 1305	Working Area Management and administration

Objectives

The objective of these tasks is to coordinate and manage the WPs in this Working Area. It is to ensure the optimal use of resources, that deadlines are met and that the results meet the quality requirements.

Approach

Each WP and work in each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. WP progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.1.4 WP1400	Dissemination and Exploitation Working Area management and administration

Name and number of Work Package

The name of Work Package 1400 is:"Dissemination" working area management and administration

Working Area

This WP is 1 of 5 in Work Area Management and Quality Aaaurance.

Partner

Responsible for the WP: NB

Objectives

The objective of this Work package is to manage the Working Area "Dissemination of information and results".

There are 5 Work Packages in this Working Area, each with a coordinator.

The tasks in this WP are the following:

Tasks 1401 to 1405:	Working Area Management and administration, Phase 1 to Phase 5

Prerequisits

None.

Approach

Each Work Package will be carefully monitored to ensure that the objectives are met within budget and timescale. Progress of work and the use of resources will be reported according to the project reporting procedures.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 1401:	Partners: NB

|---------------->

Task 1402:	Partners: NB

|---------------->

Task 1403:	Partners: NB

|---------->

Task 1404:	Partners: NB

|---------------->

Task 1405:	Partners: NB

|--------------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

--------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.4 WP 1400 Time table and deliverables

5.1.4.1	Tasks 1401 to 1405	Working Area management and administration

Objectives

The objective of these tasks is to coordinate and manage the WPs in this Working Area. It is to ensure the optimal use of resources, that deadlines are met and that the results meet the quality requirements.

Approach

Each WP and work in each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. WP progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.1.5 WP1500	Quality Assurance

Name and number of Work Package

The name of Work Package 1500 is: Quality Assurance

Working Area

This WP is 1 of 5 in Work Area Management and Quality Assurance

Partner

Responsible for the WP: BL

Objectives

The objective of this Work Package is to ensure that all products and deliverables from Project ONE meet agreed standards of quality.

The tasks in this WP are:

Task 1501 to 1505:	WP1500 management - Phase 1 to Phase 5

Task 1510:	Define methods and measures for Quality Control

Task 1521 to 1525:	Quality control - Phase 1 to Phase 5

Prerequisites:

None.

Approach:

The Quality Assurance procedures adopted for ONE will be set out in the Quality Plan which will be produced from Work Package 1510.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 1501:	Partners: BL

|---------------->

Task 1502:	Partners: BL

|---------------->

Task 1503:	Partners: BL

|---------->

Task 1504:	Partners: BL

|---------------->

Task 1505:	Partners: BL

|--------------------->

Task 1510:	Partners: BL

|---------------->

Task 1521:	Partners: BL

|---------------->

Task 1522:	Partners: BL

|---------------->

Task 1523:	Partners: BL

|---------->

Task 1524:	Partners: BL

|---------------->

Task 1525:	Partners: BL

|--------------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

---------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.5 WP 1500 Time table and deliverables

5.1.5.1 Tasks 1501 tp 1505. WP1500 management

Objectives

The objective of these tasks is to coordinate and manage the WPs in this Working Area. It is to ensure the optimal use of resources, that deadlines are met and that the results meet the quality requirements.

Approach

Each WP will be carefully monitored to ensure that the objectives are met within budget and timescale. Work progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.1.5.2	Tasks 1510 Define methods and measures for Quality Control

Objectives

The objective of this task is to define methods and to choose measures for carrying out the Quality Control function.

Approach

The methods and measures for Quality Control at BL will be used as a basis for the ONE QA measures.

Deliverables

1510	Quality Plan

1520/x	Quality control statement for each deliverable.

5.1.5.3 Tasks 1521 to 1525. Quality control

Objectives

The objective of these tasks is to ensure the quality of all the deliverables, software and reports. The main objective is to ensure that there is correspondence between the objective of a task and the deliverables of the task.

Approach

The methods for how to measure Quality of deliverables will be defined in this WP on the basis of BL's Quality Assurance methods.

Quality Control will compare the results with the Quality Plan defined in Task 1510.

Deliverables

1520/x	Quality control statement for each deliverable.

5.2	2000	REQUIREMENTS AND SPECIFICATION

5.2.1 WP2100	SR software evaluation

Name and number of Work Package

The name of Work Package 2100 is: SR software evaluation

Working Area

This WP is 1 of 7 in Work Area Software development

Partner

Responsible for the WP: DBC

Other partners that will participate in this WP:

BIBSYS, BL, BRODD, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO.

Objectives

The objective of this Work package is to study available software packages as a basis for the development of SRPM and communication modes within ONE.

The objective is also to choose, if possible, one of the available software packages for the basis.

The tasks in this WP are the following:

Task 2100	WP2100 management

Task 2110	Definitions of evaluation forms

Task 2120	SRPM Software evaluation

Task 2130	Client Software evaluation

Task 2140	Communication stack evaluation

Task 2150	Choice of software basis for SRPM in ONE

Prerequisits

It is a prerequisite for this WP that the project team has access to source code and documentation of:

Nordic SR-Net software

NLC kernel software and CANSEARCH

ION SRPM

SOCKER SRPM

EUROPAGATE

and the other relevant packages that may be evaluated.

For the full overview of task dependancies, see Appendix II.

Approach

Each package will be analysed for its suitability with reference to normal software evaluation criteria including adaptability, portability, expandability, documentation, functionality, availability etc. to meet other services required by ONE partners.

A cross-reference will be made of all packages investigated in order to assist in determining the software basis for SRPM in ONE.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 2100:	Partners: DBC

|---------------->

Task 2110:	Partners: DBC, SIL

|--------->

Task 2120:	Partners: BIBSYS, BRODD, DBC, SIL

|--------->

Task 2130:	Partners: DBC, DDB, SIL

|--------->

Task 2140:	Partners: BIBSYS, DBC, SIL

|--------->

Task 2150:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|---->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

--------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.6 WP 2100 Time table and deliverables

5.2.1.1	Task 2100	WP2100 management

Objectives

The objective of this task is to coordinate the evaluation of the different software packages. It is to ensure that the evaluations are comparable and that they are finished on time.

Approach

Each partner will be allocated a specific package to evaluate. A list of evaluation criteria will be generated providing guidelines on how to summarise the package evaluation.

Each task will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.2.1.2	Task 2110	Definition of evaluation forms

Objective

The objective of this task is to get a unified way of evaluating the software packages.

Approach

Identifying the relevant properties of each type of software (SRPM, client etc.) such as architecture, platform, use of development tools and associated documentation. On this basis a proforma will be designed. The use of the proforma will simplyfy the work in tasks 2120, 2130 and 2140.

Deliverables

2110	Evaluation proformas

5.2.1.3	Task 2120	SRPM Software evaluation

Objectives

The objective of this task is to study and evaluate existing, free software in order to choose a basis for further development.

This task is divided into the following sub-tasks:

T2120-1	Nordic SR-Net software

T2120-2	NLC kernel software

T2120-3	ION software

T2120-4	SOCKER software

T2120-5	DBV-OSI software

T2120-6	other relevant and available packages

Approach

Each package will be evaluated according to the properties identified in task 2110. A summary of each will be generated with recommendations to the package usefulness for ONE.

Deliverables

2120	SRPM Software Evaluation

5.2.1.4	Task 2130	Client Software evaluation

Objectives

The objective of this task is to evaluate existing client software as a basis for the ONE client software.

This task will be divided into the following sub-tasks:

T2130-1	Can-Search

T2130-2	SOCKER

T2130-3	Choice of other available, relevant client packages

Approach

Each package will be evaluated according to the properties identified in task 2110. A summary of each will be generated with recommendations to the package usefulness for ONE.

Deliverables

2130	Stand-alone Client Software Evaluation

5.2.1.5	Task 2140	Communication stack evaluation

Objectives

The objective of this task is to evaluate different software for use of different communication stacks.

This task will be divided into the following sub-tasks:

T2140-1	EUROPAGATE software

T2140-2	Nordic SR-Net software

T2140-3	mOSI

T2140-4	TOSI

T2140-5	DBV-OSI II software

Approach

Each package will be evaluated according to the properties identified in task 2110. A summary of each will be generated with recommendations to the package usefulness for ONE.

Deliverables

2140	Communication Stack Software Evaluation

5.2.1.6	Task 2150	Choice of software basis for SRPM in ONE

Objectives

The objective of this task is to compare the evaluated software packages and to choose one for the basis of the common ONE software.

This task will be divided into the following sub-tasks:

T2150-1	Choice for SRPM basis

T2150-2	Choice for communication stack software

T2150-3	Choice for client software

Approach

The evaluation summaries will be combined to a single document. The summary information will be analysed with respect to the usefulness for the ONE partner systems and the NEP. A conclusions section will be added to the document.

Deliverables

2150	Choices of software packages.

5.2.2 WP2200	Specification of services to be offered

Name and number of Work Package

The name of Work Package 2200 is: Specification of services to be offered

Working Area

This WP is 1 of 9 in Work Area Use and Usability

Partner

Responsible for the WP: DBC

Other partners that will participate in this WP:

BIBSYS, BL, DDB, JR, LIBRIS, Pica, TKAY, UBO

Objectives

The objective of this WP is to make a list of services offered from each of the participating systems, both at present and plans for the project.

The WP is divided into the following tasks:

Task 2200	WP2200 Management

Task 2210	Services in partners' systems

Prerequisits

Each partner institution must have a plan for which services to be offered through the network and how.

Approach

The WP coordinator prepares a proforma for describing the services. Each Partner fills inn the form for own system. The WP coordinator compiles the total list.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 2200:	Partners: DBC

|---------------->

Task 2210:	Partners: BIBSYS, BL, DBC, DDB, JR, LIBRIS, Pica, TKAY, UBO

|---------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

---------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.7 WP 2200 Time table and deliverables

5.2.2.1	Task 2200	WP2200 Management

Objectives

The objectives of this task are:

-	to design a uniform way of describing the services in a system

-	to ensure that the service descriptions are made

-	to coordinate the descriptions of the services in partners systems

The outputs of this WP are invaluable documents for the testing phases in verifying the operation for each local system.

Approach

Each task will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

2200/A	Proforma for describing the services offered in a system.

Progress reports according to the project reporting procedures.

5.2.2.2	Task 2210	Services in partners' systems

Objectives

Each of the partners whose databases/systems will be a server, will describe the services they intend to offer in the network for each of the databases/systems, and on which conditions the databases/systems will be available.

This task is divided into the following sub-tasks:

T2210-1	Services in BIBSYS

T2210-2	Services in BL

T2210-3	Services in DBC

T2210-4	Services in DDB

T2210-5	Services in LIBRIS

T2210-6	Services in Pica

T2210-7	Services in TKAY

T2210-8	Services in UBO

Approach

Generate a proforma subsection for each SR protocol service. Use a copy of this for each host and enter the details about the host services currently offered or to be planned.

Deliverables

2210	Service descriptions for the participating systems

5.2.3 WP2300	SRPM requirements and specifications

Name and number of Work Package

The name of Work Package 2300 is: SR Protocol Machine requirements and specifications

Working Area

This WP is 1 of 9 in Work Area Use and Usability

Partner

Responsible for the WP: BRODD

Other partners that will participate in this WP:

BIBSYS, BL, DBC, JR, LIBRIS, Pica, SIL, TKAY, UBO.

Objectives

The objective of this WP is to define the overall requirements for the common SR Protocol Machine, structure, functionality and platform(s).

The objective of this WP is also to make specifications for the common Protocol Machine, both target and origin. The specifications will be made in two steps:

First the specifications for version 1 of the software,

the first specifications will be enhanced for version 2 of the software.

The second specification will be enhanced to include the whole SR-standard with amendments.

The objective of this WP is to specify the local SRPM enhancements if the common software is not to be used. The objective is also to specify the necessary changes in the local systems in order to communicate with other systems in ONE.

The last objective of this WP is to specify the communication stacks to be used both for version 1 and version 2 of the systems.

The WP is divided into the following tasks:

Task 2301 to 2303:	WP2300 management, Phase 1 to Phase 3

Task 2310:	Common SRPM Requirements

Task 2321:	Common SRPM Specifications, Version 1

Task 2322:	Common SRPM Specifications, Version 2

Task 2330:	Local system SR specification

Task 2341:	Specification of communication stacks, version 1

Task 2342:	Specification of communication stacks, version 2

Prerequisits

The ISO SR-1995 and the evaluated software packages for SRPM including the decision of which package to use as basis for the development.

SRPM specifications from Nordic SR-Net, SOCKER and ION projects and the results from WP 2100.

For the full overview of task dependancies, see Appendix II.

Approach

Each Task participant will investigate SRPM specifications from Task Inputs and ascertain specific functional requirements for their respective Origin and Target systems.

A Functional Requirements Document will be generated that formally identify the requirements.

A Software Requirements Document will be generated including formally identifiable requirements and a cross-reference to respective functional requirements that they satisfy.

Each Task participant will investigate SRPM specifications from Task Inputs and ascertain specific software requirements for their respective Origin and Target systems and the communications stacks utilised.

The properties of the available software for communication stacks will be compared with the stack requirements. As far as possible available software for the communication stacks will be used.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 2301:	Partners: BRODD

|---------------->

Task 2302:	Partners: BRODD

|---------------->

Task 2303:	Partners: BRODD

|---------->

Task 2310:	Partners: BIBSYS, BL, BRODD, DBC, JR, LIBRIS, Pica, SIL, TKAY, UBO

|---->

Task 2321:	Partners: BIBSYS, BL, BRODD, DBC, JR, LIBRIS, SIL, TKAY, UBO

|---->

Task 2322:	Partners: BIBSYS, BL, BRODD, DBC, JR, LIBRIS, Pica, SIL, TKAY, UBO

|---------->

Task 2330:	Partners: BIBSYS, BL, DBC, JR, LIBRIS, Pica, TKAY, UBO

|----------------->

Task 2341:	Partners: BIBSYS, DBC, SIL

|---->

Task 2342:	Partners: BIBSYS, DBC, SIL

|---------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

---------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.8 WP 2300 Time table and deliverables

5.2.3.1	Task 2301 to T2303	WP2300 management

Objectives

This logical task lasts for three phases and is therefore divided into three concrete tasks. The objective of each one is to ensure that the work in the Work Package is carried out according to plan.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.2.3.2	Task 2310	Common SRPM Requirements

Objectives

The objective of this task is to define the requirements for the SRPM whether this is going to be connected to the NEP or to any of the local systems.

This task will be divided into the following sub-tasks:

T2310-1	Requirements for target part of SRPM

T2310-2	Requirements for origin part of SRPM

Approach

A generic SRPM will be defined for both target and origin with particular atention to the connectivity for the user at the origin and host at the target. Requirements will be focussed to the use of the API and Toolbox and to adaptability to different computer platforms. A Requirements document will be produced.

Deliverables

2310	Common SRPM Requirements

5.2.3.3	Task 2321 and T2322	Common SRPM specifications

Objectives

The objective of these tasks is to make specifications for the SRPM, version 1 and version 2.

Task 2321 and 2322 will be divided into the following sub-tasks:

T232x-1	Specification for target part of SRPM

T232x-2	Specification for origin part of SRPM

Approach

The Requirements document will be used as input and the SRPM specifications generated. A SRPM specifications document will be produced.

Deliverables

2321	Common SRPM specifications, version 1

2322	Common SRPM specifications, version 2

5.2.3.4	Task 2330	Local system SR specification

Objectives

The objective of this task is to ensure that each of the planned server systems specify their SRPM in time for the other developments.

This task will be divided into the following sub-tasks:

T2330-1	Specifications of BIBSYS

T2330-2	Specifications of BL

T2330-3	Specifications of DBC

T2330-4	Specifications of DDB

T2330-5	Specifications of LIBRIS

T2330-6	Specifications of Pica

T2330-7	Specifications of TKAY

T2330-8	Specifications of UBO

Approach

Each local system will be analysed with respect to its SRPM requirements and the SRPM specifications for the local system generated.

Deliverables

2330	Report on results of the SRPM specification for each local system.

5.2.3.5	Task 2341 and 2342 Specification of communication stacks

Objective

The objective of this task is to define the communication stack(s) to be used by version 1 and version 2 of the systems.

The objective is further to describe and document the communication stack(s) to be used for each version of the systems.

Approach

For each local system, the communications stack(s) will be identified.

A specifications document will be generated identifying each project target with its network details including addresses, ports etc.

Deliverables

2341	Communication stacks for version 1

2342	Communication stacks for version 2

5.2.4 WP2400	EXPLAIN requirements and specifications

Name and number of Work Package

The name of Work Package 2400 is:EXPLAIN requirements

Working Area

This WP is 1 of 9 in Work Area Use and Usability

Partner

Responsible for the WP: JR

Other partners that will participate in this WP:

BIBSYS, BL, BRODD, DBC, DDB, LIBRIS, NB, Pica, SIL, TKAY, UBO.

Objectives

The objective of this WP is to define the requirements for an EXPLAIN protocol service, both for the target and for the origin.

EXPLAIN uses the regular Search Protocol service searching an "EXPLAIN database". A special attribute set for searching this database is being defined.

The objective of this WP is to make clear specifications for the coding of the EXPLAIN protocol service, both in the target and in the origin.

The WP is divided into the following tasks:

Task 2401 and 2402:	WP2400 management, Phase 2 and Phase 3

Task 2410	General EXPLAIN requirements

Task 2420	General EXPLAIN specifications

Prerequisits

Results from WP6100 User Interface

For the full overview of task dependancies, see Appendix II.

Approach

The protocol service EXPLAIN will be analysed and mapped to the requirements of the local host EXPLAIN databases. The specifications for each system will be written to a specifications document.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

_________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 2401:	Partners: JR

|---------------->

Task 2402:	Partners: JR

|---------->

Task 2410:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, Pica, SIL, TKAY, UBO

|---------->

Task 2420:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|---------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

--------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.9 WP 2400 Time table and deliverables

5.2.4.1	Task 2401 and T2402	WP2400 management

Objectives

The objective of these tasks is to coordinate and manage the tasks in this WP. It is further to ensure that the work is carried out according to the project plan.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.2.4.2	Task 2410	General EXPLAIN requirements

Objectives

The objective of this task is to define the requirements for a general EXPLAIN protocol service based on the HELP/EXPLAIN facilities in the partners' systems.

This task will be divided into the following sub-tasks:

T2410-1 EXPLAIN requirements for target

T2410-2 EXPLAIN requirements for origin

Approach

Each Task participant will investigate EXPLAIN requirements from Task Inputs and ascertain specific software requirements for their respective SR systems and databases.

A Functional Requirements Document will be generated including requirements as being formally identifiable.

Each system will be specifically referenced under separate sections.

Deliverables

2410	General EXPLAIN requirements

5.2.4.3	Task 2420	General EXPLAIN specifications

Objectives

The objective of this task is to specify the general EXPLAIN protocol service based on the requirements made in Task 2410.

This task will be divided into the following sub-tasks:

T2420-1 EXPLAIN specifications for target

T2420-2 EXPLAIN specifications for origin

Approach

For each task, appropriate elements of the EXPLAIN protocol service will be analysed and specific specifications will be devised. Each local system will be taken and its EXPLAIN protocol service will be characterised. A specifications document will be written.

Deliverables

2420	General EXPLAIN specifications

5.2.5 WP2500	API and Toolbox

Name and number of Work Package

The name of Work Package 2500 is: API and Toolbox

Working Area

This WP is 1 of 9 in Work Area Use and Usability

Partner

Responsible for the WP: BRODD

Other partners that will participate in this WP:

BIBSYS, BL, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

Objectives

API

The objective of this WP is to specify the interface between the local library system and the SRPM (API) in order to transfer necessary information between the local library system and the SRPM. Specific points to address will be support for different platforms, (e.g. PC and UNIX).

A detailed design document will be generated formally defining each API function and its parameters and data.

An appendix will have a reference of API functions against specific software requirements.

This work may be divided into an SR Origin API and an SR Target API.

TOOLBOX

The objective of this WP is also to make Toolbox (a set of procedures for MARC conversions, character conversions etc.) that may also contain an interface between the local library system and the API-SRPM package.

The structure of these modules is as follows:

Library System

|

----------------------------------------

Origin | Target

----------------------------------------

Toolbox

----------------------------------------

API

----------------------------------------

SRPM

==============================================

OSI upper layers	| TCP/IP

------------------------------------

OSI lower layers | TCP/IP

The Toolbox will be a set of procedures the local system developer can use in order to connect the local system in an easy way to the network, and to perform different types of conversions. The Toolbox may among other facilities, hide the details of the actual application protocol.

In communication between systems in a network, there is a need to convert between different formats. One type of such conversion is between two MARC formats. The Toolbox will therefore contain a general module for such conversion.

There is also a need to convert between different character sets. A system usually uses a "local" set of characters in its database and in its user interface. Conversion from one character set into another is therefore useful when receiving bibliographic records.

Many European countries have special characters in their language. These characters are transcribed differently in different systems (and countries). In order to improve a search result, the search request ougth to be sent in ISO 10646 (or UNICODE). The Target may then use its own transcription rules before the search is performed.

When character set negotiation is included in the SR/Z39.50 protocol, this character conversion module will be needed. Therefore it will be part of the Toolbox.

Many systems use CCL (ISO 8777) as the local user dialogue. The SR/Z39.50 has Reverse Polish Notation (RPN) as mandatory. Thus the "CCL-systems" must be able to convert between CCL and RPN. This is a facility that should be offered in the Toolbox.

The above mentioned examples are only some of many facilities that could be included in a Toolbox.

The WP is divided into the following tasks:

Task 2501 to T2502:	WP2500 management

Task 2510	API specification

Task 2520	Toolbox requirements

Task 2530	Toolbox specifications

Prerequisits

Documentation of APIs from Nordic SR-Net, SOCKER and ION.

Documentation of Toolbox from Nordic SR-Net;

For the full overview of task dependancies, see Appendix II.

Approach

API functions will be defined and functions distinguished between High level and Lower level areas. Specific points to address will be support for different platforms, (ie PC, UNIX, The stacks etc).

A detailed design document will be generated formally defining each API function and its parameters and data.

An appendix will have a reference of API functions against specific software requirements.

The requirements for the content of a Toolbox will be identified. The Toolbox will be a set of separate modules. All partners will participate in defining requirements and specifications for the Toolbox. Then the time schedule for the development for each module will be decided.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 2501:	Partners: BRODD

|---------------->

Task 2502:	Partners: BRODD

|---------------->

Task 2510:	Partners: BIBSYS, BL, BRODD, DBC, DDB, LIBRIS, Pica, SIL, TKAY, UBO

|---------------->

Task 2520:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|---------------->

Task 2530:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|----------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

---------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.10 WP 2500 Time table and deliverables

5.2.5.1	Task 2501 and T2502	WP2500 management

Objectives

The objective of these tasks is to coordinate and manage the tasks in this WP. It is further to ensure that the work is carried out according to the project plan.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.2.5.2	Task 2510	API specification

Objectives

The objective of this task is to specify API for the complete SR/Z39.50 protocol (SR-1995). The task will be divided into the following sub-tasks:

T2510-1	Specification for API target

T2510-2	Specification for API origin

Approach

For each task, the appropriate SRPM specifications will be identified and mapped to API functions relating to the protocol model.

Input and Output parameters will be defined and the API document will be written.

Deliverables

2510	API specification

5.2.5.3	Task 2520	Toolbox requirements

Objectives

The objective of this task is to define the requirements for a Toolbox. These requirements will include the different tools included in the Toolbox as well as the interface to it.

Approach

For each task, appropriate toolbox functions will be identified relating to origin and target systems. The requirements of the toolbox functions and how the toolbox is integrated into the origin and target programs will be defined. A functional requriements document will be generated.

Deliverables

2520	Toolbox requirements

5.2.5.4	Task 2530	Toolbox specifications

Objectives

The objective of this task is to decide which modules should be included in the Toolbox, and to describe the specifications for these modules in the Toolbox.

Approach

The toolbox functional requriements document will be used as input and specifications for each toolbox function will be generated. Details such as function parameters, data validity will be generated together with examples for each function. A specification document will be written.

Deliverables

2530	Toolbox specifications

5.2.6 WP2600	NEP Requirement and Specification

Name and number of Work Package

The name of Work Package 2600 is: Neutral Entry Point (NEP) Requirement and Specification

Working Area

This WP is 1 of 9 in Work Area Use and Usability

Partner

Responsible for the WP: DBC

Other partners that will participate in this WP:

BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, SIL, TKAY and UBO will participate in defining the requirements.

Objectives

The objective of this work package is to identify the requirements for a Neutral Entry Point (NEP) to the systems in the network. Such a NEP may be called by a local system or by a stand- alone system. In both cases it will only work as an SR Origin.

The WP is divided into the following tasks:

Task 2600 WP2600 management

Task 2610 NEP Requirements

Task 2620 NEP Specifications

Prerequisits

Results from WP 2100 SR software evaluation.

For the full overview of task dependancies, see Appendix II.

Approach

The results of investigations of other client packages will be used in order to generate a NEP Functional Requirements document. This will include aspects such as platform and communication stacks to be supported.

Specific attention will be paid to the connectivity to local systems and the use of the designed ONE API and Toolbox and also to the portability to different computer platforms.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 2600:	Partners: DBC

|--------------->

Task 2610:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, SIL, TKAY, UBO

|------->

Task 2620:	Partners: DBC

|------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

--------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.11 WP 2600 Time table and deliverables

5.2.6.1	Task 2600 WP2600 management

Objectives

The objective of this task is to coordinate and manage the tasks in this WP.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.2.6.2	Task 2610 NEP Requirements

Objectives

The objective of this task is to define the requirements for the NEP.

Approach

The requirements will be defined on the basis of the evaluated software packages (see 5.2.1), the experience of the partners and an analysis of the needed functionality for a NEP.

The local systems will be analysed with respect to connectivity specifications and the ONE API and Toolbox specifications. Requirements of the NEP interface will be generated in terms of adaptability and portability to different computer platforms. A requirements document will be generated.

Deliverables

2610	Requirements for NEP

5.2.6.3	Task 2620 NEP Specifications

Objectives

The objective of this task is to describe the specifications for the NEP based on the defined requirements.

Approach

The NEP requriements will be used as input and the design specifications will be generated. The design will account for portability and use for local systems. A specifications document will be written showing cross reference of specifications to requirements.

Deliverables

2620	Specifications for NEP

5.2.7 WP2700	Stand-alone client requirements and specification

Name and number of Work Package

The name of Work Package 2700 is: Stand-alone client Requirement and Specification

Working Area

This WP is 1 of 9 in Work Area Use and Usability

Partner

Responsible for the WP: SIL

Other partners that will participate in this WP:

All partners except Pica will participate in this WP.

Objectives

The objective of this work package is to identify the requirements for a stand-alone client to the systems in the network. Such a client will use the NEP (see 5.2.6) for SR-protocol services and network connection.

The WP is divided into the following tasks:

Task 2700 WP2700 management

Task 2710 Stand-alone client requirements

Task 2720 Stand-alone client specifications

Prerequisits

Results from WP 2100 SR software evaluation.

For the full overview of task dependancies, see Appendix II.

Approach

The results of investigations of other client packages will be used in order to generate a Stand- Alone Client Functional Requirements document. This will include aspects such as platform and communication stacks to be supported.

Specific attention will be paid to the connectivity to local systems and the use of the designed ONE API.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 2700:	Partners: SIL

|---------------->

Task 2710:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LB, LIBRIS, LMJ, NB, NM, SIL, TKAY, UBO

|------->

Task 2720:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LB, LIBRIS, LMJ, NB, NM, SIL, TKAY, UBO

|--------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

---------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.12 WP 2700 Time table and deliverables

5.2.7.1	Task 2700 WP2700 management

Objectives

The objective of this task is to coordinate and manage the tasks in this WP.

Approach

Each task will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.2.7.2	Task 2710 Stand-alone client Requirements

Objectives

The objective of this task is to define the requirements for the Stand-alone client.

Approach

Requirements of the Stand-alone client user interface will be generated in terms of adaptability to different user needs.

Requirements of the Stand-alone client concerning adaptability and portability to different computer platforms will be defined.

A combined requirements document will be generated.

Deliverables

2710	Requirements for a stand-alone client

5.2.7.3	Task 2720 Stand-alone client Specifications

Objectives

The objective of this task is to describe the specifications for the Stand-alone client based on the defined requirements.

Approach

The Stand-alone client requriements will be used as input and the design specifications will be generated. The design will account for portability and user needs. A specifications document will be written showing cross reference of specifications to requirements.

Deliverables

2720	Specifications for the stand-alone client

5.3	3000	DESIGN OF SOFTWARE

5.3.1 WP3100	Design of SRPM

Name and number of Work Package

The name of Work Package 3100 is: Design of SRPM, version 1

Working Area

This WP is 1 of 7 in Work Area Software development

Partner

Responsible for the WP: SIL

Other partners that will participate in this WP:

BIBSYS, BL, DBC, DDB, JR, LIBRIS, Pica, TKAY, UBO

Objectives

The objective of this WP is to design the code for both versions of SRPM. This WP will optimise the actual coding.

The WP is divided into the following tasks:

Task 3101 and 3102:	WP3100 management, Phase 2 and Phase 3

Task 3110	Common SRPM version 1 design

Task 3120	Common SRPM version 2 design

Task 3130	Local system SR-design, version 1

Task 3140	Local system SR-design, version 2

Task 3150	NEP design, version 1

Task 3160	NEP design, version 2

Task 3171 to 3172	Communication stack design and installation

Prerequisits

Results from WP2300 SRPM Specifications.

Results from WP2600 NEP requirements and specifications

For the full overview of task dependancies, see Appendix II.

Approach

A logical model of the design will begenerated on the basis of the specifications. This structure will be refined using a top down approach.

The SRPM software requirements document will be analysed and the SRPM designed in a top-down approach utilising a suitable design methodology.

SRPM Architectural Design Documentation will be generated including formally identifiable requirements and a cross-reference to respective software requirements that they satisfy.

The NEP software requirements document will be analysed and the NEP designed in a top-down approach utilising a suitable design methodology.

A NEP Architectural Design Document will be generated including formally identifiable requirements and a cross-reference to respective software requirements that they satisfy.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 3101:	Partners: SIL

|---------------->

Task 3102:	Partners: SIL

|---------->

Task 3110:	Partners: SIL

|---->

Task 3120:	Partners: SIL

|---->

Task 3130:	Partners: BIBSYS, BL, DBC, DDB, LIBRIS, Pica, TKAY, UBO

|---->

Task 3140:	Partners: BIBSYS, BL, DBC, DDB, LIBRIS, Pica, TKAY, UBO

|---------->

Task 3150:	Partners: DBC

|-->

Task 3160:	Partners: DBC

|---------->

Task 3171:	Partners: BIBSYS, BL, DBC, JR, LIBRIS, Pica, SIL, TKAY, UBO

|---->

Task 3172:	Partners: BIBSYS, BL, DBC, JR, LIBRIS, Pica, SIL, TKAY, UBO

|---->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

-------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.13 WP 3100 Time table and deliverables

5.3.1.1	Task 3101 to T3103	WP3100 management

Objectives

The objective of these tasks is to coordinate and manage the tasks in this WP. It is further to ensure that the work is carried out according to the project plan.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Project Reports in accordance with the designated project reporting procedures

5.3.1.2	Task 3110	Common SRPM version 1 design

Objectives

The objective of this task is to design the code (programme structure) for the first version of the common SRPM.

This task will be divided into the following sub-tasks:

T3110-1 design of target

T3110-2 design of origin

Approach

The SRPM will be designed using a suitable methodology. The design will be decomposed to a module level which can be passed to programmers. The design will be done according to the specifications and requirements documents previously produced.

Deliverables

3110	Design documentation for Common SRPM, version 1

5.3.1.3	Task 3120	Common SRPM version 2 design

Objectives

The objective of this task is to design the code (programme structure) for the final version of the common SRPM.

This task will be divided into the following sub-tasks:

T3120-1 design of target

T3120-2 design of origin

Approach

The SRPM design will be enhanced to incorporate the Phase 2 protocol services to be supported. The design will be decomposed to a module level which can be passed to programmers. The design will be to the specifications and requirements documents previously produced.

This design will be made while version 1 is tested by users. Thus some of the test results will influence the specifications and design of version 2.

Deliverables

3120	Common SRPM version 2 design

5.3.1.4	Task 3130	Local system SR-design, version 1

Objectives

The objective of this task is to design the first ONE-version of each local system.

This task will be divided into the following sub-tasks:

T3130-1	SR design for BIBSYS, version 1

T3130-2	SR design for BL, version 1

T3130-3	SR design for DBC, version 1

T3130-4	SR design for DDB, version 1

T3130-5	SR design for LIBRIS, version 1

T3130-6	SR design for Pica, version 1

T3130-7	SR design for TKAY, version 1

T3130-8	SR design for UBO, version 1

Approach

Each local system will be designed to the version 1 specifications. A suitable design methodology will be used for each system. The design will be decomposed to a modular level which can be handed to programmers for coding.

Deliverables

3130	Design documentation for the local systems, version 1

5.3.1.5	Task 3140	Local system SR-design, version 2

Objectives

The objective of this task is to design the second ONE-version of each local system.

This task will be divided into the following sub-tasks:

T3140-1	SR design for BIBSYS, version 2

T3140-2	SR design for BL, version 2

T3140-3	SR design for DBC, version 2

T3140-4	SR design for DDB, version 2

T3140-5	SR design for LIBRIS, version 2

T3140-6	SR design for Pica, version 2

T3140-7	SR design for TKAY, version 2

T3140-8	SR design for UBO, version 2

Approach

Each local system design will be enhanced to incorporate the Phase 2 protocol services to be supported. The design will be decomposed to a module level which can be passed to programmers. The design will be to the specifications and requirements documents previously produced.

Deliverables

3140	Design documentation for the local systems pertaining to Version 2 enhancements.

5.3.1.6	Task 3150	NEP design, version 1

Objectives

The objective of this WP is to design the code for the Neutral Entry Point, version 1 according to the specifications described in Task 2620.

Approach

The NEP specifications will be used as input and a general design structure generated using a suitable methodology. This structure will be refined using a top down approach.

Deliverables

3150	Design documentation for NEP, version 1

5.3.1.7	Task 3160	NEP design, version 2

Objectives

The objective of this WP is to design the code for the Neutral Entry Point, version 2.

Approach

The NEP version 2 specifications will be used as input and the design generated by enhancing the design of version 1. The design wil be decomposed to module level with suitable specifications for programmers to code (top down procedure).

Deliverables

3160	Design documentation for NEP, version 2

5.3.1.8	Task 3171 to 3172	Stack design and installation

Objective

The objective of these tasks is to design and install the communication stacks for each system.

Approach

Available software will be used, possibly adjusted.

The communication stack will be designed in such a way that a change in the carrier network anywhere will not influence the interoperability between the systems.

Deliverables

3170 Communication stack description

5.3.2 WP3200	Stand-alone client, Generic user assistance and EXPLAIN design

Name and number of Work Package

The name of Work Package 3200 is: Stand-alone client, Generic user assistance and EXPLAIN design.

Working Area

This WP is 1 of 7 in Work Area Software development

Partner

Responsible for the WP: JR

Other partners that will participate in this WP:

BIBSYS, BL, DBC, DDB, LIBRIS, Pica, SIL, TKAY, UBO

Objectives

The objective of this WP is to design a Stand-alone client, a Generic user assistance, and to design the code for the EXPLAIN protocol service, both target and origin, both NEP and all local systems.

The WP is divided into the following tasks:

Task 3201 and 3202:	WP3200 management, Phase 3 and Phase 4

Task 3210	Design of Stand-alone client

Task 3221 and 3222:	Design of EXPLAIN in NEP, Phase 3 and Phase 4

Task 3231 and 3232:	Design of EXPLAIN in local systems, Phase 3 and Phase 4

Task 3240	Generic user assistance design

Prerequisits

Results from WP 2400 EXPLAIN Requirements and Specifications which are dependant on the results from WP 6100.

For the full overview of task dependancies, see Appendix II.

Approach

The Requirements and specifications for the Stand-alone client, the Generic user assistance, and the EXPLAIN will be analysed and the design for each task will be undertaken as described in each subsection.

The design of EXPLAIN in the different systems will span two phases. The partners will decide in the specifications for the EXPLAIN service (WP 2400) which functions will be designed in phase 3 and which in phase 4.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

___________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 3201:	Partners: JR

|---------->

Task 3202:	Partners: JR

|---------------->

Task 3210:	Partners: JR, SIL

|---------->

Task 3221:	Partners: DBC, SIL

|---------->

Task 3222:	Partners: DBC, SIL

|---------------->

Task 3231:	Partners: BIBSYS, BL, DBC, DDB, LIBRIS, Pica, TKAY, UBO

|---------->

Task 3232:	Partners: BIBSYS, BL, DBC, DDB, LIBRIS, Pica, TKAY, UBO

|---------------->

Task 3240:	Partners: JR, SIL

|---------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

--------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.14 WP 3200 Time table and deliverables

5.3.2.1	Task 3201 and 3202	WP3200 management

Objective

The objective of these tasks is to coordinate and manage the tasks in the WP. It is further to ensure that the work is carried out according to the project plan.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Project reports in accordance with the designated project reporting procedures.

5.3.2.2	Task 3210	Stand-alone client design

Objective

The objective of this task is to design the code for a Stand-alone client according to the specifications given in 5.2.7.

Approach

The Stand-alone client specifications will be used as input and the design generated using a suitable methodology. The design wil be decomposed to module level with suitable specifications for programmers to code.

Deliverables

3210	Design documentation for for Stand-alone client

5.3.2.3	Task 3221 and 3222	Design of EXPLAIN in NEP

Objective

The objective of this task is to design the code (structure) of EXPLAIN used in the NEP and in the stand-alone client.

Approach

The specifications and requirements of the Explain protocol service in the NEP will be used as input for the design. The design will utilise a suitable methodology and will be decomposed to a modular level to be handed to programmers.

Deliverables

3221	Design documentation for EXPLAIN in NEP, Phase 3

3222	Design documentation for EXPLAIN in NEP, Phase 4

5.3.2.4	Task 3231 and 3232 Design of EXPLAIN in local systems

Objective

The objective of this task is to design the implementation of EXPLAIN in the local systems, both for server and origin if both roles will be supported.

This task will be divided into the following sub-tasks:

T323x-1	SR design for BIBSYS

T323x-2	SR design for BL

T323x-3	SR design for DBC

T323x-4	SR design for DDB

T323x-5	SR design for LIBRIS

T323x-6	SR design for Pica

T323x-7	SR design for TKAY

T323x-8	SR design for UBO

Approach

Each local system specifications will be used as input in order to design in the EXPLAIN protocol service to the extent supported by the local host. A suitable methodology will be used and the design decomposed to a modular level for programming.

Deliverables

3231	Design documentation for EXPLAIN in local systems, Phase 3

3232	Design documentation for EXPLAIN in local systems, Phase 4

5.2.3.5	Task 3240 Generic user assistance design

Objective

The objective of this task is to design the code for a generic user assistance module for client systems.

Approach

Specifications for Generic User assistance will be used as input for the design. Since this is a virtually endless scope of work, it should be decided at the time of design which features are required and can be implemented within the budget. Other specifications may be exploited later. A suitable design methodology will be used and the design decomposed to a modular level.

Deliverables

3240	Design documentation for Generic user assistance

5.3.3 WP3300	Design of API and Toolbox

Name and number of Work Package

The name of Work Package 3300 is: Design of API and Toolbox

Working Area

This WP is 1 of 7 in Work Area Software development

Partner

Responsible for the WP: SIL

Other partners that will participate in this WP:

BL, BRODD, DBC, Pica

Objectives

The objective of this WP is to design the code for the API and the Toolbox. The API will be designed separately for the target and for the origin.

The WP is divided into the following tasks:

Task 3301 to 3303:	WP3300 management, Phase 2 to Phase 4

Task 3310	Design of API

Task 3321 to 3323:	Design of Toolbox, Phase 2 to Phase 4

Prerequisits

Results from WP 2500 API and Toolbox.

For the full overview of task dependancies, see Appendix II.

Approach

The Requirements and Specifications of the API and the Toolbox will be analysed and the design for each task will be undertaken as described in each subsection.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 3301:	Partners: SIL

|---------------->

Task 3302:	Partners: SIL

|---------->

Task 3303:	Partners: SIL

|---------------->

Task 3310:	Partners: Pica, SIL

|-------->

Task 3321:	Partners: BL, BRODD, DBC, Pica, SIL

|---------------->

Task 3322:	Partners: BL, BRODD, DBC

|---------->

Task 3323:	Partners: BL, BRODD, DBC

|---------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

--------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.15 WP 3300 Time table and deliverables

5.3.3.1	Task 3301 to 3303	WP3300 management

Objective

The objective of these tasks is to coordinate and manage the tasks in this WP. It is further to ensure that the work is carried out according to the project plan.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.3.3.2	Task 3310	Design of API

Objective

The objective of this task is to design the code for a common API based on the specifications for API.

This task will be divided into the following sub-tasks:

T3310-1 Design of target

T3310-2 Design of origin

Approach

The requirements and Specifications of the API will be used as input and the API functions will be designed with respect to the definitions of parameters, and parameter processing. Each API function will be designed with respect to its aspects of specific identification, purpose, subordinates, interfaces, resources, dependencies and data processing. A suitable methodology wil be used where appropriate and the design will be decomposed to a modular level suitable for programmers.

Deliverables

3310 Design documentation for API

5.3.3.3	Task 3321 and 3322	Design of Toolbox

Objective

The objective of these tasks is to design the code for the modules of the Toolbox.

These tasks will be divided into the following sub-tasks:

T3320-1 Overall design for target

T3320-2 Overall design for origin

T3320-3 Design for general CCL-to-RPN module

T3320-4 Design for general RPN-to-CCL module

T3320-5 Design for MARC conversion

T3320-6 Design for character conversion module

T3320-7 Design for other modules in tool-kit

Approach

The requirements and Specifications of the Toolbox will be used as input and the Toolbox functions will be designed with respect to the definitions of parameters, and parameter processing. Each Toolbox function will be designed with respect to its aspects of specific identification, purpose, subordinates, interfaces, resources, dependencies and data processing. A suitable methodology wil be used where appropriate and the design will be decomposed to a modular level suitable for programmers.

Deliverables

3321	Design documentation for Toolbox, Phase 2 modules

3322	Design documentation for Toolbox, Phase 3 modules

3323	Design documentation for Toolbox, Phase 4 modules

5.4	IMPLEMENTATION

5.4.1 WP4100	Implementation of SRPM

Name and number of Work Package

The name of Work Package 4100 is: Implementation of SRPM

Working Area

This WP is 1 of 7 in Work Area Software development

Partner

Responsible for the WP: SIL

Other partners that will participate in this WP:

BIBSYS, BL, DBC, JR, LIBRIS, Pica, TKAY, UBO

Objectives

The objective of this WP is to implement the common SRPM.

The WP is divided into the following tasks:

Task 4101 to 4103 WP4100 management

Task 4110	Common SRPM Version 1 implementation

Task 4120	Common SRPM Version 2 implementation

Task 4130	Local system SR-implementation, Version 1

Task 4140	Local system SR-implementation, Version 2

Task 4150	NEP implementation, Version 1

Task 4160	NEP implementation, Version 2

Prerequisits

Results from WP3100 Design of SRPM

For the full overview of task dependancies, see Appendix II.

Approach

The approach to each sub task is described in the following subsections.

The programme design will be rewritten into machine compileable language code. Wherever suitable, the ANSI-C programming language will be used.

ASN.1 compilers will be used to compile the protocol units.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 4101:	Partners: SIL

|---------------->

Task 4102:	Partners: SIL

|---------->

Task 4103:	Partners: SIL

|---------------->

Task 4110:	Partners: SIL

|----------->

Task 4120:	Partners: SIL

|---------------->

Task 4130:	Partners: BIBSYS, BL, DBC, JR, LIBRIS, Pica, TKAY, UBO

|----------->

Task 4140:	Partners: BIBSYS, BL, DBC, JR, LIBRIS, Pica, TKAY, UBO

|---------------->

Task 4150:	Partners: DBC

|---------->

Task 4160:	Partners: DBC

|---------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

-------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.16 WP 4100 Time table and deliverables

5.4.1.1	Task 4101 to 4103	WP4100 management

Objective

The objective of these tasks is to coordinate the tasks in this WP in order to control the progreee of the work and the use of resources.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.4.1.2	Task 4110	Common SRPM Version 1 implementation

Objective

The objective of this task is to code the Version 1 of the common SRPM.

This task will be divided into the following sub-tasks:

T4110-1 implementation of SRPM target

T4110-2 implementation of SRPM origin

Approach

For each task, the module definitions of the SRPM will be used as input and the SRPM coded. As modules are completed they will be tested and integrated together in an appropriate manner. During integration, where necessary stub modules will be replaced for actual modules until the actual module is ready for integration. The programs will be functionally tested during the integration phase and when appropriate early versions issued for operational testing and evaluation.

Deliverables

4110	Operational code for SRPM, version 1

5.4.1.3	Task 4120	Common SRPM Version 2 implementation

Objective

The objective of this task is to implement the full SR-1995 protocol for the common SRPM.

This task will be divided into the following sub-tasks:

T4120-1 implementation of SRPM target

T4120-2 implementation of SRPM origin

Approach

The Version 1 SRPM code will be used as basis for development of the Version 2 programs. Additional functions will be developed and added in to the version 1 programs.

Deliverables

4120	Operational code for SRPM, version 2

5.4.1.4	Task 4130	Local system SR-implementation, Version 1

Objective

The objective of this WP is to implement the necessary changes in the local systems in order to be able to communicate via SR.

The objective of this task is to ensure that the local SR-implementations are according to the requirements of version 1 of ONE.

This task will be divided into the following sub-tasks:

T4130-1	SR implementation for BIBSYS, version 1

T4130-2	SR implementation for BL, version 1

T4130-3	SR implementation for DBC, version 1

T4130-4	SR implementation for DDB, version 1

T4130-5	SR implementation for LIBRIS, version 1

T4130-6	SR implementation for Pica, version 1

T4130-7	SR implementation for TKAY, version 1

T4130-8	SR implementation for UBO, version 1

T4130-9	SR implementation for LB, version 1

Approach

For each local system and for each sub task, the module definitions of the local system will be used as input and coded. As modules are completed they will be tested and integrated together in an appropriate manner.

Deliverables

4130	Report on SRPM-modules for each server, version 1

5.4.1.5	Task 4140	Local system SR-implementation, Version 2

Objective

The objective of this WP is to implement the complete SR standard in the local systems according to the implementation plans for each system. The implementation of EXPLAIN in the local systems is included.

This task will be divided into the following sub-tasks:

T4140-1	SR implementation for BIBSYS, version 2

T4140-2	SR implementation for BL, version 2

T4140-3	SR implementation for DBC, version 2

T4140-4	SR implementation for DDB, version 2

T4140-5	SR implementation for LIBRIS, version 2

T4140-6	SR implementation for Pica, version 2

T4140-7	SR implementation for TKAY, version 2

T4140-8	SR implementation for UBO, version 2

T4140-9	SR implementation for LB, version 2

Approach

For each local system and for each sub task, the module definitions of the Version 2 local system will be used as input and coded. As modules are completed they will be tested and integrated together in an appropriate manner.

Deliverables

4140	Report on SRPM-modules for each server, version 2

5.4.1.6	Task 4150	NEP implementation, Version 1

Objective

The objective of this task is to implement a first version of the NEP.

Approach

The NEP definitions, specification and design version 1, will be used as input and coded.

Deliverables

4150	Operational code for NEP, version 1

5.4.1.7	Task 4160	NEP implementation, Version 2

Objective

The objective of this task is to implement the full SR-1995 facilities in the NEP.

This task includes the linking of NEP to the Toolbox.

Approach

The Version 1 NEP code will be used as basis for development of the Version 2 programs. Additional functions will be developed and added in to the version 1 programs.

Deliverables

4160	Operational code for NEP, version 2

5.4.2 WP4200	Stand-alone client, Generic user assistance, and EXPLAIN implementation

Name and number of Work Package

The name of Work Package 4200 is: Stand-alone client, Generic user assistance, and EXPLAIN implementation

Working Area

This WP is 1 of 7 in Work Area Software development

Partner

Responsible for the WP: SIL

Other partners that will participate in this WP:

BIBSYS, BL, DBC, JR, LIBRIS, Pica, TKAY, UBO

Objectives

The objective of this WP is to implement the Stand-alone client, a generic user assistance, and the EXPLAIN facility in the SRPM (common and local), in NEP, in the Stand-alone client, and in the local clients.

The WP is divided into the following tasks:

Task 4200	WP4200 management

Task 4210	Implementation of the Stand-alone client

Task 4220	Implementation of EXPLAIN in NEP Version 2

Task 4230	Implementation of EXPLAIN in local systems, version 2

Task 4240	Implementation of generic user assistance

Prerequisits

Results from WP 3200 Generic user assistance and EXPLAIN design

For the full overview of task dependancies, see Appendix II.

Approach

The approach to each sub task is described in the following subsections.

Most modules will be written in ANSI C.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 4200:	Partners: SIL

|---------------->

Task 4210:	Partners: SIL

|---------------->

Task 4220:	Partners: DBC

|---------------->

Task 4230:	Partners: BIBSYS, BL, DBC, JR, LIBRIS, Pica, TKAY, UBO

|---------------->

Task 4240:	Partners: JR, SIL

|---------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

--------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.17 WP 4200 Time table and deliverables

5.4.2.1	Task 4200	WP4200 management

Objective

The objective of these tasks is to coordinate and manage the tasks in this WP. It is further to ensure that the work is carried out and proceeds according to the project plan.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.4.2.2	Task 4210	Implementation of Stand-alone client

Objective

The objective of this task is to write and test the code for the Stand-alone client.

Approach

The Stand-alone client design will be rewritten into machinereadable code. ANSI C is planned used as programming language.

Deliverables

4210	Operational code for the Stand-alone client

5.4.2.3	Task 4220	Implementation of EXPLAIN in NEP Version 2

Objective

The objective of this task is to write and test the code for EXPLAIN in NEP.

Approach

The EXPLAIN design will be rewritten in machinereadable code. The code modules will be integrated in the NEP and in the standalone client where appropriate and initially tested.

Deliverables

4220	Operational code for EXPLAIN in NEP

5.4.2.4	Task 4230	Implementation of EXPLAIN in local systems, Version 2

Objective

The objective of this task is to ensure that EXPLAIN is implemented in the local systems offered as systems in the project.

This task will be divided into the following sub-tasks:

T4230-1	SR implementation for BIBSYS

T4230-2	SR implementation for BL

T4230-3	SR implementation for DBC

T4230-4	SR implementation for DDB

T4230-5	SR implementation for LIBRIS

T4230-6	SR implementation for Pica

T4230-7	SR implementation for TKAY

T4230-8	SR implementation for UBO

Approach

The EXPLAIN design specifications will be used as input and coded. The code modules will be integrated in the local systems where appropriate and initially tested.

Deliverables

4230	Report on EXPLAIN implementations in local systems

5.4.2.5	Task 4240	Implementation of generic user assistance

Objective

The objective of this task is to write and test the code for a generic user assistance module.

Approach

The module specifications for the generic user assistance will be used as input and the modules coded. The coded modules will be tested against known criteria. Where appropriate, this module should be integrated in the local systems or NEP to establish its operation and use.

Deliverables

4240	Operational code for generic user assistance

5.4.3 WP4300	Implementation of API and Toolbox

Name and number of Work Package

The name of Work Package 4300 is: Implementation of API

Working Area

This WP is 1 of 7 in Work Area Software development

Partner

Responsible for the WP: SIL

Other partners that will participate in this WP:

BL, BRODD, DBC

Objectives

The objective of this WP is to write the specified API in machinereadable code.

The WP is divided into the following tasks:

Task 4301 to 4303:	WP4300 management, Phase 2 to Phase 4

Task 4310	Implementation of API

Task 4321 to 4323:	Implementation of Toolbox, Phase 2 to Phase 4

Prerequisits

Results from WP 3300 Design of API and Toolbox

For the full overview of task dependancies, see Appendix II.

Approach

The approach to each sub task is described in the following subsections.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 4301:	Partners: SIL

|---------------->

Task 4302:	Partners: SIL

|---------->

Task 4303:	Partners: SIL

|---------------->

Task 4310:	Partners: SIL

|---------------->

Task 4321:	Partners: BL, BRODD, DBC

|---------------->

Task 4322:	Partners: BL, BRODD, DBC

|---------->

Task 4323:	Partners: BL, BRODD, DBC

|---------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

--------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.18 WP 4300 Time table and deliverables

5.4.3.1	Task 4301 to 4303	WP4300 management

Objective

The objective of these tasks is to coordinate and manage the tasks in this WP. It is further to ensure that the work is carried out according to the project plan.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.4.3.2	Task 4310	Implementation of API

Objective

The objective of this task is to

This task will be divided into the following sub-tasks:

T4310-1 Implementation of target

T4310-2 Implementation of origin

Approach

Each API function module specification will be used as input and coded.

Where appropriate, both origin and target protocol related functions will be developed together in order to ascertain that both origin and target are operational. The protocol functions will start with basic networked connectivity followed bu Initialisation and then on to Search, Presentation etc. Simple test programs will be developed in order to test the API function behaviour.

Deliverables

4310	Operational code for API

5.4.3.3	Task 4321to 4323 Implemetation of Toolbox

Objective

The objective of this WP is to produce the machinereadable code for a Toolbox which includes modules such as:

Routines for connecting and using the network

Conversion between MARC-formats

Translation between CCL and RPN

Translation between character sets

This task will be divided into the following sub-tasks:

T4320-1	Overall implementation for target

T4320-2	Overall implementation for origin

T4320-3	Implementation for general CCL-to-RPN module

T4320-4	Implementation for general RPN-to-CCL module

T4320-5	Implementation for MARC conversion

T4320-6	Implementation for character conversion module

T4320-7	Implementation for other modules in tool-kit

Approach

For each Tool box function, (defined as a subtask), the module specifications will be used as input and the module will be coded and initially tested.

Where appropriate, simple test programs will be devised to test the module and provide example of how the toolbox function is used.

Deliverables

4321	Toolbox Phase 2 modules, code

4322	Toolbox Phase 3 modules, code

4323	Toolbox Phase 4 modules, code

5.5	5000	TESTING AND OPERATIONS

5.5.1 WP5100	Interoperability testing

Name and number of Work Package

The name of Work Package 5100 is: Interoperability testing

Working Area

This WP is 1 of 9 in Work Area Use and Usability

Partner

Responsible for the WP: TKAY

Other partners that will participate in this WP:

BIBSYS, BL, DBC, DDB, LIBRIS, Pica, SIL, UBO

Objectives

The objective of this WP is to test and verify the existing SR/Z39.50 software installations at the partners' institutions and to see if they can communicate. And to describe any discrepancies identified by this task.

The WP is divided into the following tasks:

Task 5101 to 5105:	WP5100 management, Phase 1 to Phase 5

Task 5110	Definition of interoperability test suite for existing systems

Task 5120	Interoperability testing of existing systems

Task 5130	Documentation of the test results

Task 5140	Definition of interoperability test suite for Version 1

Task 5150	Interoperability testing of version 1 of systems

Task 5160	Definition of interoperability test suite for Version 2

Task 5170	Interoperability testing of version 2 of systems

Task 5180	Documentation of interoperability testing

Prerequisits

Access to partners' systems.

Results from Task 1210 Negotiations on service contracts

For the full overview of task dependancies, see Appendix II.

Approach

The interoperability testing will first test the network connections (lower layers), then the communication on the Transport layer and at last the communication in the upper layers and for the SR protocol.

The manager of the WP will define proformas to be used in describing the results of the testing.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 5101:	Partners: TKAY

|---------------->

Task 5102:	Partners: TKAY

|---------------->

Task 5103:	Partners: TKAY

|---------->

Task 5104:	Partners: TKAY

|---------------->

Task 5105:	Partners: TKAY

|--------------------->

Task 5110:	Partners: TKAY

|------>

Task 5120:	Partners: BIBSYS, BL, DBC, DDB, LIBRIS, Pica, TKAY, UBO

|--------->

Task 5130:	Partners: BIBSYS, BL, DBC, DDB, LIBRIS, Pica, TKAY, UBO

|--->

Task 5140:	Partners: TKAY

|--->

Task 5150:	Partners: BIBSYS, BL, DBC, DDB, LIBRIS, Pica, SIL, TKAY, UBO

|-------->

Task 5160:	Partners: TKAY

|--->

Task 5170:	Partners: BIBSYS, BL, DBC, DDB, LIBRIS, Pica, SIL, TKAY, UBO

|------->

Task 5180:	Partners: TKAY

|------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

--------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.19 WP 5100 Time table and deliverables

5.5.1.1	Task 5101 to 5105	WP5100 management

Objective

The objective of this task is to manage and coordinate the interoperability testing.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.5.1.2	Task 5110	Definition of interoperability test suite for existing systems

Objective

The objective of this task is to define a set of tests to be performed from several systems to each of the operational servers in order to see where, if any, communication problems are located.

Software which automates the testing, at least on UNIX sites, will be used. Specifications and development of software tools capable of the testing will be found or created.

Approach

The basis for this task will either be the Conformance Test Suite for SR defined in the Nordic SR-Net project or the similar Test Suite defined by DANET for the DBV-OSI project.

The Interoperability Test Suite will basicly test positive correlation to the standard, SR/Z39.50.

Deliverables

5110	Interoperability test suite for existing systems

5.5.1.3	Task 5120	Interoperability testing of existing systems

Objective

The objective of this task is to perform interoperability tests between those systems which have an SR/Z39.50 connection.

This task will be divided into the following sub-tasks:

T5120-1	Testing from BIBSYS to all others

T5120-2	Testing from BL to all others (?)

T5120-3	Testing from DBC to all others

T5120-4	Testing from DDB to all others

T5120-5	Testing from LIBRIS to all others

T5120-6	Testing from Pica to all others

T5120-7	Testing from TKAY to all others

T5120-8	Testing from UBO to all others

Approach

The test-suite defined in task 5110 will be applied to each of the sub-tasks. All messages will be logged.

Deliverables

5120	Test logs from each system

5.5.1.4	Task 5130	Documentation of the test results

Objective

The objective of this task is to document the test results in order to improve interoperability.

Approach

The test logs from the participating systems will be used to summarise the test results and identify the communication problems.

The partners in this task will meet for one day and discuss the results of the interoperability testing of the existing systems. They will then propose solutions to communication problems which may have occured.

The WPM will collect the test results, analyse them and record the decisions made by the partners at the meeting.

Deliverables

5130	Documentation of interoperability test results and conclusions.

5.5.1.5	Task 5140	Definition of interoperability test suite for Version 1

Objective

The objective of this task is to define the test suite to use for interoperability testing of version 1 of the systems.

Approach

The results from Task 5110 and 5130 will be used as the basis for defining interoperability test suite for version 1.

Deliverables

5140 Interoperability test suite, Version 1

5.5.1.6	Task 5150	Interoperability testing of version 1 of systems

Objective

The objective of this task is to test the interoperability of version 1 of the systems.

This task will be divided into the following sub-tasks:

T5150-1	Testing from BIBSYS to all others

T5150-2	Testing from BL to all others (?)

T5150-3	Testing from DBC to all others

T5150-4	Testing from DDB to all others

T5150-5	Testing from LIBRIS to all others

T5150-6	Testing from Pica to all others

T5150-7	Testing from TKAY to all others

T5150-8	Testing from UBO to all others

T5150-9	Testing from NEP to all others

Approach

The test-suite defined in task 5140 will be applied to each of the sub-tasks. All messages will be logged.

Deliverables

5150	Test logs from each system

5.5.1.7	Task 5160	Definition of interoperability test suite for Version 2

Objective

The objective of this task is to define the interoperability test suite for version 2 of the systems.

Approach

The Test suite defined for version 1 and the results from Task 5150 will be used as the basis for defining interoperability test suite for version 2.

Deliverables

5160	Interoperability test suite for version 2

5.5.1.8	Task 5170	Interoperability testing of version 2 of systems

Objective

The objective of this task is to test the interoperability of the full SR-1995 implementations.

This task will be divided into the following sub-tasks:

T5170-1	Testing from BIBSYS to all others

T5170-2	Testing from BL to all others (?)

T5170-3	Testing from DBC to all others

T5170-4	Testing from DDB to all others

T5170-5	Testing from LIBRIS to all others

T5170-6	Testing from Pica to all others

T5170-7	Testing from TKAY to all others

T5170-8	Testing from UBO to all others

T5170-9	Testing from NEP to all others

Approach

The test-suite defined in task 5160 will be applied to each of the sub-tasks. All messages will be logged.

Deliverables

5170	Test logs from each system

5.5.1.9	Task 5180	Documentation of interoperability testing

Objective

The objective of this task is to document the result of all three interoperability testing tasks.

Approach

The working on, and results from, the interoperability testing will be documented using session logs

and user experience reports. Results will be described using the proforma defined by the WP manager.

Deliverables

5180	Documentation and conclusions of the interoperability testing.

5.5.2 WP5200	Application interworking

Name and number of Work Package

The name of Work Package 5200 is: Application interworking

Working Area

This WP is 1 of 9 in Work Area Use and usability

Partner

Responsible for the WP: BRODD

Other partners that will participate in this WP:

BIBSYS, BL, DBC, DDB, LIBRIS, Pica, TKAY, UBO

Objectives

The objective of this WP is to see if searching the remote databases gives sensible results. If the database structure and indexing differs so much that it will influence the search results, this has implications for both user manuals and EXPLAIN implementation.

The WP is divided in the following tasks:

Task 5201 and 5202	WP5200 management, Phase 1 and Phase 2

Task 5210	Creating test environment

Task 5220	Application interworking tests

Prerequisits

Results from Task 6120 Local systems' analysis.

For the full overview of task dependancies, see Appendix II.

Approach

A test environment will be created for all systems. Searches will be carried out in order to see how e.g. the result of an author search, a personal name search etc. in each system.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 5201:	Partners: BRODD

|---------------->

Task 5202:	Partners: BRODD

|----------------->

Task 5210:	Partners: BIBSYS, BL, BRODD, DBC, DDB, LIBRIS, Pica, TKAY, UBO

|---------------->

Task 5220:	Partners: BIBSYS, BL, DBC, DDB, LIBRIS, Pica, TKAY, UBO

|----------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

--------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.20 WP 5200 Time table and deliverables

5.5.2.1	Task 5201 to 5202	WP5200 management

Objective

The objective of this task is to manage and coordinate the application interworking testing.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.5.2.2	Task 5210	Creating test environment

Objective

The objective of this task is to define and create test environments in order to test application interworking before the trial service starts.

This task will be divided into the following sub-tasks:

T5210-1	Define main features for the test environments

T5210-2	Create the test environments

Approach

Common entries that are available on all databases will be identified for search statements, in order to compare search results. A proforma will be defined for result description.

Suitable forms for session logs will be defined for logging the system responses during the application interworking testing.

Deliverables

5210	Description of the test environments

5.5.2.3	Task 5220	Application interworking tests

Objective

The objective of this task is to find out the differences between the systems regarding search results for the same search statement. The result of this task will be used as input to user manuals.

Approach

The search statements identified in Task 5210 will be used in searching all the servers. All sessions will be logged.

The results of the search sessions will be analysed in order to identify differencies in system behaviour.

Deliverables

5220	Results of Application interworking tests

5.5.3 WP5300	Organisation and administration of trial service

Name and number of Work Package

The name of Work Package 5300 is: Organisation and administration of trial service

Working Area

This WP is 1 of 5 in Work Area Dissemination of information and results

Partner

Responsible for the WP: DDB

Other partners that will participate in this WP:

BIBSYS, BL, DBC, JR, LB, LIBRIS, LMJ, NM, Pica, TKAY, UBO

Objectives

The objective of this WP is to organise the user testing of the systems and the trial service.

The WP is divided into the following tasks:

Task 5301 to 5303:	WP5300 management, Phase 2 to Phase 4

Task 5310	Planning trial service, version 1

Task 5320	Planning trial service, version 2

Task 5331 to 5332	Choosing, and instructing, users for participation in testing

Prerequisits

Results from Task 1210 Negotiations on Service Contracts; Results from WP 2200 Specification of services to be offered.

For the full overview of task dependancies, see Appendix II.

Approach

One will define the content of session logs, forms for user interviews etc.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

___________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 5301:	Partners: DDB

|---------------->

Task 5302:	Partners: DDB

|---------->

Task 5303:	Partners: DDB

|---------------->

Task 5310:	Partners: DDB

|---------------->

Task 5320:	Partners: DDB

|---------->

Task 5331:	Partners: BIBSYS, BL, DBC, JR, LB, LIBRIS, LMJ, NM, Pica, TKAY, UBO

|---------------->

Task 5332:	Partners: BIBSYS, BL, DBC, JR, LB, LIBRIS, LMJ, NM, Pica, TKAY, UBO

|---------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

---------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.21 WP 5300 Time table and deliverables

5.5.2.1	Task 5301 to T5303	WP5300 management

Objective

The objective of these tasks is to coordinate and manage the work in this WP. It is further to ensure that task 5320 makes use of the results from the first of the user testing periods.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.5.2.2	Task 5310	Planning trial service, version 1

Objective

The objective of this task is to plan the trial service concerning user groups, logs etc.

Approach

A plan will be made which identifies the user groups in each partner institution that should be represented in the users of the trial service. The minimal number of end-users participating in the trial service will be decided.

A list of suggested types of searches to be performed, will be made, but this list will not limit the users' use of the trial service.

The different data needed for analysing the trial service, will be identified, and how these data can best be collected.

Deliverables

5310	Plan for trial service, version 1

5.5.2.3	Task 5320	Planning trial service, version 2

Objective

The objective of this task is to ensure that different user groups in many partner institutions take part in the trial service and that the user sessions is adaquatly logged.

Approach

The plan for trial service of version 1 will be enhanced, both regarding user groups, number of users and types of logs needed.

Deliverables

5320	Plan for trial service, version 2

5.5.2.4	Task 5331 and 5332	Choosing, and preparing, users for participation in testing

Objective

The objective of this task is to ensure a wide selection of users, from all participating systems, which will participate both in testing and in the trial service.

The objective is also to instruct the users for the trial service.

Approach

The plan for the trial service defines the types of users that should be selected. The operators of the library services will choose users, representative of their user groups, which will be testing and using the trial service first.

Each participating partner will make written instructions to their respective users in how to use the trial service.

More users will be added in phase 5.

Deliverable

Initial list of users chosen for the testing period.

5.5.4 WP5400	User testing (trial service)

Name and number of Work Package

The name of Work Package 5400 is: User testing (trial service)

Working Area

This WP is 1 of 5 in Work Area Dissemination of information and results

Partner

Responsible for the WP: DDB

Other partners that will participate in this WP:

All partners except NB.

Objectives

The objective of this WP is to test the new services in real environments and in real working situations.

The WP is divided into the following tasks:

Task 5401 to 5403:	WP5400 management, Phase 3 to Phase 5

Task 5411 to 5412:	Porting software, Phase 3 to Phase 4

Task 5421 to 5423:	User training, Phase 3 to Phase 5

Task 5431 to 5433:	User support, Phase 3 to Phase 5

Task 5441 to 5443:	Technical support, Phase 3 to Phase 5

Task 5450	Analysis of search results (based on session logs)

Task 5460	Analysis of errors and error situations (based on session logs)

Task 5470	Analysis of user reactions and experiences (based on forms and interviews)

Prerequisits

Operative systems;

Access to partners' systems;

Short user guidence manuals

Results from WP 4100 Implementation of SRPM;

Results from WP 4200 Implementation of EXPLAIN;

Results from WP 4300 Implementation of API and Toolbox.

Results from WP 5200 Application interworking

Results from WP 9100 User documentation;

For the full overview of task dependancies, see Appendix II.

Approach

The selected users will get instruction on how to use the system by their local Project Team members.

The users decide themselves what to search for and when. Their use of the trial service will be part of their daily work.

During the trial service new versions of the software will be installed, both as "new versions" and as a result of error corrections. The users will be instructed in how to use the new and corrected versions by the local PT member.

A PT member in each partner institution will be responsible for user support such as answering questions on how to use the system and the different (protocol) services such as EXPLAIN.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 5401:	Partners: DDB

|---------->

Task 5402:	Partners: DDB

|---------------->

Task 5403:	Partners: DDB

|--------------------->

Task 5411:	Partners: BL, BRODD, DBC, JR, Pica, SIL, UBO

|---------->

Task 5412:	Partners: BL, BRODD, DBC, JR, Pica, SIL, UBO

|---------------->

Task 5421:	Partners: BIBSYS, BL, DBC, DDB, JR, LB, LIBRIS, LMJ, NM, Pica, SIL, TKAY, UBO

|---------->

Task 5422:	Partners: BIBSYS, BL, DBC, DDB, JR, LB, LIBRIS, LMJ, NM, Pica, SIL, TKAY, UBO

|---------------->

Task 5423:	Partners: BIBSYS, BL, DBC, DDB, JR, LB, LIBRIS, LMJ, NM, Pica, SIL, TKAY, UBO

|--------------------->

Task 5431:	Partners: BIBSYS, BL, DBC, DDB, JR, LB, LIBRIS, LMJ, NM, Pica, SIL, TKAY, UBO

|---------->

Task 5432:	Partners: BIBSYS, BL, DBC, DDB, JR, LB, LIBRIS, LMJ, NM, Pica, SIL, TKAY, UBO

|---------------->

Task 5433:	Partners: BIBSYS, BL, DBC, DDB, JR, LB, LIBRIS, LMJ, NM, Pica, SIL, TKAY, UBO

|--------------------->

Task 5441:	Partners: BIBSYS, BL, DBC, DDB, JR, LB, LIBRIS, LMJ, NM, Pica, SIL, TKAY, UBO

|---------->

Task 5442:	Partners: BIBSYS, BL, DBC, DDB, JR, LB, LIBRIS, LMJ, NM, Pica, SIL, TKAY, UBO

|---------------->

Task 5443:	Partners: BIBSYS, BL, DBC, DDB, JR, LB, LIBRIS, LMJ, NM, Pica, SIL, TKAY, UBO

|--------------------->

Task 5450:	Partners: DDB

|--------->

Task 5460:	Partners: DDB

|--------->

Task 5470:	Partners: DDB

|--------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

----------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.22 WP 5400 Time table and deliverables

5.5.4.1	Task 5401 to 5403	WP5400 management

Objective

The objective of this task is to coordinate and manage the user testing to ensure that all users get the support and the documentation they need.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.5.4.2	Task 5411 to 5412	Porting software

Objective

The objective of these tasks is to ensure that there is a plan for porting software . This includes corrected versions of the software as well as the planned version 1 and version 2.

Approach

A description of the necessary tools available for each platform for installing the software, will be made. The availability of the tools will be ensured.

The plan will also contain a time schedule for when to install new and corrected versions at the different sites.

Deliverables

5410	Plan for porting software versions

5.5.4.3	Task 5421 to 5423	User training

Objective

The objective of these tasks is to ensure that each partner offering a client service has a plan for performing user training, and that such training takes place before the users start using the trial service .

The objective of the user training is to ensure that the users understand the possibilities, and limitations, of the systems, and also the possible discrepansies in search results from different servers.

Approach

Each partner offering a client service will carry out user trainig in the most suitable way for their institution.

Deliverables

5420	Plan for user training

5.5.4.4	Task 5431 to 5433	User support

Objective

The objective of these tasks is to ensure that each partner offering a client service will have a plan for performing user support, and set aside time for user support in the trial service, during regular opening hours.

Approach

Each partner offering a client service will appoint at least one person responsible for user support.

User support will cover short instructions in how to use the system, and actual assistance in using the system.

Deliverables

5410	Plan for user support

5.5.4.5	Task 5441 to 5442	Technical Support

Objective

The objective of these tasks is to ensure that there is a plan for technical support available in the trial service period, during regular opening hours.

Approach

Each partner offering either a client or a server service will appoint person(s) responsible for technical support during the trial service in order to quickly correct errors that might occur in either the system modules or in the network communication modules.

When, or if, an error occurs, the location of the error will start at once. When located, the correction of the error will start within 4 hours on working days.

Deliverables

5420	Plan for technical support

5.5.4.6	Task 5450 Analysis of search results (based on session logs)

Objective

The objective of this WP is to find out where the systems must be improved and other changes.

Approach

User logs will be analysed for unexpected system responses.

Deliverables

5450 Analysis of search results

5.5.4.7	Task 5460 Analysis of errors and error situations (based on session logs)

Objective

The objective of this WP is to find out where the systems must be improved and other changes.

Approach

Faulty responses will be analysed to exclude the possibility of faulty use of system, and then compared to the session logs.

Deliverables

5460 Analysis of errors and error situations

5.5.4.8	Task 5470 Analysis of user reactions and experiences (based on forms and interviews)

Objective

The objective of this WP is to find out where the systems must be improved and other changes.

Approach

The results from forms and interviews will be used to systematically review the user experience with respect to the services and the user friendliness.

Deliverables

5470 Analysis of user reactions and experiences

5.6	6000	USER INTERFACE

5.6.1 WP6100	User interface

Name and number of Work Package

The name of Work Package 6100 is: Local user interface analysis

Working Area

This WP is 1 of 9 in Work Area Use and Usability

Partner

Responsible for the WP: JR

Other partners that will participate in this WP:

BIBSYS, BL, BRODD, DBC, DDB, LIBRIS, Pica, SIL, TKAY, UBO

Objectives

The objective of this work package is to get a list of all user facilities in the systems regarding search criteria, display formats, help functions etc. The result of this work package will be used as basis for the requirements for a generic user assistance, and the mapping of this to the EXPLAIN protocol service.

The WP is divided into the following tasks:

Task 6101 to 6103:	WP6100 management, Phase 1 to Phase 3

Task 6110	Defining forms for describing local user interfaces

Task 6120	Local user interface analysis (search possibilities, present possibilities, help functions, sort, etc.)

Task 6130	Requirements for user assistance (all types of users)

Task 6140	Specification of generic user assistance

Task 6150	Mapping generic user assistance services to EXPLAIN

Prerequisits

Knowledge of local systems' user interfaces.

Approach

Proforma for describing the local user interfaces will be defined.

Each partner will fill in the proforma for their local system. These proformas will then be analysed in order to produce a complete list of all search, display and help possibilities in the systems.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 6101:	Partners: JR

|---------------->

Task 6102:	Partners: JR

|---------------->

Task 6103:	Partners: JR

|---------->

Task 6110:	Partners: JR, BRODD

|---->

Task 6120:	Partners: BIBSYS, BL, DBC, DDB, LIBRIS, Pica, TKAY, UBO

|----------->

Task 6130:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, Pica, SIL, TKAY, UBO

|---------------->

Task 6140:	Partners: JR

|---------->

Task 6150:	Partners: JR

|---------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

---------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.23 WP 6100 Time table and deliverables

5.6.1.1	Task 6101 to 6103	WP6100 management

Objective

The objective of this WP is to find out where the systems must be improved and other changes.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.6.1.2	Task 6110 Defining forms for describing local user interfaces

Objective

The objective of this task is to make a tool which will enable us to collect a complete list of search, display and help possibilities in the participating systems.

Approach

A list of system attributes such as search possibilities, display formats etc. will be made and structured into a proforma.

Deliverables

6110	Proforma for describing local user interfaces

5.6.1.3	Task 6120 Local user interface analysis (search possibilities, present possibilities, help functions, sort, etc.)

Objective

The objective of this task is to collect as much information as possible about user interfaces used in existing library systems.

This task will be divided into the following sub-tasks:

T6120-1	Posibilities in BIBSYS user interface

T6120-2	Posibilities in BL user interface

T6120-3	Posibilities in DBC user interface

T6120-4	Posibilities in DDB user interface

T6120-5	Posibilities in LIBRIS user interface

T6120-6	Posibilities in Pica user interface

T6120-7	Posibilities in TKAY user interface

T6120-8	Posibilities in UBO user interface

Approach

The Proforma defined in Task 6110 will be filled in by the partner offering client or server systems. The analysis will be based on the filled-in formes which give the descriptions of the user interface in a uniform manner.

Deliverables

6120	Analysis of local user interface possibilities

5.6.1.4	Task 6130 Requirements for user assistance (all types of users)

Objective

The objective of this task is to make requirements for online user assistance in systems. And to identify which generic requirements can be implemented in an EXPLAIN protocol service.

This task will be divided into the following sub-tasks:

T6130-1 Requirements for each local system

T6130-2 Requirements for NEP

T6130-3 General requirements

Approach

The requirements will be defined on the basis of the results in task 6120 and the know-how of the partners.

Deliverables

6130 Requirements for user assistance

5.6.1.5	Task 6140 Specification of generic user assistance

Objective

The objective of this work package is to specify a generic user assistance in a client system.

Approach

The generic user assistance requirements (results from task 6130) will be used a the basis for these specifications. The requirements identified in task 6130 will be divided into groups:

-	requirements that must be satisfied locally

-	generic requirements that can be satisfied locally

-	generic requirements that can be mapped to a network protocol service

-	requirements that will not be included in ONE software modules

Deliverables

6140 Specification of generic user assistance

5.6.1.6	Task 6150 Mapping generic user assistance services to EXPLAIN

Objective

The objective of this task is to map a generic user assistance to an EXPLAIN database.

Approach

The identified user assistance requirements will be matched towards the present version and functionality of the EXPLAIN attribute set. If one or more requirements can not be mapped to the existing attribute set and functionality, new attribute types and/or functions will be defined.

Deliverables

6150 Mapping generic user assistance services to EXPLAIN

5.7	DISSEMINATION AND EXPLOITATION

5.7.1 WP7100	Dissemination and exploitation

Name and number of Work Package

The name of Work Package 7100 is: Dissemination and exploitation.

Working Area

This WP is 1 of 5 in Work Area Dissemination of information and results

Partner

Responsible for the WP: NB

Other partners that will participate in this WP:

BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, Pica, SIL, TKAY, UBO

Objectives

The main objective of this WP is to ensure three ways of information dissemination:

-	external information distributed within the project

-	internal information distributed within the project

-	project information and results distributed outside the project

The objective of this WP is to ensure that information from and about the project will be spread during the project period, and that the results will be published. It is also the objective of this WP to find the best way to disseminate the information from and about the project to the library communicy as a whole.

The objective of this WP is also for each partner to make a plan for the exploitation of the results from the project, and to carry out this plan at the end of the project.

The WP is divided into the following tasks:

Task 7101 to 7105:	WP7100 management, Phase 1 to Phase 5

Task 7110	Dissemination plan

Task 7121 to 7125:	Dissemination of information, Phase 1 to Phase 5

Task 7130	Exploitation plans

Task 7141	Porting common software, Phase 2

Task 7142	Porting common software, Phase 4

Task 7143	Porting common software, Phase 5

Task 7151 to 7153:	Maintenance of common software, Phase 3 to Phase 5

Task 7160	Preparation for exploitation activities

Prerequisits

Information to be disseminated.

Approach

The Work Package Manager (WPM) will inform externally of all open documents from the project. All partners will present the project and the results in their local fora such as library conferences and periodicals. The partners will attend meetings such as IFLA, ELAG, ISO, EWOS, EFILA and ZIG where they will present the project.

The WPM will supervise the dissemination of information througout the project to ensure that the "world outside" will be kept informed about the progress of the project.

The WPM will create and maintain a "project archive" and a system which ensures that all partners receive the distributed information, internal and external.

The WPM will ensure that all documents, external and internal, are delivered to the "project archive".

The WPM will perform an awareness function for external information relevant to the project.

Address lists (electronic and non-electronic mail) of all interested receivers will be compiled. At each phase the list of open documents produced, will be distributed.

Regular channels will be established within the project for exchange of information, documents and software modules.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

__________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 7101:	Partners: NB

|---------------->

Task 7102:	Partners: NB

|---------------->

Task 7103:	Partners: NB

|---------->

Task 7104:	Partners: NB

|---------------->

Task 7105:	Partners: NB

|--------------------->

Task 7110:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|---------------->

Task 7121:	Partners: NB

|---------------->

Task 7122:	Partners: NB

|---------------->

Task 7123:	Partners: NB

|---------->

Task 7124:	Partners: NB

|---------------->

Task 7125:	Partners: NB

|--------------------->

Task 7130:	Partners: BIBSYS, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|---------------->

Task 7141:	Partners: SIL

|---------------->

Task 7142:	Partners: SIL

|---------------->

Task 7143:	Partners: SIL

|------------>

Task 7151:	Partners: SIL

|----------------->

Task 7152:	Partners: SIL

|---------------->

Task 7153:	Partners: SIL

|--------------------->

Task 7160:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|--------------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

---------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.24 WP 7100 Time table and deliverables

5.7.1.1	Task 7101 to 7105	WP7100 management

Objective

The objective of these tasks is to coordinate and manage the tasks in this WP. It is further to ensure that information is disseminated both inside and outside the project.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.7.1.2	Task 7110	Dissemination plan

Objective

The objective of this task is to define a plan for dissemination of information both within the project and to external bodies.

Approach

The different channels for various forms of information exchange will be established.

The relevant fora for presentation of the project progress and results will be identified. The responsibility for the presentations in the different fora will be distributed among the partners.

The sites reciving software modules from the project will be identified together with specific requirements for each site.

The different types of documents to disseminate will be identified. A structure for numbering the documents according to type and availability will be chosen.

Recipient of documents will be identified.

The list of receipients will be updated at the start of each phase.

The dissemination plan and how it has been carried out will be discussed at all project team plenary meetings. Adjustments to the plan will be done when necessary.

Deliverables

7110	Dissemination plan

5.7.1.3	Task 7121 to 7125	Dissemination of information

Objective

The objective of these tasks is to ensure dissemination within the project of both internal and external information, and to disseminate the results from the project to all interested parties.

Approach

All partners will present the project progress in their local fora and in all relevant global fora they attend.

A file server is established. There will be a public and an internal file store on this file server.

Most documents will be distributed through the file-server, but paper copies will be distributed on request.

Documents not in machinereadable form will be distributed by mail.

Open documents produced within the project will be externaly distributed when they are approved by the Commission.

Deliverables

7120/A Report on dissemination of information and results, Phase 1

7120/B Report on dissemination of information and results, Phase 2

7120/C Report on dissemination of information and results, Phase 3

7120/D Report on dissemination of information and results, Phase 4

7120/E Report on dissemination of information and results, Phase 5

5.7.1.4	Task 7130 Exploitations plan

Objective

The objective of this WP is for each partner to make a plan for the exploitation of the results from the project, and to carry out this plan at the end of the project.

This task will be divided into the following sub-tasks:

T7130-1 Exploitation of common results

T7130-2 Exploitation in BIBSYS

T7130-3 Exploitation in BL

T7130-4 Exploitation in DBC

T7130-5 Exploitation in DDB

T7130-6 Exploitation in JR

T7130-7 Exploitation in LIBRIS

T7130-8 Exploitation in Pica

T7130-9 Exploitation in TKAY

T7130-10Exploitation in UBO

Approach

The exploitation plan will be based on the exploitation plans of the partners.

Deliverables

7130	Exploitation plan

5.7.1.5	Task 7141 to 7143	Porting common software

Objective

The objective of these tasks is to port the common software modules to non-partners.

Approach

The commonly developed software will be freely available to non-partners. The necessary tools for installing the software will be described for the actual platforms.

When requesting the ONE software, the receiver institution is responsible for installing these necessary tools. The partner who has developed the module, will also install it. The receiver of the software will cover expenses connected with the installation such as travels.

Deliverables

7140/A	Description of necessary tools for installation of each module

7140/B	Report on porting common software, Phase 3

7140/C	Report on porting common software, Phase 4

7140/D	Report on porting common software, Phase 5

5.7.1.6	Task 7151 to 7153 Maintenance of common software

Objective

The objective of these tasks is to ensure maintenance services for the common software.

Approach

A plan for maintenance of the software will be made. This plan will also contain the responsible partner for maintenance of the different software modules.

The partner responsible for the development of a software module, is also responsible for the maintenance of this module during the project.

Deliverables

715x	Report on type of maintenance included

5.7.1.7	Task 7160 Preparation for exploitation activities

Objective

The objective of this task is to ensure that exploitation of the results from the projects is done.

Approach

The partners will identify subjects for negotiations for regular service contracts, and in some cases start these negotiations.

The partners will also inform other institutions on the possibilities for getting the software packages from the project and how to install and use them.

Deliverable

An updated exploitation plan for each partner with description of the state of the art for the exploitation of the results.

5.8	8000	STANDARDISATION

5.8.1 WP8100	Study of standards with amendments

Name and number of Work Package

The name of Work Package 8100 is: Study of standards with amendments

Working Area

This WP is 1 of 5 in Work Area Dissemination of information and results

Partner

Responsible for the WP: BRODD

Other partners that will participate in this WP:

BIBSYS, BL, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

Objectives

The objective of this WP is to ensure that all partners have a good knowledge, and understanding, of the relevant standards. The objective is also to give input the the standardisation work on SR.

It is further the opbject of this WP to encourage the partners to participate in the relevant standardisation bodies.

The WP is divided into the following tasks:

Task 8101 to 8105:	WP8100 management, Phase 1 to Phase 5

Task 8110	Study of SR and proposed enhancements

Task 8120	Study of Z30.50 Version 3

Task 8130	Study of TOSI

Task 8140	Study of mOSI

Task 8150	Update of ISP ALD11

Task 8160	Proposal for standard enhancements

Task 8171 to 8175:	Participation in standardisation bodies, Phase 1 to Phase 5

Prerequisits

Latest version of standards available, including proposed amendments.

Approach

The relevant standardisation documents will be distributed. Each partner will make a list of which parameters/attributes are relevant for his local implementation and which parameter/attributes are missing in the present standards.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

___________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 8101:	Partners: BRODD

|---------------->

Task 8102:	Partners: BRODD

|---------------->

Task 8103:	Partners: BRODD

|---------->

Task 8104:	Partners: BRODD

|---------------->

Task 8105:	Partners: BRODD

|--------------------->

Task 8110:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|---------------->

Task 8120:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|---------------->

Task 8130:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|---------------->

Task 8140:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|---------------->

Task 8150:	Partners:

|----------------->

Task 8160:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|--------------------->

Task 8171:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|---------------->

Task 8172:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|---------------->

Task 8173:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|---------->

Task 8174:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|---------------->

Task 8175:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, NB, Pica, SIL, TKAY, UBO

|--------------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

---------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.25 WP 8100 Time table and deliverables

5.8.1.1	Task 8101 to 8105	WP8100 management

Objective

The objective of these tasks is to coordinate and manage the tasks in this WP. It is further to ensure that all partners have the relevant standards documents available.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Progress reports according to the project reporting procedures.

5.8.1.2	Task 8110	Study of SR and proposed enhancements

Objective

The objective of these tasks is to ensure that all partners are familiar with SR and its proposed amendments.

Approach

The relevant documents will be distributed and each member of the Project team will study them, particularly the protocol service descriptions.

Deliverables

8110	A list of the services and attributes that each partner will support.

5.8.1.3	Task 8120	Study of Z39.50 Version 3

Objective

The objective of these tasks is to ensure that all partners are familiar with Z39.50 Version 3.

Approach

The Z39.50 Version 3 document will be distributed. Each member of the Project Team will study it. Each partner will list the services and attributes they will support and compare this list to the one made in task 8110. A complete list of services and attributes supported by each partner will be made.

Deliverables

8120	List of supported services and attributes.

5.8.1.4	Task 8130	Study of TOSI

Objective

The objective of these tasks is to ensure that all partners know what Thin OSI is and in particular what the package TOSI does.

Approach

The documentation of TOSI will be distributed and studied with respect to functionality and possible integration with the local SRPM.

Deliverables

8130	Reports from Partners with respect to possible integration locally.

5.8.1.5	Task 8140 Study of mOSI

Objective

The objective of these tasks is to ensure that all partners know what minimal OSI means and in particular what the "package" mOSI contains.

Approach

The results from the EWOS Project Team "PT 031 Study of mOSI and SR" will be distributed together with available documentation of mOSI implementations.

Deliverables

8140	Report on possibilities for local installation of mOSI

5.8.1.6	Task 8150	Update of ISP ALD11

Objective

The objective of these tasks is to ensure that the experiences from ONE is reflected in the profile work of EWOS EGLIB.

Approach

The necessary changes identified in the project will be structured and given to EWOS EGLIB either for inclusion in ALD11 or for definition of a new profile.

Deliverables

8150	List of changes and additions to ALD11.

5.8.1.7	Task 8160 Proposal for standard enhancements

Objective

The objective of this work package is to give input to the standardisation of application protocols for libraries, based on experience and research.

This task will be divided into the following sub-tasks:

T8160-1 Proposals for new protocol services

T8160-2 Proposals for new OIDs

Approach

The results from the user requirements and system requirements will be compared with the possibilities in the present standards. Requirements not supported by the present standards will be identified and presented as proposals to standard amendments and proposal for new registered values for attributes.

Deliverables

8160/A Proposals for new protocol services

8160/B Proposals for new OIDs

5.8.1.8	Task 8171 to 8175 Participation in standardisation bodies

Objective

The objective of these tasks is to enable the partners to attend meetings in the standardisation bodies, that all partners attend the EFILA meetings, and that partners can attend some of the ZIG meetings in order to present European views and requirements.

This task will be divided into the following sub-tasks:

T8170-1 Participation in TC 46/SC 4/WG 4

T8170-2 Participation in EWOS EGLIB

T8170-3 Participation in EFILA

T8170-4 Participation in ZIG

Approach

The partners will arrange beteew them who and how many will participate in the different standardisation meetings. All relevant standardisation meetings will be attended by at least two members of the Project team.

Deliverables

8170	Report on partners' participation in the standardisation bodies and implementators' groups..

5.9	9000	DOCUMENTATION

5.9.1 WP9100	User documentation

Name and number of Work Package

The name of Work Package 9100 is: User documentation

Working Area

This WP is 1 of 5 in Work Area Dissemination of information and results

Partner

Responsible for the WP: LIBRIS

Other partners that will participate in this WP:

BIBSYS, BL, BRODD, DBC, DDB, JR, Pica, SIL, TKAY, UBO

Objectives

The objective of this work package is to ensure that all participating systems will have user documentation, on paper or in machine-readable form, instructing the user of the facilities in the different systems.

The WP is divided into the following tasks:

Task 9101 to 9105:	WP 9100 management, Phase 1 to Phase 5

Task 9110	Defining rules and forms for documentation (all types)

Task 9121 to 9124:	User documentation (for use of SR module), Phase 2 to Phase 5

Task 9131 to 9134:	Installation documentation, Phase 2 to Phase 5

Task 9141 to 9143:	System operation documentation, Phase 3 to Phase 5

Task 9151 to 9155:	Software documentation, Phase 1 to Phase 5

Prerequisits

Results from WP 2100, WP 2300, WP 2400, WP 2500 and WP 6100 (System specifications).

Local systems' user documentation

For the full overview of task dependancies, see Appendix II.

Approach

Rules and forms for documentation of the commonly developed software modules will be defined on the basis of the partners local rules for documentation.

All commonly developed software modules will be documented according to these rules. This documentation will be written in english.

Documentation for the end users will be enhancements of existing local user documentation and will therefore be written in the same language as the existing user documentation.

Start and completion dates

Phase 1	|Phase 2	|Ph.3	|Phase 4	|Phase 5	|

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

_________________________________________________________

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

Task 9101:	Partners: LIBRIS

|---------------->

Task 9102:	Partners: LIBRIS

|---------------->

Task 9103:	Partners: LIBRIS

|---------->

Task 9104:	Partners: LIBRIS

|---------------->

Task 9105:	Partners: LIBRIS

|--------------------->

Task 9110:	Partners: LIBRIS

|---------------->

Task 9121:	Partners: BIBSYS, BL, DBC, DDB, LIBRIS, Pica, SIL, TKAY, UBO

|---------------->

Task 9122:	Partners: BIBSYS, BL, DBC, DDB, LIBRIS, Pica, SIL, TKAY, UBO

|---------->

Task 9123:	Partners: BIBSYS, BL, DBC, DDB, LIBRIS, Pica, SIL, TKAY, UBO

|---------------->

Task 9124:	Partners: BIBSYS, BL, DBC, DDB, LIBRIS, Pica, SIL, TKAY, UBO

|--------------------->

Task 9131:	Partners: BRODD, DBC, SIL

|---------------->

Task 9132:	Partners: BRODD, DBC, SIL

|---------->

Task 9133:	Partners: BRODD, DBC, SIL

|---------------->

Task 9134:	Partners: BRODD, DBC, SIL

|--------------------->

Task 9141:	Partners: BIBSYS, BL, BRODD, DBC, DDB, LIBRIS, Pica, SIL, TKAY, UBO

|---------->

Task 9142:	Partners: BIBSYS, BL, BRODD, DBC, DDB, LIBRIS, Pica, SIL, TKAY, UBO

|---------------->

Task 9143:	Partners: BIBSYS, BL, BRODD, DBC, DDB, LIBRIS, Pica, SIL, TKAY, UBO

|--------------------->

Task 9151:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, Pica, SIL, TKAY, UBO

|---------------->

Task 9152:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, Pica, SIL, TKAY, UBO

|---------------->

Task 9153:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, Pica, SIL, TKAY, UBO

|---------->

Task 9154:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, Pica, SIL, TKAY, UBO

|---------------->

Task 9155:	Partners: BIBSYS, BL, BRODD, DBC, DDB, JR, LIBRIS, Pica, SIL, TKAY, UBO

|--------------------->

|	|	|	|	|	|	|	|	|	|	|	|	|	|	|	|

--------------------------------------------------------------------------------------

0	2	4	6	8	10	12	14	16	18	20	22	24	26	28	30

Fig.5.26 WP 9100 Time table and deliverables

5.9.1.1	Task 9101 to 9105	WP 9100 management

Objective

The objective of these tasks is to coordinate and manage the tasks in this WP. It is further to ensure that all types of documentation for the developed modules are produced on time.

Approach

Each task for each phase will be carefully monitored to ensure that the objectives are met within budget and timescale. Task progress will be reported according to the project reporting procedures.

Deliverables

Management reports.

5.9.1.2	Task 9110	Defining rules and forms for documentation (all types)

Objective

The objective of this task is to get a unified way of documentation from the project.

Approach

The rules and forms of documentation of the commonly developed software will be based on the rules for such documentation used in the partner institution and in ISO 9000.

Deliverables

9110	Rules and forms for documentation

5.9.1.3	Task 9121 to 9124	User documentation (for use of SR module)

Objective

The objective of this task is to write user guidlines for the use of the extra facilities that SR gives.

This task will be divided into the following sub-tasks:

T9120-1	User documentation for BIBSYS

T9120-2	User documentation for BL

T9120-3	User documentation for DANBIB

T9120-4	User documentation for DDB

T9120-5	User documentation for LIBRIS

T9120-6	User documentation for Pica

T9120-7	User documentation for LINNEA

T9120-8	User documentation for UBO:BOK and TRIP

T9120-9	User documentation for LB

T9120-10	User documentation for LMJ

T9120-11	User documentation for NM

T9120-12	User documentation for NEP

Approach

This type of documentation will be enhancements of the existing, local user documentation.

Deliverables

9120	User documentation

5.9.1.4	Task 9131 to 9134	Installation documentation

Objective

The objective of this task is to write installation documentation for all commonly developed software.

The objective of this work package is to write the description of the installation of the different software packages produced in the project. The description will cover installation on the following platforms:

PC-WINDOWS

PC-DOS (possibly)

UNIX

XWINDOWS

....

This task will be divided into the following sub-tasks:

T9131-1	Installation documentation for SRPM and API

T9131-2	Installation documentation for NEP

T9131-3	Installation documentation for Toolbox

Approach

Installation guidelines will be made for each type of platform the software can run on. For each platform, the tools needed for the modules to be compiled and operated, will be listed.

Deliverables

9130	Installation documentation

5.9.1.5	Task 9141 to 9144	System operation documentation

Objective

The objective of this task is to write operation documentation for system operators. This includes how to restart modules, which files must be included in the different types of back-up, how to operate the software, manage smaller error situations etc.

This task will be divided into the following sub-tasks:

T9141-1	System operation documentation for BIBSYS

T9141-2	System operation documentation for BL

T9141-3	System operation documentation for DANBIB

T9141-4	System operation documentation for DDB

T9141-5	System operation documentation for LIBRIS

T9141-6	System operation documentation for Pica

T9141-7	System operation documentation for LINDA

T9141-8	System operation documentation for UBO and TRIP

T9141-9	System operation documentation for NEP

T9141-10	System operation documentation for Toolbox

T9141-11	System operation documentation of SRPM and API

Approach

Guidelines will be made which describes how to start and operate the software modules. This includes the sequence to start modules.

Deliverables

9141/A	System operation documentation for local systems

9141/B	System operation documentation for NEP

9141/C	System operation documentation for Toolbox

9141/D	System operation documentation of SRPM and API

5.9.1.6	Task 9151 to 9155	Software documentation

Objective

The objective of this work package is to ensure that all software is documented, both inside the code and in a separate file/report.

The objective is further to document the software in parallel with its development. The software will be documentet as described in the Quality Assurance Plan.

This task will be divided into the following sub-tasks:

T9151-1	Software documentation for BIBSYS

T9151-2	Software documentation for BL

T9151-3	Software documentation for DANBIB

T9151-4	Software documentation for DDB

T9151-5	Software documentation for LIBRIS

T9151-6	Software documentation for Pica

T9151-7	Software documentation for LINDA

T9151-8	Software documentation for UBO and TRIP

T9151-9	Software documentation for NEP

T9151-10	Software documentation for SRPM

T9151-11	Software documentation for API

T9151-12	Software documentation for Toolbox

Approach

Software documentation of locally developed modules (which will not be ported) will follow the local rules for documentation.

The commonløy developed software (which will be ported) will be documented according to the rules defined in Task 9110.

Deliverables

9150/A	Software documentation of NEP

9150/B	Software documentation of SRPM

9150/C	Software documentation of API

9150/D	Software documentation of Toolbox