Skip to main content
OCLC Support

WorldShare Record Manager release notes, April 26 2025

 

Release Date: April 26, 2025

Introduction

This release of WorldShare Record Manager provides one enhancement in addition to 3 bug fixes. The new feature will help you manage more complex workflows, including:

  • Set holding and export a bibliographic record using TCP/IP in one action
  • Bug fixes
    • Duplicate non-Latin fields after updating a bibliographic record
    • ISBN fields were no longer added to a bibliographic record
    • Unable to update the LHR summary if text contains an ampersand character

The enhancement is the direct result of your feedback.

New features and enhancements

Set holding and export a bibliographic record using TCP/IP in one action

You can set a holding and export a bibliographic record in one action by clicking the "Set holding and export" button. This button had been implemented in an earlier release of Record Manager, but the record was always sent to an export list.
With today's release, a new user preference allows you to select whether you wish to send the record to an export list or TCP/IP.

The new user preference is located under Working with Records / Bibliographic Records and is set to "Export list" by default.

UserPrefExport.png

Changing this user preference to TCP/IP will send the record directly to your local system via TCP/IP when clicking the "Set holding and export button".

 Visit Working with Records for additional information and workflows.

Bug fixes

Duplicate non-Latin fields after updating a bibliographic record

Non-Latin fields are no longer duplicated after updating a bibliographic record or setting or deleting a holding. Previously non-Latin fields were duplicated. 

ISBN fields were no longer added to a bibliographic record

Additional ISBN fields, e.g. a 10-digit ISBN or a 13-digit ISBN, are now again added to a bibliographic record when validating or replacing the record. Previously, these additional 020 fields were no longer added.

Unable to update the LHR summary if text contains an ampersand character

You can now update the LHR summary if the text you're adding contains an ampersand character. Previously, text containing an ampersand resulted in an error message.

Important links

Support website(s)

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