WorldShare Record Manager release notes, April 10 2025
Release Date: April 10, 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:
- Records containing errors that have no significant impact on effective use of the record can now be added and replaced. Correction is optional.
- Bugs:
- Exported 092 field has additional information from 082 field
- Field is now enabled after using "Insert from Cited Record"
- Applying LHR constant data that contains empty subfields
New features and enhancements
Records containing errors that have no significant impact on effective use of the record can now be added and replaced
You can now add or replace bibliographic records containing errors that have no significant impact on the effective use of the record. Correcting them is optional. Previously, some minor validation errors prevented users from adding or replacing a bibliographic record.
For example, leaving the fixed field element Festschrift (008/30) blank is a minor level validation error that required correction, but now is acceptable for adding or replacing a record.
All validation errors can still be viewed by using the "Validate" button under the Record menu.
This applies to the latest version of the Metadata API 2.0 as well. See release notes.
Validate bibliographic records for additional information and workflows.
VisitBug fixes
Exported 092 field has additional information from 082 field
If you export 092 fields, content from 082 $a field is copied to the 092 only if the 092 lacks a non-empty $a. Previously, the exported 092 field had additional information from the 082 field copied upon exporting.
Field is now enabled after using "Insert from Cited Record"
After having used the "Insert from Cited Record" option, the field is now enabled, and further edits can be made. Previously, the field was disabled unless you validated it.
Applying LHR constant data that contains empty subfields now working correctly
Applying LHR constant data that contains empty subfields now works correctly and will no longer result in a system error. Also, empty subfields will not be removed from the Constant Data templates. Previously, applying LHR constant data caused a system error and empty subfields to disappear.
Important links
Support website(s)
Support information for this product and related products can be found at: