Bath Profile - vendor considerations Page 1 The Bath Profile - vendor considerations Rob Bull.

Slides:



Advertisements
Similar presentations
Remote Visualisation System (RVS) By: Anil Chandra.
Advertisements

Cathy N. Hartman University of North Texas Libraries October 10, 1998 Cathy N. Hartman University of North Texas Libraries October 10, 1998.
Canada The Bath Profile and The Journey To Interoperability Carrol D Lunau Bath Profile Maintenance Agency July 7, 2003
Bath Profile – 4 years on A perspective of Z39.50 and the Bath Profile from a commercial systems provider. 8 th July 2003.
Z39.50 Profiles The Bath Profile ZIG Meeting Leuven, Belgium July 2000 William E. Moen School of Library and Information Sciences University.
Standardizing Usage Statistics Requests with SUSHI Theodore Fons Senior Product Manager Innovative Interfaces.
Mobile Agents Mouse House Creative Technologies Mike OBrien.
© IG Service ConsultingApr 2013 Project Scoping Decisions Lift & Shift v Transform & Shift.
COM vs. CORBA.
CAIRNS goes public Stephen Winch Scottish Library & Information Council CIGS: State of the union: union catalogues in the Scottish information environment.
Slide 1Explain LiteONE -2 OPAC Network in Europe Explain Lite Research and Development activity in the ONE-2 Project - OPAC Network in Europe 2.
THE JINI TECHNOLOGY Alessio Zumbo
Distributed components
Copyright 2004 Monash University IMS5401 Web-based Systems Development Topic 2: Elements of the Web (g) Interactivity.
Managing Data Resources
Presentation Outline  Project Aims  Introduction of Digital Video Library  Introduction of Our Work  Considerations and Approach  Design and Implementation.
Peoplesoft Fundamentals David Lewis 10/18/02 (adapted from Psoft Training Materials)
DCS Architecture Bob Krzaczek. Key Design Requirement Distilled from the DCS Mission statement and the results of the Conceptual Design Review (June 1999):
Recall The Team Skills 1. Analyzing the Problem 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5. Refining the System.
Software Requirements
The future of the catalogue Warwick Cathro Assistant Director- General, Innovation.
Introduction to Databases Transparencies 1. ©Pearson Education 2009 Objectives Common uses of database systems. Meaning of the term database. Meaning.
Developing Enterprise Architecture
Seattle Area Software Quality Assurance Group Release and Configuration Management, The Acceleration of Change and Its Contribution To Software Quality.
 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.
M1G Introduction to Database Development 6. Building Applications.
Database Management. ICT5 Database Administration (DBA) The DBA’s tasks will include the following: 1. The design of the database. After the initial design,
Service Transition & Planning Service Validation & Testing
Chapter 8 Evaluating Alternatives for Requirements, Environment, and Implementation.
An Alternative Approach to Interoperability Testing The Use of Special Diagnostic Records in the Context of Z39.50 and Online Library Catalogs William.
Implementation - Part 2 CPS 181s March 18, Pieces of the Site-building Puzzle Page 180, figure 4.1.
Database Design and Management CPTG /23/2015Chapter 12 of 38 Functions of a Database Store data Store data School: student records, class schedules,
Category #2 Bundling and Unbundling Workgroup September 24, 2007.
Module 10 Administering and Configuring SharePoint Search.
1 Geospatial and Business Intelligence Jean-Sébastien Turcotte Executive VP San Francisco - April 2007 Streamlining web mapping applications.
5 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
Z39 Server and Z39.50 Gateway. Z39 Configuration Z39.50 Server Bath Profile conformance has been added to the Z39 Server. Z39 server supports Structure.
ONE-2, SVUC, danZIG & Holdings ZIG July 2000 Poul Henrik Jørgensen, Danish Bibliographic Centre
Extending Access To Information Resource Discovery Service William E. Moen, Ph.D. Kathleen R. Murray, Ph.D. School of Library and Information Sciences.
Introduction to Database Tonga Institute of Higher Education NOS 215.
The future of the catalogue Warwick Cathro Assistant Director- General, Innovation.
BEST Guard – Information Logging. bEST Guard Records all actions executed on an MFP Produkt type: Server based application (software only) Development.
Z39.50 & The Z Texas Profile William E. Moen School of Library and Information Sciences University of North Texas Denton, TX.
Design Reuse Earlier we have covered the re-usable Architectural Styles as design patterns for High-Level Design. At mid-level and low-level, design patterns.
IBM Software Group ® Managing Reusable Assets Using Rational Suite Shimon Nir.
User Modeling and Recommender Systems: Introduction to recommender systems Adolfo Ruiz Calleja 06/09/2014.
Database Management Systems
Open Archive Forum Rachel Heery UKOLN, University of Bath UKOLN is funded by Resource: The Council for Museums, Archives.
Modern Programming Language. Web Container & Web Applications Web applications are server side applications The most essential requirement.
1 Dublin Core in Z39.50: The Bath Profile Paul Miller Interoperability Focus UK Office for Library & Information Networking (UKOLN)
Z39.50 and the ZING Initiatives: MAVIS Users Conference, 2003 November 6, 2003 Larry E. Dixson Library of Congress.
Interoperability and Standards for Bibliographic Applications Poul Henrik Jørgensen Danish Library Centre Telematics for.
1 CS 430: Information Discovery Lecture 26 Architecture of Information Retrieval Systems 1.
Integration of Laserfiche and GIS with GeoDoc ® IS121 Beth Dennis, Urban Crossroads, Inc.
Submitted by: Moran Mishan. Instructed by: Osnat (Ossi) Mokryn, Dr.
JAFER Toolkit Project Oxford University 1 JAFER Java-based high level Z39.50 toolkit Matthew Dovey; Colin Tatham; Antony Corfield; Richard Mawby Oxford.
SQL IMPLEMENTATION & ADMINISTRATION Indexing & Views.
JAFER Toolkit Project Oxford University 1 “A Visual Toolkit For Information Retrieval” Authors: Antony Corfield, Matthew Dovey, Richard Mawby & Colin Tatham.
Robert Worden Open Mapping Software Ltd
Chapter 8 Environments, Alternatives, and Decisions.
BANKING INFORMATION SYSTEMS
Physical Changes That Don’t Change the Logical Design
LOCO Extract – Transform - Load
Introduction to Networking
Ch > 28.4.
MANAGING DATA RESOURCES
MANAGING DATA RESOURCES
Introduction of Week 11 Return assignment 9-1 Collect assignment 10-1
Metadata The metadata contains
Establish, configure and maintain a website/system
Presentation transcript:

