1 / 18

NISO Metasearch Initiative: Distributed Service Registries Workshop

This workshop provides an overview of the NISO Metasearch Initiative, its history, purpose, and scope, as well as the conceptual model, collection descriptions, and service descriptions. It focuses on enabling the discovery and retrieval of remotely maintained content.

justinbjones
Télécharger la présentation

NISO Metasearch Initiative: Distributed Service Registries Workshop

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NISO Metasearch Initiative Registries Robert Sanderson Dept. of Computer Science University of Liverpool azaroth@liv.ac.uk http://www.niso.org/committees/MetaSearch-info.html (With thanks to Pete Johnston) Distributed Service Registries Workshop, 14-15 July 2005 Slide 1

  2. Overview NISO MI History Purpose and Scope Conceptual Model Collection Descriptions Service Descriptions Registries Distributed Service Registries Workshop, 14-15 July 2005 Slide 2

  3. NISO Metasearch Initiative History • First meeting May 7-8, 2003 in Denver, CO • Initiated by the Content Providers, not the Metasearchers or NISO • Worried about how to handle the load generated by overly broad metasearch strategies • Ebsco, Thomson Gale, Elsevier • Also present: Library Systems Vendors, Metasearchers, NISO Distributed Service Registries Workshop, 14-15 July 2005 Slide 3

  4. NISO Metasearch Initiative History • Initial Meeting topics: • Access Management • Usage Statistics • Searching Options • Metasearcher Identification • Resource Description • Result Set Management Distributed Service Registries Workshop, 14-15 July 2005 Slide 4

  5. NISO Metasearch Initiative History • Jenny Walker (Ex Libris) and Andrew Pace (NCSU) • Three task groups set up • TG1: Access Management • (Mike Teets, OCLC) • TG2: Collection and Service Description • (Juha Hakala, Helsinki University/FinlandNational Library) • TG3: Search and Retrieval • (Matt Goldner, OCLC; Sara Randall, Endeavor) Distributed Service Registries Workshop, 14-15 July 2005 Slide 5

  6. NISO Metasearch Initiative History • Metasearch Workshop, Washington DC, October 2003 • MI Face to face meeting, Raleigh-Durham, April 2004 • MI Face to face meeting, Raleigh-Durham, April 2005 • Plus, of course, email list discussions • And frequent conference calls Distributed Service Registries Workshop, 14-15 July 2005 Slide 6

  7. Purpose and Scope Focus on Task Group 2, Collection and Service Descriptions. Purpose: To enable the discovery of appropriate, remotely maintained content and a means of retrieving that content. • Discover collections of potential interest • Identify a collection • Select one or more collections from those discovered • Identify services that provide access to the collection • Select a service with with to interact • Interact with service Distributed Service Registries Workshop, 14-15 July 2005 Slide 7

  8. Purpose and Scope Scope: • While the Initiative concerns metasearch, the scope of interest for TG2 is actually enabling retrieval of items. • Need descriptions of collections and of services that provide access to them • Electronic services only, not physical services • Content services only, not transactional services • Collections and services, not agents Distributed Service Registries Workshop, 14-15 July 2005 Slide 8

  9. Conceptual Model • Collections: • contain one or more Items • contain zero or more Collections • are made available by zero or more Services • Services: • make available exactly one Collection Distributed Service Registries Workshop, 14-15 July 2005 Slide 9

  10. Conceptual Model Conceptual Model Diagram: For those of you who like UML Distributed Service Registries Workshop, 14-15 July 2005 Slide 10

  11. Conceptual Model Example: is-available-at Service Collection Service has-part has-part is-available-at Collection Collection Service is-available-at has-part has-part Collection Collection Service is-available-at Distributed Service Registries Workshop, 14-15 July 2005 Slide 11

  12. Collection Descriptions • Description schema builds on Dublin Core Collection Description Application Profile (DC CD AP) • Provides a core set of collection description properties, not a completely comprehensive one • Suitable for collection discovery across a broad range, rather than item discovery • NISO MI primarily addressing 'library' style collections, with some additional requirements (strength/completeness) Distributed Service Registries Workshop, 14-15 July 2005 Slide 12

  13. Collection Descriptions • Interesting recent scoping questions: • Are both a collection description of a library's collection (physical books) and a collection description of the metadata about those books (electronic records) required? (is-described-by field) • Should an electronic full text collection be described in a different document to a collection summarising the items? • Abstracting and Indexing services' collections? Distributed Service Registries Workshop, 14-15 July 2005 Slide 13

  14. Service Descriptions • Description schema: ZeeRex • “Z39.50's Explain Explained, and Re-Engineered in XML” • [Search and] Retrieval Services, not any Service • Semantics of service, not syntax • Eg: record schemas, access points, server capabilities • Vs: WSDL, UDDI, ASN.1/BER, XML Schema, SOAP • Need implementation of protocol before you can interact with a service via that protocol – don't need syntax stored in registry, just the semantics. Distributed Service Registries Workshop, 14-15 July 2005 Slide 14

  15. Service Descriptions Purpose is to enable discovery and usage of appropriate services Thus needs to include 'WSDL' like fields such as host, port, path/database name Has general information to allow the record to be useful without the associated collection description (title, description etc) Also has metadata fields for harvesting source, last update Z39.50 and SRW/U oriented, but capable of describing all the protocols and retrieval methods identified by TG2 Distributed Service Registries Workshop, 14-15 July 2005 Slide 15

  16. Registries Finally, you say, he gets to the Registries bit... Actually, the MI doesn't consider a registry implementation in scope, just recommended best practice documents, especially as many of the members of the working groups are from commercial organisations with their own internal requirements and confidential data. However discussions to ensure that the documents meet the requirements have gone on ... (and on, and on, and on at times) Distributed Service Registries Workshop, 14-15 July 2005 Slide 16

  17. Some Registry Requirements Search fields in Collection Description Search fields in Service Description Cross search of Service and Collection attributes (collection about fish that has a service with a title access point) Interaction via standard protocols for search/retrieve (SRW/U, Z39.50) Harvestable (OAI-PMH) Discovery strategy for new services Distributed Service Registries Workshop, 14-15 July 2005 Slide 17

  18. Main References • NISO MI: http://www.niso.org/committees/MS_initiative.html • DC CD: http://dublincore.org/groups/collections/ • ZeeRex: http://explain.z3950.org/ Distributed Service Registries Workshop, 14-15 July 2005 Slide 18

More Related