ORCA

Catalog and Circulation

 

 

Catalog Design ---- Cascade wind down --- Orca catalog launch --- Record loading, circulation, ongoing transactions

 

Catalog merger and loading updates

News release

Timeline

Write to ORCA staff team

Merger

Overview: outline of tasks

ORCA staff team

Cat and Circ

Outline - list of tasks

Catalog Design Task Force

Background

Orbis

Orbis catalog

WSCLP Washington State Cooperative Library Project

WSCLP Cascade catalog

 

The Orbis and Cascade databases will be merged in the summer of 2003.  During the spring, enhancements will be added to the Orbis catalog to build the framework for the Orca catalog, reflecting the best of the Cascade and Orbis catalogs.  Orca will be launched in mid-June, and the Orbis catalog interface will be retired.  Cascade will be shut down in mid-June.  Records from former Cascade libraries will begin loading into Orca by late June. Requesting for Cascade library patrons will be available as soon as their records are being added to the catalog. Orca circulation for Orbis libraries will continue uninterrupted.

Orbis catalog enhancement and building the Orca framework

The best of Cascade and Orbis features will come together in the Orca catalog, including Advanced Searching and Scoping – capabilities not available to Orbis when it was first established in 1994 and subsequently implemented for Cascade.  Considering current and potential use of the new catalog, the staff team will forward recommendations and comments to Council on several catalog and circulation topics: Journal Scoping, Journal Title Index, MESH index, Institution Priority for record loading, Fines for overdue materials, and Visiting Patron.  During the spring and summer, III will install new features on Orbis and do some re-mapping and re-indexing.  Additional work may be necessary later in the summer and fall as more INN-Reach software enhancements are completed.

Orca catalog design

A Catalog Design Task Force will advise Council on aesthetic and functional topics for implementing the new catalog:  Design of the web catalog (colors, buttons, information (Help) pages and search help screens), and setup for the Advanced Keyword index.

Cascade “wind down”

The Cascade catalog will be closed to circ transactions and any updating starting in mid-June.  Cascade libraries will have already begun clearing out old or problem transactions, and will clear out the remainder during a period of “down time.”  During this time, Cascade patrons will be unable to request materials through an INN-Reach system.

Orca catalog launched

The Orca web catalog interface will replace the Orbis interface.  The Orbis and Cascade catalogs will be officially retired.  Patrons trying to access Cascade or Orbis will be automatically referred to Orca.

Record loading, circulation, and ongoing transactions

Records from former Cascade sites will be loaded into the Orca database.  Data from all Cascade local systems will be loading simultaneously, over multiple links.  When a matching record is identified, Cascade institution holdings will be attached.  When appropriate, new records will be created, or Cascade records will overlay older records based on the Encoding level and Institution priority codes.

Circulation.  Patrons from Orbis sites will be able to use Orca as soon as the interface is available.  Patrons from Cascade sites will be able to use Orca as soon as records from their library catalog begin loading.  In other words, Orbis patrons will see very little interruption in service, but automated requesting will be unavailable to Cascade patrons for a short period in the latter part of June.

Impact of loading during the summer months -- Ongoing transaction and projects.  Loading all 6.7 million records from former Cascade sites will take all summer even with low use load.  Completion of the Orca catalog by fall term is the top priority for summer.  As announced earlier, a moratorium on other projects effecting load is in effect to ensure on-time completion.  We will provide additional information later this spring to establish project file sizes that III indicates may be processed without interfering with the system load, and any opportunities for scheduling larger projects so that they may move ahead during this period.

 

Back to ORCA main page

 

 

Last updated: January 15, 2003