Bath Profile - vendor considerations Page 1 The Bath Profile - vendor considerations Rob Bull

Bath Profile - vendor considerations Page 2 What vendors ? Bespoke system developers: –software houses –data providers Library cataloguing system vendors Suppliers of client packages/gateways Developers of other profiles Toolkit suppliers

Bath Profile - vendor considerations Page 3 Software Implications To existing services/systems: –Z39.50 components –database components –user interface components Consideration for new services/systems Maintenance/Administration Toolkits/APIs Decision for which functional area and conformance level to achieve.

Bath Profile - vendor considerations Page 4 Existing Services/Systems Need to look at which functional area to fit into : –server side may be determined by specifications of the database package –client side may be determined by scope of user interface requirements Need to look at which conformance level to fit into : –decide if additional development is necessary to raise current conformance level.

Bath Profile - vendor considerations Page 5 Existing Services/Systems Z39.50 Scan Service: –many systems do not support scan Record Retrieval: –many systems do not support GRS.1 or XML Holdings: –do any systems support the new Holdings profile ? Character set and language negotiation: –very little implementation.

Bath Profile - vendor considerations Page 6 New Services/Systems Look at requirements from customers - see how they align to the profile. Make users/customers aware of the profile and its importance. Look at related national profiles, (e.g, Finnish, CENL, ONE-2, DanZig) for similar conformance. Will database support Character set and language negotiation ?.

Bath Profile - vendor considerations Page 7 Database Systems Database functionality determines much of the target functionality Will the database search capabilities support the profile attribute combinations ? Will the database support suitable indexing for the scan service ?

Bath Profile - vendor considerations Page 8 Maintenance/Administration Client side: –predictability of server behaviour –conformance to the profile should reduce administration and the need to set up individual tables of attributes etc. Server side: –new indexes ? –supported search capability ? –Character sets ?

Bath Profile - vendor considerations Page 9 Functionality/Conformance There is no easy way of determining within the Z39.50 protocol the level of functionality or conformance supported by a client or server : –could be easily crafted on the Init service using a simple XML definition –use of XML is being tested in the ONE-2 project.

Bath Profile - vendor considerations Page 10 Toolkits No new crafted ASN.1 in the profile: –should not impact on popular freeware Z39.50 toolkits, for example those of Crossnet and Index Data. –vendors who use other Z39.50 toolkits will need to establish if there is support for GRS.1, character set and language negotiation etc.

Bath Profile - vendor considerations Page 11 Questions Is this the big one... ? –…or just another in a line of profiles, and should I wait to see what emerges next year ? Who is going to prove the profile is successful ? –ONE-2 project will address a significant portion, but these are mainly bespoke systems and not COTS systems.

Bath Profile - vendor considerations Page 12 Questions What about the new attribute architecture being designed ? How do I create a companion profile for my community ? –CIMI is considering writing guidelines for profile development.

Bath Profile - vendor considerations Page 13 Benefits Conformance to a profile ensures predictability to developers and users, –removes the syndrome: “code is there because that’s how that system behaves” Provides a stable basis to extend in the future.

Bath Profile - vendor considerations Page 14 Drawbacks At some time, the line of profiles being developed has to stop to enable vendors the opportunity to catch up with their developments. Is a low level of conformance really just an opt-out escape clause, or should developers and vendors bite the bullet and aim for a higher conformance level.