Passa al contenuto principale
Supporto OCLC

WorldShare Record Manager release notes, December 15 2025

  1. Ultimo aggiornamento
  2. Salva come PDF

 

Release Date: December 15 2025

Introduction

This release of  WorldShare Record Manager provides one change in functionality in addition to 5 bug fixes, including:

  • New option to delete customized scripts and script packages 
  • Bug fixes
    • Chronology does not print on labels if enumeration is missing  
    • Cutter part of a call number is incorrectly split up on labels 
    • Labels are not sorted in the order that barcodes were added to the label print list 
    • Incorrect volumes were displayed in a label print list
    • When validating a record with a newly added 010 field the leading spaces were no longer automatically added

The enhancement is the direct result of your feedback.

Recommended actions

For this release, we recommend that you review the new "Delete" feature for customized scripts and script packages, as this is a change of the previous behaviour, where you were able to archive but not delete these. 

New features and enhancements

New option to delete customized scripts and script packages

Delete customized scripts 

When viewing the list of customized scripts, the option "View Archived Scripts" is no longer available.

CustomizedScriptList.png

 

It has been replaced by a new option, "Delete" that displays when you view an existing customized script. Instead of archiving scripts that are no longer needed, you can now delete them. 

DeleteCustomizedScript.png

If you want to create a new customized script that is similar to one that you no longer need, you have the option to "Clone" it and save it under a new name. 

After clicking the "Delete" button, you will see a dialog asking you if you really want to delete that script. You can delete the script by clicking on "Delete" or clicking "Cancel" to close the dialog. 

DeleteCustomizedScriptWarning.png

If the customized script that you want to delete is used in one of the script packages, you will not be able to delete it. An error message tells you that the customized script is used in x script packages and will also list the name of the first script package. 

Remove the customized script from the script package(s) that it is used in first, if you really want to delete it. 

CustomizedScriptUnableToDelete.png

 

Delete script packages 

When viewing the list of script packages, the option "View Archived Script Packages" is no longer available.

ScriptPackagesList.png

It has been replaced by a new option, "Delete" that displays when you view an existing script package. Instead of archiving script packages that are no longer needed, you can now delete them. 

ScriptPackageView.png

If you want to create a new script package that is similar to one that you no longer need, you have the option to "Clone" it and save it under a new name. 

After clicking the "Delete" button, you will see a dialog asking you if you really want to delete that script package. You can delete the script package by clicking on "Delete" or clicking "Cancel" to close the dialog. 

Bug fixes

Chronology does not print on labels if enumeration is missing 

Chronology information will now print correctly on your labels if the record does not have enumeration. Previously, the chronology would not have been printed on the labels. 

Cutter part of a call number is incorrectly split up on labels

The Cutter part of a call number will now display correctly on labels. Previously, the content of the 852 $i subfield was split up with an extra line break. 

Labels are not sorted in the order that barcodes were added to the label print list

The order in which labels display on a label print list does now match the order in which the corresponding barcodes were added to the label print list. Previously, the order of the labels was sometimes different from the input order. 

Incorrect volumes were displayed in a label print list 

Volume information that was selected from the enumeration/chronology dropdown in a label print list will now be reflected correctly in the label layout. Previously, there was an inconsistency in how labels were displayed in the label records list and the label layout. 

When validating a record with a newly added 010 field, the leading spaces were no longer automatically added

You can now add a 010 (containing the LCCN) to a bibliographic record, and leading spaces will automatically be added. Previously missing leading spaces led to a validation error for that record. 

Important links

Support website(s)

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