SRW/U: Re-Introduction SRW is a Web Services based Information Retrieval Protocol Motivations: Create an easy to implement protocol with the power of Z39.50.

Slides:



Advertisements
Similar presentations
View from Elsevier NISO Metasearch Initiatives Meeting May 7, 2003 M. Krellenstein.
Advertisements

Searching Options and Result Sets Sara Randall Endeavor Information Systems October 30, 2003.
Z39.50 as a Web Service Ralph LeVan Research Scientist.
Schedule of Releases (since Tromso meeting) and New Access Interfaces.
Z39.50 as a Web Service Ralph LeVan Research Scientist.
A centre of expertise in digital information management UKOLN is supported by: SRU: An overview of the SRU protocol and how it can be used.
Searching very large bodies of data using a transparent peer-to-peer proxy Mike Taylor and Marc Cromme, Index Data
Delivering MARC/XML records from the Library of Congress catalogue using the open protocols SRW/U and Z39.50 Mike Taylor, Index Data
Reinventing using REST. Anything addressable by a URI is called a resource GET, PUT, POST, DELETE WebDAV (MOVE, LOCK)
General introduction to Web services and an implementation example
Ray Denenberg Ralph LeVan Interoperability Standards & Searching Multiple Repositories Workshop 20 March 25, 2006; Washington.
XML Configuration Access Protocol (XCAP) Jonathan Rosenberg dynamicsoft.
ZML  ZNG  ZING “Z39.50 over XML”  “Z39.50 Next Generation”  “Z39.50-international: Next Generation”
Lucene Part3‏. Lucene High Level Infrastructure When you look at building your search solution, you often find that the process is split into two main.
Ray Denenberg Ralph LeVan Workshop 20 March 25, 2006; Washington Metasearch - the NISO Initiative.
14 October 2003ADASS 2003 – Strasbourg1 Resource Registries for the Virtual Observatory R.Plante (NCSA), G. Greene (STScI), R. Hanisch (STScI), T. McGlynn.
ELAG 2005 / Workshop 1: ZING Geneva, June 2005 Ole Husby, BIBSYS.
Brokering Mathematical Services Through a Web Registry.
Web Services By Ethan Justin Yuli. Web Services in Action Information through Integration (Google Example)Google Example What do Web.
CSE 636 Data Integration Web Services.
Introduction to Structured Query Language (SQL)
Federated Searching: The ABC’s of HSE, XML, & Z39.50 Harry Samuels Product Manager Linking & Searching August 27, 2004.
Overview of Search Engines
Integrating Complementary Tools with PopMedNet TM 27 July 2015 Rich Schaaf
Positioning Z39.50 in the Networked Library Standards for Building Sustainable Services William E. Moen School of Library and Information Sciences Texas.
Z39.50 for Finding It All William E. Moen School of Library and Information Sciences Texas Center for Digital Knowledge University of North Texas Denton,
M i SMob i S Mob i Store - Mobile i nternet File Storage Platform Chetna Kaur.
Enabling Embedded Systems to access Internet Resources.
OASIS ebXML Registry Standard Open Forum 2003 on Metadata Registries 10:30 – 11:15 January 20, 2003 Kathryn Breininger The Boeing Company Chair, OASIS.
Web Feature Service – What and How? Ian Painter - Snowflake Software.
ELAG 2004  Work Shop on ZING Bill Oldroyd, Animator British Library Janifer Gatenby, Scribe OCLC PICA, Leiden, Netherlands.
WikiD (Wiki/Data) Jeffrey A. Young OCLC Office of Research Presented by Stu Weibel CERN OAI4 Geneva, Switzerland 20 October 2005.
Lecture Set 14 B new Introduction to Databases - Database Processing: The Connected Model (Using DataReaders)
1 Technologies for distributed systems Andrew Jones School of Computer Science Cardiff University.
ISO ILL, NISO NCIP or OpenURL? ELAG 2005 workshop 2 report Ed. Poul Henrik Jørgensen.
A Web Services Approach for Search and Retrieve The Next Generation Z39.50 Access 2004, October 13-16, 2004, Halifax, Nova Scotia William E. Moen School.
Thanks to Bill Arms, Marti Hearst Documents. Last time Size of information –Continues to grow IR an old field, goes back to the ‘40s IR iterative process.
1.NET Web Forms Web Services © 2002 by Jerry Post.
Web Services Based on SOA: Concepts, Technology, Design by Thomas Erl MIS 181.9: Service Oriented Architecture 2 nd Semester,
XML Web Services Architecture Siddharth Ruchandani CS 6362 – SW Architecture & Design Summer /11/05.
Introduction to Web Services Eric Lease Morgan University Libraries of Notre Dame June 24, 2005.
Web: Minimal Metadata for Data Services Through DIALOGUE Neil Chue Hong AHM2007.
Search Engine Architecture
Lecture Set 14 B new Introduction to Databases - Database Processing: The Connected Model (Using DataReaders)
OCLC Online Computer Library Center Interoperability Standards & Searching Multiple Repositories Ralph LeVan/OCLC Ray Denenberg/Library of Congress.
Efficient RDF Storage and Retrieval in Jena2 Written by: Kevin Wilkinson, Craig Sayers, Harumi Kuno, Dave Reynolds Presented by: Umer Fareed 파리드.
Data Manipulation Jonathan Rosenberg dynamicsoft.
Ray Denenberg Rob Sanderson “ Key Standards Updates ” SRU Project Briefing April 4, 2006; Washington.
CNI, 4th April 2006 Slide 1 Key Standards Update: SRU (“Technical” Details) Dr. Robert Sanderson Dept. of Computer Science University of Liverpool
WEB SERVICE DESCRIPTION LANGUAGE (WSDL). Introduction  WSDL is an XML language that contains information about the interface semantics and ‘administrivia’
An Introduction to Web Services Web Services using Java / Session 1 / 2 of 21 Objectives Discuss distributed computing Explain web services and their.
WSDL Specification WSDL = Web Service Description Language Similar to ASN.1 – describes the abstract on the wire data structures Multiple bindings to on.
System/SDWG Update Management Council Face-to-Face Flagstaff, AZ August 22-23, 2011 Sean Hardman.
Web Services An Introduction Copyright © Curt Hill.
Next Generation Z39.50 A Web Services Approach for Search and Retrieve 6 th Annual State GILS Conference, March 31 – April 3, 2004, Raleigh, NC William.
Z39.50 and the ZING Initiatives: MAVIS Users Conference, 2003 November 6, 2003 Larry E. Dixson Library of Congress.
TapirLink: Enabling the transition to TAPIR Renato De Giovanni TDWG 2007.
1 CS 430: Information Discovery Lecture 26 Architecture of Information Retrieval Systems 1.
Apache Solr Dima Ionut Daniel. Contents What is Apache Solr? Architecture Features Core Solr Concepts Configuration Conclusions Bibliography.
International Planetary Data Alliance Registry Development and Coordination Project Report 7 th IPDA Steering Committee Meeting July 13, 2012.
The AstroGrid-D Information Service Stellaris A central grid component to store, manage and transform metadata - and connect to the VO!
A Semi-Automated Digital Preservation System based on Semantic Web Services Jane Hunter Sharmin Choudhury DSTC PTY LTD, Brisbane, Australia Slides by Ananta.
Java Web Services Orca Knowledge Center – Web Service key concepts.
Jonathan Rosenberg dynamicsoft
z/Ware 2.0 Technical Overview
Middleware independent Information Service
Introduction to Persistent Identifiers
Wsdl.
Building a Database on S3
WEB SERVICES From Chapter 19, Distributed Systems
Presentation transcript:

SRW/U: Re-Introduction SRW is a Web Services based Information Retrieval Protocol Motivations: Create an easy to implement protocol with the power of Z39.50 Need for a generic IR web service Use existing off the shelf solutions where possible Re-evaluate Z39.50 “a good idea at the time” baggage Avoid library-centric preconception More Information: me: : Rob Sanderson

SRW/U: Summary SRW is the SOAP binding. (HTTP POST of XML for XML) SRU is the REST binding. (HTTP GET for XML) Current stable version is 1.1, released February Three Operations Available: Explain Retrieve service description SearchRetrieve Search, sort and retrieve records Scan Retrive ordered list of index terms Rob Sanderson

SRW/U: Explain Operation Purpose: Retrieve Service Description Request: Very Simple Not quite so simple as version 1.0 Response: Very Simple Not quite so simple as version 1.0 ZeeRex record wrapped in standard metadata ZeeRex: Z39.50 Explain Explained and Re-Engineered in XML XML service description tailored for Z39.50 and SRW Rob Sanderson

SRW/U: SearchRetrieve Operation Purpose: Search, Sort and Retrieve Records Request: Query in CQL (a string) Record Schema Identifier and XPath for sub-record level Sort specification (also a string) Result set manipulation (where to start, time to live etc.) Response: List of Records Result set information (identifier, time to live) Potentially some diagnostics All records are returned in XML. All identifiers are URIs or published aliases. Rob Sanderson

SRW/U: Scan Operation Purpose: Retrieve Ordered List of Indexed Terms Request: CQL to determine index and starting point Number of terms Relative location of starting point in term list Response: List of Terms Potentially some diagnostics Term: Value Frequency in database Alternative for display Rob Sanderson

CQL: Introduction Purpose: Simple and Intuitive but still Expressive Queries Language Components: Index dc.creator Relation any Term “sanderson denenberg” == SearchClause Boolean and == Triple Relation/Boolean Modifiers Parentheses for precedence Context Sets for disambiguation/extension Rob Sanderson

SRW/CQL: Metasearch Requirements Requirements: Result Set Metadata (including Links/Branding) Record Metadata Configurable Authentication Minimal Statefulness Standard, Extensible Query Language Ability to Handle Ranking Algorithms Multiple Resources per Message I'll add: Fairly Easy to Implement and: Builds on Known Specifications Rob Sanderson

SRW/CQL: Requirements Met Extensible Metadata: All messages have space for extensions Records and Terms have additional space Authentication handled through this space as tokens All Identifiers are URIs Extensible Query Language: CQL Context sets can be defined by anyone No requirement to register anything Work already begun to facilitate relevance ranking Minimal State Requirements: HTTP, not persistent Z39.50 connections Only state required is for result sets, which aren't mandatory Rob Sanderson

SRW/CQL: Requirements Not Met Single Database/Server Model: SRW only queries one database at once and isn't 'expensive' Could be implemented (badly) as an extension Or 'SRW++' which wraps multiple SRW messages Metasearch Model Once More: Rob Sanderson Client MetaSearch Database1 Database2 Database3 Database4 A B

SRW++: MetaSearching Protocol Multiple Resource Single Query: Rob Sanderson Client MetaSearch Database1 Database2 Database3 Database4 A AB Here B is acting as A, a MetaSearch Protocol! So A must be at least a superset of B... All requirements for B are requirements for A. Hence SRW++. B

SRW++: Requirements Rob Sanderson Database1 Database2 MetaSearch AB Client A[B] Control of MetaSearch Through A: Must at least allow selection of remote resources Must, therefore, advertise available remote resources Must allow selection of combined or separate result sets Fine grained control of remote resource? eg record schema Incremental Updates or Single Response: HTTP is not asynchronous, but can be faked with tokens If not incremental, then no user feedback If incremental, then constantly combining and reranking... Or result sets aren't combined, just republished If not some combination, result set metadata is lost

Conclusions Rob Sanderson SRW + CQL: Fits the requirements for protocol B today Built on existing protocols and standards Extensible at many granularities Three primary operations, available via SOAP or REST Several OSS implementations available Right Now SRW++: Extend SRW to handle multiple database searching Enable control of MetaSearcher behaviour Asynchronous/Incremental vs single message NISO Taskgroups to inform the development