Z39.50 is a standard for search and retrieval of many types of information such as text, images and multimedia. Z39.50 is a national and international standard defining a protocol for computer-to-computer information retrieval. It enables information seekers to search different systems on a network or the Internet through the use of a single user interface.
Frankly speaking Z39.50 is a outdated protocol which is not much in use now a days. The z39.50 enable user to do federated search, means search various databases through a single user interface and single query. Now a days many other protocols came into existence like SRU/SRW which have significant seraching and retrieval functions.
ABOUT “Z39.50”
ANSI/NISO Z39.50 is the American National Standard Information Retrieval Application Service Definition and Protocol Specification for Open Systems Interconnection. The National Information Standards Organization (NISO), an American National Standards Institute (ANSI) accredited standards developer that serves the library, information, and publishing communities, approved the original standard in 1988 (referred to as Z39.50-1988 or Version 1). NISO published a revised version of the standard in 1992 (referred to as Z39.50-1992 or Version 2).
ANSI/NISO Z39.50 defines a standard way for two computers to communicate for the purpose of information retrieval. Z39.50 makes it easier to use large information databases by standardizing the procedures and features for searching and retrieving information. Specifically, Z39.50 supports information retrieval in a distributed, client and server environment where a computer operating as a client submits a search request (i.e., a query) to another computer acting as an information server. Software on the server performs a search on one or more databases and creates a result set of records that meet the criteria of the search request. The server returns records from the result set to the client for processing. The power of Z39.50 is that it separates the user interface on the client side from the information servers, search engines, and databases. Z39.50 provides a consistent view of information from a wide variety of sources, and it offers client implementors the capability to integrate information from a range of databases and servers.
ANSI/NISO Z39.50 can be implemented on any platform. This means that Z39.50 enables different computer systems -- with different operating systems, hardware, search engines, database management systems -- to interoperate and work together seamlessly. A Z39.50 implementation enables one interface to access multiple systems providing end users with nearly transparent access to other systems. Users access multiple systems with the familiar commands and displays of their own local systems. New commands and search techniques do not have to be learned. The results of the search are presented on the local system -- again, in the formats and styles users are accustomed to.
One of the strengths of ANSI/NISO Z39.50 is that it is an American National Standard. NISO developed and maintains Z39.50 using consensus procedures approved by ANSI, the principal coordinator of voluntary standardization in the United States. Z39.50 is not a proprietary standard and will continue to be responsive to the needs of the implementors that use the standard and the information consumers that benefit from its implementation.
Library 2.0
Library 2.0 is a loosely defined model for a modernized form of library service that reflects a transition within the library world in the way that services are delivered to users. The focus is on user-centered change and participation in the creation of content and community. The concept of Library 2.0 borrows from that of Business 2.0 and Web 2.0 and follows some of the same underlying philosophies. This includes online services like the use of OPAC systems and an increased flow of information from the user back to the library.
With Library 2.0, library services are constantly updated and reevaluated to best serve library users. Library 2.0 also attempts to harness the library user in the design and implementation of library services by encouraging feedback and participation. Proponents of this concept sometimes referred to as Radical Trust expect that the Library 2.0 model for service will ultimately replace traditional, one-directional service offerings that have characterized libraries for centuries.
1. Over View:-
The term "Library 2.0" was coined by Michael Casey on his blog Library Crunch as a direct spin-off of the terms Business 2.0 and Web 2.0. Casey suggested that libraries, especially public libraries, are at a crossroads where many of the elements of Web 2.0 have applicable value within the library community, both in technology-driven services and in non-technology based services. In particular, he described the need for libraries to adopt a strategy for constant change while promoting a participatory role for library users.
Library 2.0 made its conference debut at Internet Librarian 2005 in October, 2005, when Michael Stephens of Saint Joseph County Public Library addressed the idea in relation to the typical library website.
A September, 2006, article in Library Journal, titled “Library 2.0 Service for the next-generation library,” begins by expressing the benefit of Library 2.0 to library administrators and taxpayers as providing “more efficient ways of delivering services to achieve greater returns on financial investments.” The article continued by asserting that the much discussed Library 2.0 is important for librarians as it may radically change our customer service and interaction.
With Library 2.0, library services are frequently evaluated and updated to meet the changing needs of library users. Library 2.0 also calls for libraries to encourage user participation and feedback in the development and maintenance of library services. The active and empowered library user is a significant component of Library 2.0. With information and ideas flowing in both directions from the library to the user and from the user to the library – library services have the ability to evolve and improve on a constant and rapid basis. The user is participant, co-creator, builder and consultant whether the product is virtual or physical.
2. Key Principles:-
• Browser + Web 2.0 Applications + Connectivity = Full-featured OPAC
• Harness the library user in both design and implementation of services
• Library users should be able to craft and modify library provided services
• Harvest and integrate ideas and products from peripheral fields into library service models
• Continue to examine and improve services and be willing to replace them at any time with newer and better services.
3. Concerns and Considerations:-
Some concerns about Library 2.0 relate to access to technology, privacy and security. For example, Casey and Savastinuk suggest allowing patrons to tag or blog anonymously. In 2006, Steve Lawson, humanities liaison librarian, wrote a blog post entitled “A Library 2.0 skeptic's reading list” that collected links to blogs which discuss these concerns. Steve says “I'm not anti-Library 2.0 . I like to think of Library 2.0 as a continuing conversation about the future of libraries, and it makes sense to me to try to round up some voices that challenge Library 2.0 conventional wisdom.”
4. The Library 2.0 Online Public Access Catalog:-
Library 2.0 is a new way of providing library service through new Internet technologies, with emphasis on “user-centered” change and interaction. Like Web 2.0, a full-featured Library 2.0 OPAC gets better the more that users are involved in the process of interacting with the catalog and sharing content.
Librarians have been working to retool library catalogs in order to make them more useful for patrons to find, organize, and interact with information in a way that has infinite potential for user customization. These new types of catalogs are a shift from "isolated information silos" to "interlinked computing platforms." In the past the information flow was mostly one way, from library to user. With new web tools information can be released to flow in every direction (library to user, user to library, library to library, and user to user).
Jessamyn West, on her librarian.net website, authored “What We Want: An OPAC Manifesto,” which broke down the needs of library staff, geeks, and users in their OPAC. These valuable suggestions inform librarians of the flexibility, customizability and plain language approach that is desired by users in their OPAC. Librarians should be aware of these issues so that planning for improvement can begin.
5. The debate surrounding Library 2.0:-
Library 2.0 has been a source of debate in the blogosphere. Some librarian bloggers have argued that these key principles are not new and have been part of the service philosophies of many library reformers since the 19th century. Others are calling for more concrete examples of how libraries can get to Library 2.0. Walt Crawford, for example, argues that Library 2.0 comprises a combination of tools and attitudes which are excellent ideas and not new to librarianship, a few business- and tool-focused attitudes which will not serve all users and user communities, and incorrectly places libraries as the appropriate source for all users to gather all information.
Proponents of Library 2.0, such as Stephen Abram, Michael Stephens, Paul Miller and others, have spoken to these criticisms, arguing that while individual pieces of Library 2.0 may not be entirely new, the convergence of these service goals and ideas with many new Web 2.0 technologies has led to a new generation of library service. This includes the use of online social networks by libraries.
If you need more then plz give me your E-mail ok Kishore bye
Rajnish ji, thanks for your valuable comments on this discussion forum.However, i am still in dark about the practical aspects of this protocol. if two computer systems(here the server and the client) have to establish a session, both should have Z 39.50 protocol enabled database(whether OPAC or full-text database)?what kind of database query language or structure is needed? or it does not depend on the programmes/applications(whether SQL or Access etc.)?