You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, VuFind should check for Hathi availability based on current OCLC number (which is an 035 $a field). Sometimes, Hathi uses an outdated or canceled OCLC number for the record on their end. We may have these canceled OCLC numbers in our records as 035 $z fields.
Can we also check the Hathi API for matches based on the 035 $z numbers? This could be done in several ways - maybe we send all of the numbers concurrently, and maybe we check the 035 $z only when there is not a match using the 035 $a.
The text was updated successfully, but these errors were encountered:
I looked into this and it's as I remembered. Currently VuFind does not use an API to check Hathi availability before generating the link. Instead, it just generates a link based on the MARC fields (and/or bib number) and the OCLC number. There is no checking, it just looks at the MARC and generates the link. In order to do what's being asked here, we would need to re-write all the logic to precheck using an API and generate the link asynchronously. This would be a fairly large project. I'm curious about how many bad links we generate because this has been in service for a long time.
Currently, VuFind should check for Hathi availability based on current OCLC number (which is an 035 $a field). Sometimes, Hathi uses an outdated or canceled OCLC number for the record on their end. We may have these canceled OCLC numbers in our records as 035 $z fields.
Can we also check the Hathi API for matches based on the 035 $z numbers? This could be done in several ways - maybe we send all of the numbers concurrently, and maybe we check the 035 $z only when there is not a match using the 035 $a.
The text was updated successfully, but these errors were encountered: