1 CS 502: Computing Methods for Digital Libraries Lecture 19 Interoperability Z39.50.

Slides:



Advertisements
Similar presentations
OAI from 50,000 Feet OAI develops and promotes interoperability solutions that aim to facilitate the efficient dissemination of content. Begun in 1999.
Advertisements

Retrieval of Information from Distributed Databases By Ananth Anandhakrishnan.
Database System Concepts and Architecture
CNRIS CNRIS 2.0 Challenges for a new generation of Research Information Systems.
1 Building the NSDL William Y. Arms Cornell University Thinking aloud about the NSDL.
ICS (072)Database Systems: A Review1 Database Systems: A Review Dr. Muhammad Shafique.
1 Introduction to XML. XML eXtensible implies that users define tag content Markup implies it is a coded document Language implies it is a metalanguage.
Managing Data Resources
1 CS 502: Computing Methods for Digital Libraries Lecture 22 Web browsers.
Building Reliable Distributed Information Spaces Carl Lagoze CS /22/2002.
1 CS 430 / INFO 430 Information Retrieval Lecture 13 Architecture of Information Retrieval Systems.
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 8 Requirements I.
© Tefko Saracevic, Rutgers University1 metadata considerations for digital libraries.
SCORM-NSDL Workshop May 18, Educational Materials are Scattered across the Internet NASA Math Forum State standards Scientific American Ask.
1 CS 502: Computing Methods for Digital Libraries Lecture 22 Repositories.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 1: Introduction to Windows Server 2003.
CS CS 5150 Software Engineering Lecture 13 System Architecture and Design 1.
Federated Digital Library Architecture and Distributed Resource Discovery Carl Lagoze CS
“DOK 322 DBMS” Y.T. Database Design Hacettepe University Department of Information Management DOK 322: Database Management Systems.
1 An introduction to the NSDL William Y. Arms Cornell University.
1 CS 502: Computing Methods for Digital Libraries Lecture 4 Identifiers and Reference Links.
Basic Concepts Architecture Topology Protocols Basic Concepts Open e-Print Archive Open Archive -- generalization of e-print Data Provider and Service.
Chapter 4 Database Management Systems. Chapter 4Slide 2 What is a Database Management System (DBMS)?  Database An organized collection of related data.
CORDRA Philip V.W. Dodds March The “Problem Space” The SCORM framework specifies how to develop and deploy content objects that can be shared and.
Web Services Michael Smith Alex Feldman. What is a Web Service? A Web service is a message-oriented software system designed to support inter-operable.
Dienst Distributed Networked Publishing Carl Lagoze Digital Library Scientist Cornell University.
An Architecture for Online Information Integration on Concurrent Resource Access on a Z39.50 Environment Michalis Sfakakis 1 and Sarantos Kapidakis 2 An.
INTRODUCTION TO WEB DATABASE PROGRAMMING
CONTI’2008, 5-6 June 2008, TIMISOARA 1 Towards a digital content management system Gheorghe Sebestyen-Pal, Tünde Bálint, Bogdan Moscaliuc, Agnes Sebestyen-Pal.
Teaching Metadata and Networked Information Organization & Retrieval The UNT SLIS Experience William E. Moen School of Library and Information Sciences.
Database Design - Lecture 1
1 The NSDL: A Case Study in Interoperability William Y. Arms Cornell University.
Postacademic Interuniversity Course in Information Technology – Module C1p1 Contents Data Communications Applications –File & print serving –Mail –Domain.
World Wide Web Hypertext model Use of hypertext in World Wide Web (WWW) WWW client-server model Use of TCP/IP protocols in WWW.
DINI „Electronic Publishing Group“ DINI – Certificate Document and Publication Repositories “Electronic Publishing Group“
Linking electronic documents and standardisation of URL’s What can libraries do to enhance dynamic linking and bring related information within a distance.
Cookies Web Browser and Server use HTTP protocol to communicate and HTTP is a stateless protocol. But for a commercial website it is required to maintain.
1 CS 430 / INFO 430 Information Retrieval Lecture 24 Architecture of Information Retrieval Systems.
Lesson Overview 3.1 Components of the DBMS 3.1 Components of the DBMS 3.2 Components of The Database Application 3.2 Components of The Database Application.
1 CS 430 Database Theory Winter 2005 Lecture 2: General Concepts.
Kurt Maly Department of Computer Science Old Dominion University Norfolk, Virginia 23529, USA Digital Libraries, OAI and Free Software.
Alternative Architecture for Information in Digital Libraries Onno W. Purbo
World Wide Web “WWW”, "Web" or "W3". World Wide Web “WWW”, "Web" or "W3"
Saving State on the WWW. The Issue  Connections on the WWW are stateless  Every time a link is followed is like the first time to the server — it has.
SWE 513: Software Engineering
Copyright (c) 2014 Pearson Education, Inc. Introduction to DBMS.
No Longer Under Our Control? The Nature and Role of Standards in the 21 st Century Library William E. Moen School of Library and Information Sciences Texas.
A/WWW Enterprises 15 July 1996 Implementing Queries with Z39.50 A. Warnock A/WWW Enterprises
Introduction to Databases Dr. Osama AL Rababah. Objectives In this capture you will learn: Some common uses of database systems. The characteristics of.
2/22/2016J Ammerman1 Open Archives Initiative What is it? What’s it good for?
1 CS 430: Information Discovery Lecture 26 Architecture of Information Retrieval Systems 1.
Directory Services CS5493/7493. Directory Services Directory services represent a technological breakthrough by integrating into a single management tool:
Z39.50 A Basic Introduction Kathleen R. Murray, Ph.D. William E. Moen, Ph.D. May 2002.
The ___ is a global network of computer networks Internet.
Active Directory Domain Services (AD DS). Identity and Access (IDA) – An IDA infrastructure should: Store information about users, groups, computers and.
VIEWS b.ppt-1 Managing Intelligent Decision Support Networks in Biosurveillance PHIN 2008, Session G1, August 27, 2008 Mohammad Hashemian, MS, Zaruhi.
1 CS 430: Information Discovery Lecture 26 Architecture of Information Retrieval Systems.
1 CS 430: Information Discovery Lecture 13 Case Study: the NSDL.
Database Principles: Fundamentals of Design, Implementation, and Management Chapter 1 The Database Approach.
WEB SERVICES From Chapter 19 of Distributed Systems Concepts and Design,4th Edition, By G. Coulouris, J. Dollimore and T. Kindberg Published by Addison.
Database Management:.
CS 501: Software Engineering Fall 1999
CS 430 / INFO 430 Information Retrieval
OUTLINE Basic ideas of traditional retrieval systems
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Database System Concepts and Architecture.
WEB API.
Database Design Hacettepe University
Database Management Systems
WEB SERVICES From Chapter 19, Distributed Systems
Presentation transcript:

1 CS 502: Computing Methods for Digital Libraries Lecture 19 Interoperability Z39.50

2 Administration

3 Digital Library Systems Repositories Identification Systems Search Systems Users Services Collections

4 Digital Library Systems: Independent Collections and Services

5 Interoperability in Heterogeneous Distributed Systems The Computing Challenge To build large-scale distributed systems where: The components are managed by many different organizations Every system is a legacy system

6 The Computing Challenge To build large-scale distributed systems where: The components are managed by many different organizations Every system is a legacy system Every Technical Decision has an Organizational Context Interoperability in Heterogeneous Distributed Systems

7 Dienst: Broadcast Distributed Search

8 Backup index server replicates all index servers used by user interface when primary is down backup index

9 Regional Structure central collection server regional collection server regional merged index server

10 Approaches to standardization The conventional approach  Technical leaders develop standards: protocols, formats, etc. - Everybody implements the standards. - This creates an integrated, distributed system. Unfortunately...  Standards are expensive to adopt.  Concepts are continually changing.  Systems are continually changing.

11 Function versus cost of acceptance Function Cost of acceptance

12 Function versus cost of acceptance Example: text markup Function Cost of acceptance SGML ASCII HTML XML

13 Function versus cost of acceptance Example: identifiers Function Cost of acceptance URL Domain names URN

14 Federated digital library Definition Federated digital library. A group of digital libraries that support common standards and services, thus providing interoperability and a coherent service to users. In a federation, the partners may have different systems, but must agree on: technical standards (formats, protocols, interfaces, object models, metadata, etc.) policies (financial agreements, intellectual property, security, privacy, etc.)

15 The Z federation Libraries that agree on: Anglo American Cataloging Rules MARC format Z39.50 protocol Bib1 search query A successful federation. An important legacy system.

16 Aims of Z39.50 Permits one computer, the client, to search and retrieve information on another, the database server Important both technically and for its wide use in library systems Most development has concentrated on bibliographic data Most implementations emphasize searches that use a bibliographic set of attributes to search databases of MARC records

17 Sample query In the database named "Books" find all records for which the access point title contains the value "evangeline" and the access point author contains the value "longfellow."

18 Z39.50 principles Abstract view of database searching. Server stores a set of databases with searchable indexes Interactions are based on a session The client opens a connection with the server, carries out a sequence of interactions and then closes the connection. During the course of the session, both the server and the client remember the state of their interaction.

19 State Z39.50 The server carries out the search and builds a results set Server saves the results set. Subsequent message from the client can reference the result set. Thus the client can modify a large set by increasingly precise requests, or can request a presentation of any record in the set, without searching entire database.

20 Z39.50 principles Client is a computer. End-user applications need a user interface for communication with the user. The protocol makes no statements about the form of that user interface or how it connects to the Z39.50 client.

21 Z services init -- client connects to the server and exchanges initial information, e.g., preferred message size explain -- client inquires of the server what databases are available for searching, the fields that are available, the syntax and formats supported, and other options search -- client presents a query to a database choices of syntax for specifying searches only Boolean queries widely implemented one or more records may be returned to the client

22 Z services manipulation of results sets -- e.g., sort or delete present -- requests the server to send specified records from the results set to the client in a specified format options: for controlling content and formats for managing large records or large results sets

23 Technical history Z39.50 Developed for X.25 networks (connection orientation), conversion to run over TCP fitted later Original concept in days when repeating a search was expensive computation (about 1980) WAIS is a stateless derivative of an early version of Z39.50