Skip to main content
OCLC Support

WorldShare Circulation release notes, May 2018

Release Date: May 13, 2018


This release of WorldShare Management Services provides several new features in addition to numerous bug fixes. The new features are the direct result of user feedback.

Recommended actions

For this release, we recommend that you review the following checklists and complete the relevant tasks so that you can adjust your policies and workflows and train your staff. These checklists identify updates that we have determined to be significant for most institutions. We encourage you to review all the items in the release notes to determine whether there are other items that might require additional action or follow up by your institution.

Administrative actions


There are no suggested administrative actions related to this release.



View ILL request ID associated with a hold

You can now determine which WorldShare ILL or Tipasa request is associated with a hold created via Circulation Integration. Circulation Integration allows your library to streamline borrowing workflows by automatically creating temporary items and holds for loan requests. To learn more see:

When viewing the patron's Holds tab, click the 'Edit…' link to open the 'Edit Existing Hold Request' dialog box. Holds created via Circulation Integration will display a new field, 'Details,' with the applicable request ID.


Coming Soon: Enhanced integration with Tipasa and ZFL-Server

In summer 2018, WorldShare Circulation will offer an integration with ZFL-Server as well as an enhanced integration for libraries using Tipasa.

To prepare for these upcoming features, a new page has been added to the WMS Circulation section of Service Configuration, ILL Settings.

Please note that ILL Settings will not apply until a future release. It is recommended that you keep the 'Enable' settings on the default value, 'No.'

Bug fixes

Error displays in automatic email receipts

Automatic Checkin Receipt and Automatic Due Date Receipt email notifications no longer display 'field undefined' errors in the Item Barcode and/or OCLC Number fields.

New due date for recalled items not reflected in availability view in WorldCat Discovery or WorldCat Local

Recalled items were displaying with the original due date when viewing the item's availability information in WorldCat Discovery or WorldCat Local. As of this release, availability information for recalled items will reflect the recalled due date.

Title-level hold created when the Location Policy of all items' temporary shelving location(s) cannot fulfill holds

Prior to this release, the system considered the permanent as well as the temporary shelving location of barcoded and unbarcoded items when determining if a title-level hold could be fulfilled according to your library's Location Policies. This allowed some unfulfillable title-level holds to be created. 

After this release, only the temporary shelving location will be considered when a temporary location is specified.

Prompt for override credentials displays but doesn't work when placing out-of-policy holds

When attempting to create or edit a hold that will conflict with library policy, the system would prompt for your institution's override credentials and then fail to accept the username and PIN. Prior to the March 2018 release, the system would only ask that you acknowledge the exception.

As of this release, the system will once again ask for acknowledgment but will not prompt for override credentials when you create an out-of-policy hold.

Bill notices not sent if no minimum amount set in Bill Notification Policy

Prior to this release, bills assessed by policy at check in, checkout, etc. could only generate a bill notice if the associated Bill Notification Policy had a value equal to or greater than zero (0.00) set in the "Send after x worth of bills are accrued" field.

After this release, bill notices will also be generated if no minimum is set. The minimum will be interpreted as 0.00, and bill notices will be generated at check in, etc., for bills of any value.

Last Modified Date not updating for Notification Policies 

Prior to this release, the Last Modified date and time displayed in Service Configuration did not always update after a Notification Policy was saved. This issue has been resolved for all future updates.

Known issues

No new issues were introduced in this release.

Post release sessions

No post release session is scheduled at this time.

Support website(s)

Support information for this product and related products can be found at:

Next release

To be determined.