Improve Hold Duplicate Detection
Hold duplicate detection has a flaw that allows duplicate hold requests to be placed on the same titles. The detection seems to apply on title and author information stored with the hold request (apparently on the SysHoldRequestSearchTerms table), which stores point-in-time title/author details that may change if the bib record is overlayed or edited.
This idea is for improving the duplicate detection to fix this gap, but also any similar gaps I may be missing where title-related data is stored separately when the hold is created, and referenced by the dupe detection (I'm not seeing separate tables storing elements like format or pub year, but in case there may be a similar dynamic with any other criteria that can fall out of date).
Jason Tenter
shared this idea
-
Wes Osborn
commented
This is a correct assumption, here is what we were told in 2015 (at that time we put in an enhancement to ask it to use the bib id # instead or the UPC):
Format
LCCN
Author
Title
Volume
Issue
Publication Year
ISBN (the system matches on the 1st ISBN in each record)In order for a request to be considered a duplicate, each of the above fields must match in both request workforms. For example, if the format listed in request A is DVD, the format in request B must also be DVD. Similarly, depending on how complete the record being used to create the request is, certain fields in the request workform may be blank. If this is the case, that field must be blank/null in both requests in order for it to qualify as a duplicate.
It is possible that two records with different, but similar, titles could be considered duplicates. An example of this would be if you had two DVD’s both released in 2014 and one was titled Le Chef, while the other was titled Chef. Should a patron place a request for these two titles, they would visibly match on the publication year and format. However, because the stored procedure used to check for duplicate requests checks both the Browse Title and the Sort Title of a record, it will also find a match there. While the Browse Title for these would not be a match (LE CHEF and CHEF), because the Sort Title drops the initial article of ‘Le’, requests for these two titles would be determined to be duplicates.