Releases: openlibraryenvironment/dcb-service
Releases · openlibraryenvironment/dcb-service
v8.61.0
v8.60.0
Changes in this release
Features
- Increase page size and don't issue count query.
- Better defaults for threading
- Exclude items from same library as patron when the pickup library is different.
Fixes
- Make the 'out of sequence' value consider all valid workflows DCB-2085
- Fix resolution selecting an item at the patron's library with holds over an available item with 0 holds DCB-2106
- Fixes for native build
General
- Support updating more library attributes.
- Remove log warnings for missing secret / principal labels.
- Use the bounded elastic pools for threading.
v8.59.0
Changes in this release
The following changes were included in this release of DCB Service.
Features
- Prevention of renewals on items with holds DCB-1533
- For FOLIO systems, this requires Sunflower CSP3+ , it will fail safely if the endpoint is not available.
- Disallow unsupported workflow, only different pickup library DCB-2091
- Include patron names when creating Sierra virtual patrons DCB-2057
- Include patron names when creating Polaris virtual patrons DCB-2058
- Include patron names when creating Alma virtual patrons DCB-2059
Fixes
- Correctly determine FOLIO hold counts DCB-1533
- Fix handling of Polaris hold counts, disallowing cancelled holds and ensuring only item level holds are processed DCB-2093
Clustering
(Note this does not apply to systems without the improved clustering enabled)
- Addition of the clustering process audit
- Fixes for housekeeping job.
v8.58.2
v8.58.1
Changes in this release
The following changes were included in this release of DCB Service.
Fixes
- Make sure we provide the local names when constructing a FOLIO PUA transaction DCB-2043
- Improve handling when we don't find a Polaris hold for deletion DCB-2075
- Prevent double increment of availability date DCB-2075
General
- Add REQUEST_PLACED_AT_PICKUP_AGENCY as eligible cleanup status DCB-2068
v8.58.0
Changes in this release
The following changes were included in this release of DCB Service.
Features
- Added indexes to bib_record to improve performance.
Fixes
- The grace period for the availability count is now nullable, as the existing values will be null.
- The query time for cluster housekeeping has been improved.
- Fixed an issue where the ruleset was not unwrapping the JSON scalars - this was affecting the feature described in DCB-1701
- We now de-prioritise overdue CHECKED_OUT items when selecting an item for a request, so they can never be chosen over an AVAILABLE item DCB-2075
- This has been accomplished by a change in how we calculate the "availability date' for checked out items. Previously it was equal to the due date, which meant overdue items were seen as the "earliest available". Now all CHECKED_OUT items are assumed to have an availability date of at least the current date, plus the default loan period (28 days) multiplied by the hold count +1.
- This ensures that CHECKED_OUT items will still be selected if SELECT_UNAVAILABLE_ITEMS is turned on and there are no AVAILABLE items.
- Fixed an issue where we were using the wrong value when trying to delete a supplier hold during cleanup. This issue primarily affected Polaris systems and could lead to DCB-placed holds not being removed on finalisation DCB-2068.
- Improved the handling and auditing of Polaris hold deletion DCB-2068.
- In the 'fallback' scenario where we fail to initially delete a hold, DCB will attempt to cancel the hold and then retry deletion. This should address the scenario where Polaris holds can't be initially deleted because they're not in a status eligible for deletion. It should also improve visibility of the cleanup process.
v8.57.0
Changes in this release
The following changes were included in this release of DCB Service.
Features
- Live availability improvements. Fixes DCB-2019 among others.
- This changes existing behaviour. In scenarios where we would have returned UNKNOWN, we will now return the last known value with a timestamp
statusCorrectAsOf. Discovery systems integrating with dcb-service should be aware of this and we recommend exposing it to the user, so that they know when the status was fetched. - The UNKNOWN status was originally introduced as some libraries will never return information within the 7 second limit defined at the start of the project. With it gone, some titles will now appear to be available in live availability that weren't before. For requests on titles where we do not get a response during resolution (30 seconds max), the request will still fail.
- This means no requests will be placed on items without us knowing their status: it also means that if a library is not providing up-to-date data, an item will now appear as its last status (so it may appear requestable). But resolution will prevent the user from actually placing a request on an item we can't get a status for.
- This changes existing behaviour. In scenarios where we would have returned UNKNOWN, we will now return the last known value with a timestamp
- The availability check job now has a longer default grace period for items and after 3 errors will flag that a retry is needed in 7 days (if unmapped) and 30 days (if mapped).
- Accept any FOLIO transaction status - this is preparatory work for a fix for DCB-2009 in mod-dcb.
Fixes
- Fix Polaris cleanup behaviour DCB-2076. This handles the standard scenario where Polaris virtual items could not be deleted because of the virtual hold placed upon them. It does so by either deleting the hold or cancelling it, and then deleting the virtual item afterwards.
- Handle more complicated Polaris cleanup scenarios DCB-2076. This handles the more complicated situations that can occur when we try and delete a Polaris item.
- See the Polaris docs for more info: scenarios covered by this include blocked items, delayed responses from Polaris, and improved handling of Polaris responses that verifies that the item ID exists in the "deletedItems" response.
- Do not select unavailable manually selected item DCB-2082
- Use reactive delay instead of sleep to address Polaris issues.
- Use Polaris location to policy mapping when present.
v8.56.0
Changes in this release
The following changes were included in this release of DCB Service.
Features
- Include patron names when creating virtual patrons in FOLIO DCB-2043.
- If the VIRTUAL_PATRON_NAMES_VISIBLE functional setting is enabled, then DCB will supply the "real" patron names to mod-dcb, which creates a virtual patron for us.
- When enabled, this replaces the previous behaviour, where all virtual patrons were named "DcbSystem". When not enabled, the previous behaviour remains in effect.
- Suppression: use up to date suppression rules DCB-1701
- Add controller for source records.
- Add date_updated index on source_record with secondary on source_id.
Fixes
- Clustering: always flag null titles as similar, even when both are null.
- Provide hold counts for Alma items DCB-2046
General
- Added script for duplicate barcode detected DCB-2076
- Improved the range of errors captured by error overview SQL.
v8.55.0
Changes in this release
The following changes were included in this release of DCB Service.
Fixes
- DCB will now update the expiry date of Polaris virtual patrons if they are within 30 days of expiry: this has been increased from 7. The expiry date will now also be extended by 120 days, up from 90: DCB-2069
- Fixed a situation where DCB requests where Alma is the supplier were failing because DCB was using an incorrect library code: DCB-2074
v8.54.0
Changes in this release
The following changes were included in this release of DCB Service.
Fixes
- DCB now detects and updates expired / about to expire Polaris virtual patrons if one is being used in a request DCB-2059. This fixes an issue whereby Polaris virtual patrons would expire and become blocked but still be used by DCB, causing requests to fail on checkout.
- Provide the active workflow for Alma requests - Alma requests were failing because no active workflow was being provided DCB-2065
Improvements
- Added endpoint for explaining a cluster record's match points.
- Range filtering improvements.