There are ideas with far less votes that have been implemented/planned for implementation, even some with single digit up votes. I'm not sure how a commonsense improvement like this gets overlooked for years.

I agree.

MEEP candidate for the Sierra 7.1 release

Functional Requirements (what does it need to do?)

● Each item barcode appears exactly once per list.
● System suppresses duplicate rows for the same item_id.
● All holds remain tracked; paging list simply avoids duplicate display.
● Optional counter on the item line: “Holds pending: X”.
● Only pageable items appear.
● Multiple holds for a single item do not generate multiple pull requests.
● Paging list behavior is identical aside from deduplication.

Fixing this issue is critical as it is a massive pain point for staff. We had a title on the paging list with 18 entries, even though only 4 items were available to fill holds at that library. Basing the paging entries of items solely on the number of holds for that title doesn't make sense -- libraries should see paging entries based on the available items that are eligible to fill those holds. If I have two items to fill two holds, I should only see that title on my list twice. The current structure is a waste of paper and staff time.

This has come up at multiple meetings with our circ colleagues as a pain point. Having the title duplicated on the paging list doesn't serve a practical purpose for staff members pulling items to fill holds, and it's ultimately a source of confusion and a waste of paper.

I agree, we've received numerous complaints about this over the years from our member libraries. For example, a book club has 15 holds for one title, a library with 1 available copy has the title repeated on their paging list 15 times.

Any update on this? This was marked "under review" over 5 months ago.

We have received sooooooo many complaints about this system behavior over the years. Staff have had to waste an inordinate amount of time on deduping the produced lists, which has only gotten worse with the introduction of the pagination issue (SIERRA-38727) that was introduced in 6.0.

Duplicate instances of a single item frequently appear on Bib Paging Lists resulting in confusion and either wasted paper (up to *7* pages were printed for a single item once) or wasted time deleting those lines before printing. There is no need for the paging list to alert us to multiple holds for any item, especially if we can't physically fulfill those holds.