Content Comparison

🗣️Discussion Points:

1. Volunteer for Spreadsheet and Ticket Updates (11:02 - 11:04)

   • Main Topic:Susan requested volunteers to help update the spreadsheet and tickets during the meeting.
   • Details:Susan expressed difficulty in multitasking and leading the meeting simultaneously. Thomas offered to help.

2. Auto Ordering of Requests Queue (11:05 - 11:10)

1. • Main Topic:Discussion on JIRA:UXPROD-1558 regarding auto ordering of requests queue based on type

1. • (recalls

1. • before holds).
   • Details:Participants discussed the management of recalls and holds for different patron groups. Erin

1. • mentioned that their institution only uses recalls for reserves or when items cannot be obtained from another library, while holds are used internally for specific programs like laptop lending. Thomas

1. • added that New York State residents and library cardholders can only place holds, not recalls. The consensus was that this feature is desired behavior for prioritizing recalls for certain patron groups, such as faculty members over local borrowers. The feature was deemed legitimate and necessary for further refinement.

2. Request Policy Control (11:

1. 11 - 11:19)

   • Main Topic:JIRA:UXPROD-1559 regarding controlling request fulfillment options

1. • in the request policy

1. • .
   • Details:Discussion on renaming the policy and the implications of service point defaults. Susan

1. • and Thomas

1. • debated whether the service point default should be part of the user record or the request policy. Thomas suggested that the discovery layers should utilize the preferred service point setting, allowing users to update it and have it automatically selected when placing a request. The feature was considered useful for fringe cases, such as facilitating requests for patrons at different locations like New York City and Geneva campuses. The consensus was to keep the feature for further refinement, with a focus on developing the request policy beyond its current state.

2. Support Moving Request Above Page (11:20 - 11:23)

1. • Main Topic:JIRA:UXPROD-1560 regarding moving requests above page in the queue.
   • Details:Participants debated the complexity and fringe nature of the feature. Susan

1. • and Thomas

1. • discussed the backend complications of implementing this feature, such as canceling the original page request and making it a hold request. Thomas argued that this feature is overly complicated and more appropriate for special handling rather than manipulating the request queue. The consensus was to kill the feature due to its limited use cases and the complexity involved in its implementation.

2. Boolean Query Search for Requests (11:24 - 11:30)

1. • Main Topic:JIRA:UXPROD-1561 regarding adding Boolean query search capabilities to the requests app.
   • Details:Participants discussed the need for more filter options rather than complex search capabilities. Erin

1. • expressed a preference for filter options, such as filtering by location, which is coming in the Sunflower release. Thomas

1. • suggested closing the feature and reviving it if Elasticsearch is used in the future. The consensus was to close the feature, with the possibility of revival if search capabilities are expanded using Elasticsearch.

2. Improved Fielded Searching (11:31 - 11:33)

1. • Main Topic:JIRA:UXPROD-1562 regarding improved fielded searching in the requests app with explicit truncation.
   • Details:Participants discussed the current search capabilities and the need for better data practices. Joseph

1. • mentioned that staff often do quick searches for user barcodes, and Susan

1. • confirmed that both item and user barcodes can be searched. The consensus was that the current search capabilities are adequate, and the feature was closed.

2. Display Call Number Sort Code (11:34 - 11:39)

1. • Main Topic:JIRA:UXPROD-1563 regarding displaying the call number sort code in requests.
   • Details:Participants discussed the need for shelving order in the CSV export for correct sorting. Olga highlighted the importance of shelving order for sorting items correctly in Excel. Susan

1. • suggested renaming the feature to include shelving order in the CSV export. The consensus was to keep the feature for further refinement, as it is considered low-hanging fruit and relatively easy to implement.

2. Prevent Local Page Requests (11:40 - 11:41)

1. • Main Topic:JIRA:UXPROD-1564 regarding preventing local page requests.
   • Details:Participants discussed the validity of the feature and its usefulness for different institutions. Thomas

1. • mentioned that Cornell still pulls local requests manually, and Joseph

1. • added that Spokane Public Library allows patrons to place requests to prevent others from grabbing items before they arrive. The consensus was that the feature is a reasonable request and should be kept for further refinement.

2. Request Count API (11:42 - 11:45)

1. • Main Topic:JIRA:UXPROD-1565 regarding displaying request counts to users without permission to view requests.
   • Details:Participants discussed the security implications and the need for systematic handling of permissions. Susan

1. • noted that inventory currently shows the number of requests even if the user does not have permission to view them, which is a security loophole. Laurence

1. • mentioned that other apps successfully show numbers without links for users without permission. The consensus was to keep the feature for further refinement to address the security loophole and ensure consistent handling of permissions.

2. Request Staff Notes (11:46 - 11:55)

1. • Main Topic:JIRA:UXPROD-1566 regarding capturing staff notes when overriding a patron block on requesting.
   • Details:Participants debated the usefulness and storage of staff notes. Thomas

1. • mentioned that staff notes are part of the notes app and can be assigned to someone, while patron comments are part of the request itself. Susan

1. • questioned the use case for capturing these notes and where they are stored. The consensus was to keep the feature for further refinement, with a focus on understanding the use case and storage of staff notes.

2. Revert Loan When Recall is Canceled (11:

1. 56 - 11:57)

   • Main Topic:JIRA:UXPROD-1567 regarding reverting loan due dates when a recall is canceled.
   • Details:Participants expressed frustration over the lack of this feature, as recalled items have their due dates changed but do not revert when the recall is canceled. The consensus was that this feature is necessary and should be kept for further refinement.