An OPAC integrated New Books feature sure would be nice

Bug #1271725 reported by Justin Hopkins
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evergreen
Wishlist
Unassigned

Bug Description

There seems to be quite a few libraries out there that would make use of a feature that presented the same information as the /opac/extras/browse/rss2-full/item-age view but wrapped inside the OPAC. Many libraries make use of a New Books shelving location, but as Mike explained searching on them is extremely time consuming for the DB.

Revision history for this message
Justin Hopkins (hopkinsju) wrote :

On 1/21/2014 7: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.
>
>
>>
>>
>> -----Original Message-----
>> From: <email address hidden>
>> [mailto:<email address hidden>] 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
>>
>>
>>
>>

Ben Shum (bshum)
Changed in evergreen:
status: New → Triaged
importance: Undecided → Wishlist
tags: added: feeds opac
Revision history for this message
Blake GH (bmagic) wrote :

What if we added a small setting on reports that would generate a row in action_trigger.event and point to a bookbag. Then AT could use the output of a report to populated a designated bookbag/bucket. Then there would be a prepopulated bucket that could be exposed in the OPAC via crafted URL and attached to an anchor tag.

Changed in evergreen:
assignee: nobody → Terran McCanna (tmccanna)
Changed in evergreen:
assignee: Terran McCanna (tmccanna) → nobody
Revision history for this message
Jane Sandberg (sandbej) wrote :

If this does get integrated into the OPAC as a carousel, I'd recommend that we make it adhere to the WAI-ARIA Authoring Practices for carousels -- https://www.w3.org/TR/wai-aria-practices-1.1/#carousel -- for maximum accessibility and usability.

Revision history for this message
Terran McCanna (tmccanna) wrote :

I'm closing this one since we now have carousels and those carousels can either be automatically populated with new items or they can be based on buckets that are manually populated with selected new items.

Changed in evergreen:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers