-
Notifications
You must be signed in to change notification settings - Fork 3
Add HathiTrust access indicator to search results page. #1990
Comments
Is there a way to use the overlap report to determine which titles are Hathi ebooks at index time? |
That's a good question - I don't know. I suppose that if the solution to
the main issue is to build a lookup table in the database, then that lookup
could happen at index time... the times we've tried to do lookups during
indexing the performance has been too slow to be usable, but that might be
different with advances in our Solr infrastructure. If we were indexing the
HathiTrust records, I think that would be the simplest solution, but since
we aren't either a lookup during indexing or an API call on result-load are
the two solutions I can see...? Open to other suggestions.
…On Wed, May 6, 2020 at 2:50 PM pgwillia ***@***.***> wrote:
Is there a way to use the overlap report to determine which titles are
Hathi ebooks at index time?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1990 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIK3SWD5MK7AMSYGDELSIDRQHEQNANCNFSM4M2YQCJQ>
.
--
Fender F-35
Cordoba 45FP
Ibanez M522SBS
Loar LM-520
Lafferty LB
|
Connor's boiling the overlap report down to the actual overlap and moving it into a table in MySQL so that we can do a lookaside query for the OCLC on the record page to inform the JS query to HathiTrust – if the index scripts have DB access, that would be one way to do it. I don't think we could do this as a JS query on the results page, at least without changing the index work anyways to extract the OCLC during indexing so that there's something to do those JS queries on, or doing a DB query per result, which would be prohibitively bad for performance (it's an N+1 minus the +1, basically). And then you'd still be running up against HathiTrust API limits. Easier to flag the Solr result during indexing and not do a bunch of secondary queries, imo. |
Oh yeah, that makes sense - for some reason I thought the overlap report
held a catkey, but I think that's not the case. Anyway, it's something to
figure out in phase two - this is more for UX reasons than functionality.
Thanks.
…On Wed, May 6, 2020 at 2:56 PM Matthew Barnett ***@***.***> wrote:
Connor's boiling the overlap report down to the actual overlap and moving
it into a table in MySQL so that we can do a lookaside query for the OCLC
on the record page to inform the JS query to HathiTrust – if the index
scripts have DB access, that would be one way to do it.
I don't think we could do this as a JS query on the results page, at least
without changing the index work anyways to extract the OCLC during indexing
so that there's something to do those JS queries *on*, or doing a DB
query per result, which would be prohibitively bad for performance.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1990 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIK3SVKYE3SCFKPMWG5BDDRQHFJJANCNFSM4M2YQCJQ>
.
--
Fender F-35
Cordoba 45FP
Ibanez M522SBS
Loar LM-520
Lafferty LB
|
Related to issue #1973 - it would be great to add an indicator in the search results page that these records are available online, since they aren't indexible under the "online" facet.
This could be similar (or even the same as) the current eBook indicator on the result page:
In theory, it would have to function as an API call like the book jacket images we pull from Google Books on the results page - my only concern would be the rate-limiting the HathiTrust API does...
The text was updated successfully, but these errors were encountered: