Open Archives Initiative Protocol for Metadata Harvesting.
•digital library interoperability
• effective information dissemination
• simpler than z39.50
• impact on cataloging more interesting than its technical details
• works with XML and descriptive metadata
• DLO = document like object
• purpose: move metadata within the Web
• client-server model
• "one stop shopping"
• enables collaboration
• developed from a desire for interoperability betw. self-publishing archives and repositories
NOT:
• open access application itself
• an archive standard
• the same as Dublin Core metadata or initiative
• a protocol for searching cross-repository
Todd Miller, Federated Searching: Put It in Its Place
"Federated search, the new technological kid on the block, and the venerable library catalog should have some sort of relationship with each other."
I'm not sure exactly what this means. "the universe of available content is no longer limited to that stored within the library walls." If a person is searching the library, then they are looking for items that the library has. If a person just wants an answer, it doesn't matter if the library has it or not. Although, not addressed in this article, is the quality - finding answers on Google does not ensure they are correct answers.
The Truth About Federated Searching
"list of the five most commonly repeated misconceptions about federated searching."
•authentication...can be a problem
•comparing results to eliminate duplicates...not so much.
•relevant ranking, not perfect
•software will need to be freq. updated
•interoperatiblity
Lynch, Clifford A. (1997). The Z39.50 Information Retrieval Standard, Part 1
As usual, I have a fuzzy idea of what z39.50 is without actually seeing it in action.
from http://www.biblio-tech.com/html/z39_50.html:
The typical (simplified) search process involved in a Z39.50 session is as follows:
* OPAC user selects Target library (Z-server) from an OPAC menu.
* OPAC user enters search terms
* OPAC software sends search terms and Target library details to a “Z-client” a piece of software usually running as part of the library system.
* Z-client translates the search terms into “Z-speak” and contacts the Target library’s Z-server software.
* There is a preliminary negotiation between the Z-client and Z-server to establish the rules for the “Z-Association” between the two systems.
* Z-server translates the “Z-speak” into a search request for the Target library’s database and receives a response about numbers of matches etc.
* Z-client receives records
* Records are presented to the OPAC interface for the user.
Lynch discusses the history, development, and issues of the protocol.
z39.50 is pre-web.
problems include what to do with unknown attributes (interoperability)
Norbert Lossau, “Search Engine Technology and Digital Libraries: Libraries Need to Discover the Academic Internet”
"If libraries do not want to become marginalized in a key area of their traditional services, they need to acknowledge the challenges that come with the globalisation of scholarly information, the existence and further growth of the academic internet."
libraries will be left behind if they don't get with the program. Need to realize that academic content is not limited to the library portal.
the vision: "...any type and format of academically relevant content"
"The new, academic search index should come with the ease of handling and the robustness and performance of Google-like services but with the relevance and proven ("certified") quality of content as it is traditionally made available through libraries."
Libraries no longer have the monopoly on information, business, commercial, publishers all involved. Need to consider the user.
"Library users have been "empowered" by Google-like search engines to make their own choice about a search tool and to approach the world of information without any training. While librarians are mainly worried about the quality of information resources that are covered by mainstream search indexes, their users love these new tools and they would like to use them for any type of information search."
* what is a "Google-like interface" ?
Making 'invisible' web visible:
"Academic content, as described before, is often part of the invisible web and therefore not accessible to standard web robots per se. Institutions exposing their data to Google have to be aware that this can involve conversion work on the library site and that this conversion is mainly not conversion to a standard format like OAI with DC as supported by libraries."
No comments:
Post a Comment