Release Date: June 29, 2023
This release of WorldShare Acquisitions providestwo new features and one new bug fix. This feature will help you manage more complex workflows, including:
Many of these enhancements are the direct result of your feedback.
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.
These items require immediate action or decisions.
Action |
---|
None at this time. |
In an effort to keep your staff informed of new features and changes, you may also want to consider these items.
Action |
---|
Notify staff that order items and purchase requests may have a new branch and shelving location by default, based on the material type. (See below for details.) |
The system now more effectively sets the default branch and shelving location of order items and purchase requests based on material type. This saves the library time and effort of changing the branch and shelving location in certain instances. Previously, the default branch and shelving location of eBooks were set using the branch selected as the default when logging in. However, now the default branch and shelving location of eBooks will be set to Unspecified.
There are many ways that a new purchase request or order item can be created. Each of these carries a different default branch and shelving location. These defaults are described below:
Purchase request or order item? | How item was created? | Processing Type = E-Product | Created using Order Item Template? | Created using Purchase Request? | Default Branch | Default Shelving Location |
---|---|---|---|---|---|---|
Purchase Request | Platform | Yes or No | N/A | N/A | Unspecified | Unspecified |
Purchase Request | User Interface | Nee | N/A | N/A | Branch selected when logging in | First shelving location for selected branch |
Purchase Request | User Interface | Ja | N/A | N/A | Unspecified | Unspecified |
Order Item | Platform | Yes or No | N/A | N/A | Unspecified | Unspecified |
Order Item | User Interface | Nee | Nee | Nee | Branch selected when logging in | First shelving location for selected branch |
Order Item | User Interface | Nee | Ja | Nee | Branch in order item template | Shelving location in order item template |
Order Item | User Interface | Nee | Nee | Ja | Branch from purchase request | Shelving location from purchase request |
Order Item | User Interface | Ja | Nee | Nee | Unspecified | Unspecified |
Order Item | Import (MARC data) | Nee | N/A | N/A | Branch selected when logging in | First shelving location for selected branch |
Order Item | Import (MARC data) | Ja | N/A | N/A | Unspecified | Unspecified |
You can now keep your HTTP notification settings between monthly refreshes in the sandbox environment. This saves you time and effort re-entering these settings each month. Previously, this data was cleared during the monthly data refresh of the sandbox environment, but now, this data persists. This allows you to keep special test data concerning HTTP notification settings in the sandbox indefinitely, preventing you from having to re-enter each month.
There is no longer a warning message provided in the MARC data import e-mail notification (for invoice and order data) when an 001 is provided in the MARC record. Previously, a strange warning message displayed for these items with an 001 value, even though there were often no problems with the import. This warning message no longer displays.
Support information for this product and related products can be found at: