Duplicate Title Analysis should include match option for Unique OCLC number match method
The Duplicate Title Analysis job and report currently include matching on only one attribute at a time, rather than on all of the attributes that might be covered by a given match rule. For instance, matching on system number provides only matches between 035$a in different records, while the Unique OCLC number match method covers both 035$a and 035$z. As a result the duplicate title analysis report is missing records that would otherwise be found by an import profile or the match method in the network zone.
-
Susan Wynne commented
Thanks for submitting this idea, Ted!
The Duplicate Title Analysis job 035$a parameter also misses OCLC numbers that aren't formatted exactly the same, for example,
(OCoLC)5778810
ocm05778810
(OCoLC)ocm05778810These are the same OCLC control number but would not be caught by Duplicate Title Analysis.
Adding Unique OCLC number match method as an option should catch all of these duplicates.
I recently worked through thousands of duplicates in PASCAL's NZ using the Duplicate Title Analysis and Merge Records & Combine Inventory jobs. Afterwards, I identified several thousand remaining duplicate OCLC number pairs/groups using Analytics. However, I have not yet found a good way to use those results from Analytics with the Merge Records & Combine Inventory job without a lot of manual work to prep the upload file.