Searching: OCLC Number in Z39.50 with junk characters (2.5.2)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Wishlist
|
Unassigned |
Bug Description
At some point in its history, OCLC began to include alphabetic prefixes to its OCLC Control Number. There was also a point at which they pre-padded zeroes in front of the number. This, of course, creates keyword searching problems. Recently I have even run across OCLC numbers that include a backslash at the end of the number! In a previous ILS there was a parameter that allowed for these unwanted characters and zeroes to be eliminated on import. In another previous ILS the prefixes and zeroes were somehow ignored when searching for the OCLC number.
OCLC number searches in Evergreen require all characters to match exactly. This causes a problem when doing a Z39.50 Import search. Typing in just the OCLC number (TCN) retrieves the correct record from OCLC, but does not retrieve the record from the Local Catalog. Typing in the OCLC number with the prefix retrieves the record from the Local Catalog but not from OCLC. Not good. It also causes a problem for anyone trying to do an OCLC number search since they would have to guess at whether the number includes a prefix.
Evergreen needs the capability to conduct a keyword search for only the OCLC number, while ignoring the junk prefixes, zeroes and slashes, or provide a way to strip the nonessential characters when the bib records import.
tags: | added: search wishlist |
Changed in evergreen: | |
importance: | Undecided → Wishlist |
tags: |
added: z3950 removed: wishlist |
The regular catalogue search includes the identifier|oclcnum: search filter that searches the 035 field for values matching (OCoLC)#########, e.g. https:/ /laurentian. concat. ca/eg/opac/ results? query=identifie r|oclcnum%3A61162064