This white paper introduces evaluation concepts and describes outcome-based evaluation. The Institute for Museum and Library Services (IMLS) logic model is described in the context of developing a program evaluation plan. Four case studies illustrate how outputs, outcomes and indicators can be used to produce programs results.
This presentation discusses using Z39.50. The topics include framing the "finding it all" question, a resource discovery service project, and update on Z39.50 profiles, and the next generation of Z39.50.
This document discusses decomposing MARC 21 records for analysis. To prepare the test dataset of the 1% sample of MARC 21 records from the WorldCat database for use in the Z39.50 Interoperability Testbed, the authors need to be able to efficiently analyze the records to determine relevant records to be returned for a set of test searches. The first step in that analysis is to determine the occurrence of test search terms in specific records. This document describes the general approach for this analysis and identifies specifications for the analysis.
This study identifies strategies for enhancing access to Illinois libraries' holdings, where the strategies ensure the best stewardship possible for state and federal grant dollars for library automation and resources.
This document is the final report with the summary of the findings, conclusions, and recommendations for consideration by the Telecommunications Infrastructure Fund Board (TIFB) Library Working Group as part of the Needs Assessment Study of Texas Academic, Public and School Libraries. The report is the work of the Needs Assessment Study Team, Texas Center for Digital Knowledge at the University of North Texas. The study was conducted during the period of February through September 15, 2002. Funding for the study was provided by Telecommunications Infrastructure Fund Board
This document describes the procedures that participants in the Z39.50 Interoperability Testbed (Z-Interop Participant) are to use when testing Z39.50 client (Z-client) applications. The testing of a Z-Interop reference implementation Z39.50 server. Specifically, the attribute combination and other query components (e.g., Boolean operators) are reviewed, and a report of the results will be prepared for each Z-Interop participant.
This document provides a status report on the Z39.50 Interoperability Testbed Project (Z-Interop) covering the period of April 1, 2002 through June 30, 2002. The previous status report covered a ten-month period from May 1, 2001 through March 31, 2002. The Principal Investigator (PI) requested a no-cost extension for this project, which the Institute of Museum and Library Services approved. With the letter of approval, IMLS set a revised schedule for project status reports. Beginning July 1, 2002, status reports are due every six months. To respond to the revised schedule of status reports, this document highlights activities and accomplishments to communicate to IMLS progress on this project since the last status report.
This document provides a status report on the Z39.50 Interoperability Testbed Project (Z-Interop) covering the period of May 1, 2000 through March 31, 2002. Due to a family medical emergency, the Principal Investigator was not able to complete the six-month status report that was due December 1, 2001. The Principal Investigator (PI) communicated with the Institute of Museum and Library Services (IMLS) staff about this situation, and had sent via email in November 2001 information about the progress of the project.
This document provides guidelines for indexing MARC 21 records to support a set of searches using Z39.50. The Z39.50 Interoperability Testbed Project (Z-Interop) uses these guidelines to index the 400,000 MARC 21 records that comprise the Z-Interop reference implementation of the Z39.50 server and online catalog.
This document provides an overview and the details of policies and procedures of the Z39.50 Interoperability Testbed Project (referred to as Z-Interop). Specifically, the document lays out the responsibilities and obligations of the Z-Interop testbed and the organizations that participate in interoperability testing. For purposes of this document, Z-Interop staff refers to all members of the Z39.50 Interoperability Testbed Project. Z-Interop participant refers to an individual or organization who tests its Z39.50 client or Z39.50 server through the Z39.50 Interoperability Testbed.
This dialog allows you to filter your current search.
Each of the Months listed note their name and the number of records that will be limited down to if you choose that option.
The list can be sorted by name or the count.