WorldShare Acquisitions release notes, July 2025
Release Date: July 10, 2025
Introduction
This release of WorldShare Acquisitions provides two new features and enhancements in addition to numerous bug fixes. These features will help you manage more complex workflows, including:
- Enhanced ebook matching with vendor platform codes for more accurate acquisitions processing
- Reset or update receiving settings capabilities for improved serial management
Many of these enhancements are the direct result of your 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 as significant for most institutions. We encourage you to review all of the items in the release notes to determine whether there are other items that might require additional action or follow up by your institution.
Follow-up actions
In an effort to keep your staff informed of new features and changes, you may also want to consider these items.
| Action |
|---|
|
New features and enhancements
Enhanced Ebook Matching with Vendor Platform Codes
What's changed
Previously, you couldn't automatically match vendor ebook records to specific Knowledge Base collections when only platform codes were provided in the MARC file, requiring manual intervention, settling for the WorldCat record instead of the KB ebook record. Now, you can seamlessly link imported ebook records directly to the appropriate KB collections using vendor platform codes, ensuring more accurate acquisitions processing and better collection management.
New field support
- The system now recognizes vendor ebook codes provided in MARC field 981$p
- When KB Collection Identifier (981$a) and KB Title Identifier(981$b) are not provided, the system will attempt to match records using the vendor platform code
- Platform code matching uses a "starts with" search to accommodate license codes that may be appended to the base ebook code
Enhanced matching logic
The system now follows this prioritized matching sequence:
- Direct KB Matching: If 981$p and 981$a and 981$b are provided, then subfields $a and $b take precedence (981$p is ignored)
- Platform Code Matching: If only 981$p is provided, the system matches the vendor ebook code to the appropriate KB collection and searches for exact ISBN matches within that collection
- Fallback to WorldCat: If KB matching fails, the system defaults to WorldCat matching
Improved logging and notifications
- Successful KB Matches: Clear confirmation when records are successfully linked to KB collections
- Failed Matches: Detailed explanations when KB matching fails, including specific reasons
- Dual Logging: When KB matching fails but WorldCat matching succeeds, both attempts are logged
- Email Notifications: Warning messages are included in email notifications for failed matches
Getting started
To use this feature, ensure your vendors are set up with Ebook Mapping Codes and that their MARC files include the 981$p field with appropriate platform codes. Contact OCLC Support if you need assistance configuring vendor mappings.
- (Optional) Link vendors if your vendor is not the primary vendor or one of the alternate vendors:
- In WorldShare Acquisitions, go to Settings > Administration and expand the Ebook Vendor Mapping accordion.
- Click View/Edit in the Actions column for a vendor you want to view or link a local vendor to.
- In the My Linked Vendor(s) accordion, click Add.
- In the pop-up that displays, enter the vendor to link in the dropdown.
- Select the vendor, click Add.
- (Optional) You can also review the vendor codes for your vendor are accurate, in this same accordion. (Note: A bug was discovered just before the release that only the first 20 codes are displayed in the user interface. More may be present in the system and will be used for matching, however.)
- Search for a vendor, and click on the vendor name.
- Expand the Partner Exchange Services accordion.
- Click the Upload File button.
- Click Choose file, find the file on the local computer, and click Open.
- Click Upload.
- The order is created with matching KB ebook.
Visit Administer your institution configuration for WorldShare Acquisitions for additional information and workflows.
Reset or Update Receiving Settings
What's changed
Previously, you couldn't edit the receiving history of serial issues once they were configured, making it difficult to adjust expected copy counts or modify issue ranges when subscription patterns changed. Now with the Reset Receiving Settings feature, you can easily edit an issue’s receiving history by adjusting the number of expected copies associated with specific ranges, giving you more control over your serial management.
Key capabilities
- Modify receiving history for existing serial issues
- Adjust expected copy counts for specific issue ranges
- Add or remove issue range configurations
- Maintain accurate records when receiving patterns change
How to use Reset Receiving Settings
- Search for title in Discover Items and select the desired title.
- Click Issues in the upper right-hand corner to access serials management.

- Click Edit receiving settings.
- Review current receiving history.
- You will see the existing receiving history in a table format

- The table displays issue ranges, expected copies, and current actions
- You will see the existing receiving history in a table format
- Edit or add rows.
- Click the ellipses (...) in the Actions column to edit or delete an existing row

- You can also add a new row above or below any currently selected row
- Use the Actions dropdown to modify settings for specific issue ranges
- Click the ellipses (...) in the Actions column to edit or delete an existing row
- Make your changes.
- Adjust the number of expected copies for any issue range
- Add new issue ranges as needed
- Remove outdated or incorrect receiving configurations
- Save your changes.
- Click Save to apply your modifications to the receiving history
Important considerations
- If you remove receiving settings for issues that currently display in the receiving table, those issues will still appear in the table, but the expected copies received will become zero
- Example: If you previously received two copies of an issue and then deleted the receiving configuration, the table for that issue will read "2 of 0 for Copies Received"
- Issue overlap is not allowed when adjusting the receiving history - error icons will display if overlap or duplicate issues are detected

- The system automatically sorts rows from newest to oldest
Visit Edit receiving settings for additional information and workflows.
Bug fixes
Custom field options can be created without translated field names
Users can now seamlessly add options to custom fields without encountering server errors. Previously, attempting to add options when translated field names were not added would result in a server communication error, disrupting the process of customizing options. This fix ensures that all custom field options are added correctly, enhancing the flexibility and usability of the Acquisitions module.
Encumbrance is accurate for high-priced order items after unpay of invoice
Users can now unpay invoices for high-priced items that are split among multiple funds and be confident that the encumbrance will be accurate. Previously, when unpaying invoices for high-priced order items with multiple funds split by amount, the encumbrance would be recalculated by a few cents to be a different amount than what was originally entered by the library. Now, even high-priced items should be re-encumbered with the correct amount if the invoice is unpaid. As part of this bug fix, we also now support additional decimal points when splitting items by percentage. These will not show by default, but you can now enter up to 9 decimal places when splitting the cost of an order item by percentage.
Resolved intermittent errors in serials management receiving
The process for receiving serial issues has been stabilized to prevent intermittent errors. Previously, users experienced errors when attempting to receive serial issues, which occurred frequently enough to disrupt serials management workflows. With this fix, the receiving function is now reliable, allowing libraries to manage serials efficiently without unexpected interruptions. Additionally, the system now handles API exceptions more gracefully, ensuring a smoother user experience.
Known Issues
Only first 20 codes are displaying for ebook vendor platform codes
Only the first 20 platform codes are displaying for each vendor in the Ebook Mapping accordion under Administration> Settings. However, more may be present and will be used by the system.
Important links
Support website(s)
Support information for this product and related products can be found at:
