I-Share

Local Catalog Maintenance

Bibliographic Records: Fixed Fields: Publication Status

NOTES: For all queries in this series, there is a macro on the Shared Macro page called Changebib_008pubstatus.mex that can take the results of the query as an input file and edit the fixed field Publication status code to a new user-defined value, as specified within the macro.

Local Catalog Maintenance

Bibliographic Records: Fixed Fields: Government Publication Codes

ICAT Statement on State University Press Publications and Maintenance Projects

According to instructions under the 008/28 in the MARC 21 Format for Bibliographic Data, “items published by university presses are considered government publications if the presses are created or controlled by a government (e.g., state university presses in the United States).” For more information.

Correcting “the 653 problem” how to search for it, recognize it from a printout, and correct it

NOTE:  This does not apply to institutions that migrated to I-Share Voyager in 2003 or after.  This also does not apply to those I-Share Voyager libraries that did not use the bibliographic master records converted from DRA (e.g. UIC, SIUM, IIT).  However, any I-Share Voyager library that copies records from the I-Share Universal Catalog may have inadvertently copied records containing these 653 fields into their catalog.

Sample ABBA Table for New I-Share Participant Libraries

One of the most confusing yet also most important parts of the migration to Voyager is creating the “Location Load Mapping Table” (i.e., the ABBA table).

To assist the new I-Share libraries with this task, the CARLI Office thought it might be helpful to see an example ABBA table that was used in a previous conversion to Voyager.

How to Share a Query

Sharing SQL queries is another example of resource sharing within our consortium that can only be successful if queries are contributed to as well as used from this page. If you have written an SQL query for Access that you would like to share, please with the following information:

Estimated Run Times for Shared SQL Queries

It is difficult, but not impossible, to estimate how long an MS Access query will run. The timing is affected by the size of your Voyager database and the speed of your workstation. The capacity of your network connection is also an important factor, and this may vary depending on how busy your campus connection is at any particular time.

Historical Browse Statistics in I-Share

The Voyager system keeps a count of browses. It counts a browse when an item that is not charged out is discharged. If your library routinely discharges items found off the shelf, the browse counts give you an indication of the in-house use of your materials. This is especially valuable for non-circulating collections such as periodicals. 

How to Use Shared Queries

You can also watch the CARLI Introduction to Voyager Access Reporting training video series. It covers using the shared SQL.

Reports with Call Number Ranges: How to Request Them and How to Write Them

Introduction

Library staff often need reports based on call number ranges. Typically, these involve counts of items, titles, or circulation activity. The Voyager system makes the call number available in several formats, and you need to think about which one best meets your needs. You may also need to prepare a set of call number ranges. Once you’ve accomplished these two things, writing the report is pretty straightforward, but you can always ask CARLI staff to write it for you by filing a work request.

Copying Queries from One .mdb File to Another

Queries can be “copied” from one .mdb file to another. This can be useful for migrating queries that you’ve written or customized to the new CARLI_reports_2009.mdb file so that you can take advantage of the new features available in the updated file.

In Microsoft Access 2003:

Getting Started with Voyager Access Reports in the I-Share Environment

Information to help you get started and understand using Voyager Access Reports in the unique I-Share Environment. (revised 8/24/2016)

Voyager Acquisitions & Serials FAQ

The following are questions that have been raised at training sessions, at forums, or that have been submitted to the CARLI staff. If you have questions that you would like to see addressed on this FAQ please send an email to

They are loosely arranged into the following topical areas:

expand / collapse all

Secure Text doc

This is test for the secure area

Using Voyager Circjob 40 to Clear Fines of $4.99 or Less

On April 1, 2010, CARLI started running circjob 40 in all I-Share library databases to clear out UB fines of $4.99 or less per item. The circjob will run on the first day of the month, with a report available in your library’s ftp directory the day after. The report filename = 499_fines_xxx_yyyymm.txt [where xxx is your library’s 3-letter code].

The first run of the circjob will clean up many of the accumulated patron fines. The subsequent runs each month thereafter will result in much smaller reports.

Dead Requests Report

Requests and Promotes that could not be filled by an I-Share library

Description of the Request Promotion Process:

When a patron places a request for an item through the OPAC, a call slip or UB request is sent to a library to fill the request. Ideally, the library is able to fill the request.

When the library does not fill the request, one of two things can happen:

Circulation System Adminisration: How Circulation Administration Values are Used During a Checkout

  1. Circulation person logs in at a circulation terminal.
    1. Sysadmin looks up the userid.
    2. Sysadmin links to the circulation profile for that person.
    3. Sysadmin determines the circulation happening locations in the security profile.
    4. If more than one happening location exists in the security profile, a selection screen appears in the circulation module.
    5. Once one happening location is chosen, the circulation module is opened.

Call Slip Item Required: Preventing Requests for Titles that Have No Items Attached

Background

The  Call Slip Item Required setting in the OPAC Configuration-Miscellaneous screen in Voyager System Administration can be used to control the specificity of requesting in the OPAC. This option is intended to allow a library to determine whether call slip requests may or may not be placed on records that do not have items attached.

Recommended Notice Text

The UB policy standardization of August 2010 includes the recommendation that libraries send Courtesy Notices via email. Occasionally, an email can’t be sent and a print notice will be produced.

The Resource Sharing Team has suggested some text that libraries may want to use for their email and print courtesy notices.
The recommended text is brief and applicable to all I-Share libraries:

Return the item(s) or renew online.

Pages