Baskets: select entire result set (OPAC)

Bug #1821198 reported by Galen Charlton
98
This bug affects 21 people
Affects Status Importance Assigned to Milestone
Evergreen
New
Wishlist
Unassigned

Bug Description

Users can currently select all records that are displayed on the current page of search results in the catalog and have them added to the basket. However, it could be convenient to be able to select all results for the current search to include in the basket.

Evergreen master

Revision history for this message
Galen Charlton (gmc) wrote :

I note that some limits may need to be placed on this sort of feature, including

- respecting the ctx.max_basket_size basket template paramter
- asking the user to confirm that they really want to include all results
- ensuring that very large baskets don't create problems when trying to do batch actions on them, in particular, placing holds.

A particular use case I'm aware of is being able to select all results for a search in the staff interface, then immediately moving the contents of the basket into a record bucket.

Changed in evergreen:
importance: Undecided → Wishlist
tags: added: baskets search
Revision history for this message
Elizabeth Thomsen (et-8) wrote :

Yes, we do this all the time -- do a search, look at the results, perhaps add limiters or otherwise refine the search, select all and move to a basket as a way to move them to a bucket. I'm attaching a screenshot from OverDrive Marketplace showing how they handle this -- I like the fact that even though the number of search results appears with the pagination above, they repeat the number of records in the checkbox text to make it clear what the user is requesting.

Re: Galen's suggestions:

"Respecting the ctx.max_basket_size basket template parameter" -- Agree, his should work the same way whether the user is individually selecting titles to add to the basket or is selecting all results

"Asking the user to confirm that they really want to include all results" -- Always a good idea

"Ensuring that very large baskets don't create problems when trying to do batch actions on them, in particular, placing holds" -- True, but that's really a problem with basket size and holds, not with Select All. When the user is adding items to the basket, we don't know which action they are going to choose -- Place Holds may be a problem for a basket of 500 (or whatever) bib records, but adding the records to a bucket may not be. Would it be better to let users add as many records as they want up to the maximum basket size (whether they select them individually, by selecting all on each page, or selecting all search results) and then handle the holds issue when it comes up, either with a warning or a limit that the system can only process holds in batches of 100 or whatever, and send them to View Basket where they can select batches of titles to place holds.

Having the Select All option wouldn't change any of the max size and performance issues -- it just saves the user who really wants all the search results from having to go from page to page to page to select them all.

Revision history for this message
Jennifer Weston (jweston) wrote :

Saving selection time and improving workflow with a "Select All" option would definitely be beneficial to users -- recognizing that guidance is needed on consideration of basket size parameters.

+1 to idea for including a limitation warning (ex: system can only process holds in batches of #)

Revision history for this message
Elizabeth Thomsen (et-8) wrote :

The ability to Select All and add to basket was added to the Angular Staff Catalog in Release 3.7, with a limit of 1,000 records.
See: https://bugs.launchpad.net/evergreen/+bug/1885179

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

Changing title to reflect that this is specifically a request for the OPAC since it is already available in the staff catalog.

tags: added: opac
summary: - Baskets: select entire result set
+ Baskets: select entire result set (OPAC)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.