Interoperability

Worldcat Local interoperability-related FAQs

Jump to:
Interoperability: ILS | Interoperability: Authentication | Interoperability: OpenURL resolver/content management

ILS

• How does WorldCat Local work with a library's ILS?
  

  WorldCat Local integrates a locally configured version of WorldCat.org with the ILS and delivery services already in place at your library.

  WorldCat Local supports a number of activities for authenticated users.

  WITH THESE TYPES OF ITEMS	USERS CAN PERFORM THESE ACTIONS	ON THESE SYSTEMS
  Returnable items including but not limited to books, CDs and DVDs	Place a hold	Innovative: Millennium, INNOPAC ExLibris: Aleph, Voyager SirsiDynix: Horizon, Symphony, Unicorn
  	Request a selected item	WorldCat Resource Sharing™ OCLC ILLiad™ Innovative: INN-Reach OCLC VDX®* Voyager Universal Borrowing (shared catalog)
  Nonreturnable items, such as articles	Link to full text from FirstSearch or Electronic Collections Online™ Link to article full text through a library's OpenURL resolver via the OpenURL Resolver Gateway	N/A

  * Compatibility with this system is currently under development.

• With which ILSs does WorldCat Local work?
  

  OCLC has completed integration of WorldCat Local with several integrated library systems, and is in the final stages of development with other systems. WorldCat Local is currently active at libraries with the following systems:

  Innovative Interfaces: Millennium, INNOPAC, INN-Reach

  SirsiDynix: Horizon, Symphony, Unicorn

  ExLibris: Voyager, Aleph

  Expanded access to other ILSs will be added in phases, including an API and NCIP for library staff to create their own interoperability features later in 2009.

  Examples of WorldCat Local sites:

  • University of Washington
    (Innovative Interfaces INN-Reach)
  • Lincoln Trail Libraries System
    (SirsiDynix Horizon)
  • The Ohio State University Libraries
    (Innovative Interfaces INN-Reach)
  • University of California Santa Barbara
    (ExLibris Aleph)
  • University of California San Francisco
    (Innovative Interfaces Millennium)
  • University of California Los Angeles
    (ExLibris Voyager)
  • Zion-Benton Public Library
    (Horizon Unicorn)
  • Northeastern Illinois University
    (ExLibris Voyager)
  • Indiana University
    (Sirsi Symphony)
• How does OCLC support a library that migrates from one automation system to another?
  
  Libraries are required to give OCLC 90 days notice prior to migrating to a new system. OCLC will then work with library staff to transition their use of WorldCat Local to their new service. When a library adopts a new local system for which WorldCat Local has not been configured, OCLC will make reasonable efforts to develop interoperability with the system.

Authentication

• Will WorldCat Local use our library's authentication system for online services such as NetLibrary® or FirstSearch, or full text from non-OCLC electronic resources?
  
  Yes, WorldCat Local will include a link to your current authentication system for access to licensed content.
• At what point does WorldCat Local integrate user authorization?
  
  An authentication log-on will display to users at times when they need to complete authentication in order to take an action such as initiating an interlibrary loan request or linking to licensed online content. In addition, a link to user accounts can be configured to display within the interface for users who wish to log on at any time.
• Our users already create accounts in our ILS. Will they now have to create another or can we tie in to the user account?
  
  Users will need to create a WorldCat account in order to take advantage of features such as building lists or contributing content. The minimum requirements for a WorldCat account are name, password and e-mail address. This is a separate account and accesses different information than a user's ILS account.

OpenURL resolver/content management

• How will WorldCat Local work with our OpenURL resolver?
  

  OCLC staff work with you to establish links from WorldCat records to your resolver. If you have already set up the OpenURL resolver link in FirstSearch, you will find the process for establishing this link is similar. WorldCat Local links users to your OpenURL resolver at appropriate times within the search process.

  The WorldCat Local service does not access information in your resolver and deliver it through the WorldCat Local interface; rather, it links users to your resolvers.

  NOTE: It is essential for your library to add holdings information for its serials titles to WorldCat in order for WorldCat Local to appropriately display a link to your OpenURL resolver. You may wish to use the eSerials HoldingsTM service to streamline the work needed to add serials ownership information to WorldCat.

• How does WorldCat Local work with an A to Z list?
  
  OCLC can configure a link to your library's A to Z list during implementation, but we do not recommend it. Usability testing with WorldCat Local has shown that linking to your OpenURL resolver will provide a superior user experience.
• Can WorldCat Local be configured to work with repository systems in addition to CONTENTdm®, such as a Fedora repository?
  

  OCLC can harvest records from OAI repositories, crosswalk them to MARC format and load them directly into WorldCat where they become part of a user's search and discovery experience. This is how OCLC handles CONTENTdm and other digital collections.

  For collections that are not OAI-harvestable, in July 2009, OCLC will offer metasearch functionality that will allow WorldCat Local libraries to set up connectors to additional collections.

• WorldCat Local
• At a glance
• Overview
• Interface features
• WorldCat Local "quick start"
• Promote WorldCat Local in your library
• Success stories
• Ordering
• Support, training and documentation