Hi Justin,
"This improves the presentation and allows for title sorting but the search
takes *forever* to return and the results are always way off and frequently
do not return any results at all. Having just tried it, TPAC claims there
are no results whatsoever. Two or three page refreshes later it turns up 353
items. According to the DB we have 1951 distinct bibs with items in those
locations.
When TPAC claims there are no results, it's probably a result of
https://bugs.launchpad.net/evergreen/+bug/1103321. Basically, that's the
message that's returned when a search times out.
Also, once you hit a certain number of search results , the number of
retrieved search results is an estimate. The reason behind this estimate
has been explained to me many times, but I always forget the specifics.
My understanding is that it's a tradeoff between fast retrieval and
accurate result counts.
Kathy
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
[email protected]
Twitter: http://www.twitter.com/kmlussier
On 1/21/2014 8:55 PM, Mike Rylander wrote:
Justin,
The reason that search is slow is that you're effectively asking the
system to return all bib records, then pull up all their copies, then
pull up those copies' shelving locations, and finally filter out
records that do not have copies that do not have shelving locations in
your list. That is exactly the reason I built the new items
functionality.
With a little elbow grease, one could certainly use one of the many
XML format output options available for use with the new items list to
re-sort them however one would like, and display them exactly as one
would wish. Just try replacing "html-full" with "atom" or "rss2".
In fact, you could even use the OPAC to do the heavy lifting for you
if you were to extract the record IDs from the XML new item feed and
built a search using the record_list() filter and the sort(titlesort)
operator.
Perhaps, with likely less total effort, an opac format could be added
to the new item list, along with support for additional query
components (such as sorting) in the case of the opac format. A simple
redirect would do.
A wishlist bug sounds like a good idea. Perhaps time or funding will
materialize.
On Tue, Jan 21, 2014 at 6:21 PM, Holly Brennan <[email protected]> wrote:
"This improves the presentation and allows for title sorting but the search
takes *forever* to return and the results are always way off and frequently
do not return any results at all. Having just tried it, TPAC claims there
are no results whatsoever. Two or three page refreshes later it turns up 353
items. According to the DB we have 1951 distinct bibs with items in those
locations.
Has anyone else seen this behavior? Is there an open bug on it? Should there
be?"
Weird. We, too, use "New Books" as a location for searching. I just pulled
up the whole batch of new adult books in our library (5,070 records) without
a problem. It took maybe one second to load the page.
I didn't find a delay using your search method, either.
I know this is sort of non-information, but it could be helpful so I chimed
in. Let us know if you solve the problem!
-Holly
Holly Brennan
Library Technology Specialist
Homer Public Library
907-235-3180 (main)
907-435-3154 (direct)
[email protected]
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
Justin Hopkins
Sent: Tuesday, January 21, 2014 12:56 PM
To: Evergreen Discussion Group
Subject: [OPEN-ILS-GENERAL] Inconsistent/wrong search results when searching
by location in TPAC
Hi guys,
Like probably many others, we have noticed that Evergreen is lacking a
really good "new books" feature. We've explored this:
http://missourievergreen.org/opac/extras/browse/html-full/item-age/SRLWA
The presentation of this option isn't very good though, and ideally we'd
have the ability to sort by title.
It just so happens that our library who is most interested in this has a
shelving location at each of their branches called New Books. So we tried
this approach using search syntax:
http://missourievergreen.org/eg/opac/results?fi:item_type=&query=locations(1307,1308,1309,1310,1311,1558,1559)+&qtype=keyword&locg=174&sort=titlesort)
This improves the presentation and allows for title sorting but the search
takes *forever* to return and the results are always way off and frequently
do not return any results at all. Having just tried it, TPAC claims there
are no results whatsoever. Two or three page refreshes later it turns up 353
items. According to the DB we have 1951 distinct bibs with items in those
locations.
Has anyone else seen this behavior? Is there an open bug on it? Should there
be?
Regards,
Justin
