Page Comparison

Date

20 May 2019

...

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Comments

e.g. loans, fees/fines

Name

e.g. Q4 2018, Q1 2019

Clearly stated decision

Requests

Expired holds report

Logic defined above seems okay as long as we also include items where there are no more requests in queue
Typically you'd want to just get the items that need to be cleared from the service point to which you are currently logged in
However, there are some cases when you'd want to "zoom out" and include other service points (that maybe don't clear own shelves because they are unmanned, for example)
When we have a proper in-FOLIO report for this (as opposed to a csv) we might offer filters so you can include/exclude other service points from the report. For the csv solution, we should just ask Chalmers what they would find most useful.
User story:
Jira Legacy
server System Jira
serverId 01505d01-b853-3c2e-90f1-ee9b165564fc
key UIREQ-273

Requests

What happens to Paged items for which the queue has been cleared

SIG is okay with status going back to Available even when the previous state was recently returned
This approach may run into issues when/if it's possible to create page requests on custom statuses (not sure if that will be possible, though). Will need to revisit this design when we get to that feature.
For the case when the queue empties due to expiration, SIG was okay with the status staying Paged. This is such an edge case, it's not worth worrying too much about.