Date

Time	Item	Who	Description	Goals/Info/notes
2min	Administrivia	Jana Freytag	The 2021-07-05 meeting is cancelled ------ Bugfest June 30, Monday to July 9, Friday Info here: Bug Fest R2 2021 Juniper	Notetaker: Mark Canney
10 Min	Scheduled notices	julie.bickle	Update on: Notices scheduled in the past being sent: CIRC-1163 - Getting issue details... STATUS Printer management
45 Min	Title level requests	Stephanie Buck	Continued discussion and updates on TLR	Link to Google folder of mockups. We looked at 15-request-on-instance.png. It has been updated based on our conversation.

Time

Item

Who

Description

Goals/Info/notes

2min

Administrivia

Jana Freytag

The 2021-07-05 meeting is cancelled

------

Bugfest June 30, Monday to July 9, Friday

Info here: Bug Fest R2 2021 Juniper

Notetaker: Mark Canney

10 Min

Scheduled notices

julie.bickle

Update on:

Notices scheduled in the past being sent: CIRC-1163 - Getting issue details... STATUS
Printer management

45 Min

Title level requests

Stephanie Buck

Continued discussion and updates on TLR

Link to Google folder of mockups. We looked at 15-request-on-instance.png. It has been updated based on our conversation.

Meeting Notes

Bugfest. Will begin 6/30. Do we want to get together and talk about our experience? Yes, of course.

Julie. Discussion about https://folio-org.atlassian.net/browse/CIRC-1163. Notices scheduled and sent long in the past are being resent when a loan record is updated. This could happen for example, on a recall. Also, the full schedule of overdue notices is being sent at once - for example 8 notices in one test - and this feels like spamming to the researcher.

Rather than all the “old” overdue notices being resent, the Patron should receive a recalled/overdue notice as per UXPROD-2112, which could contain stronger wording than in a “standard” recall notice.

Feature: https://folio-org.atlassian.net/browse/UXPROD-2112. New triggers for overdue then recalled, and recalled and overdue.

Stephanie. Continued discussion and updates on TLR. Timing of this feature is R4. The focus of R3 is stabilizing modules, improving testing.
Review of column headers. Based on last week's discussion the first accordion is named Fulfillment in progress. And the column headers for each accordion are the same.
The Barcode column refers to Requester Barcode. Do we need to specify requestor? It was dropped for space. It would be nice to have a hyperlink to the patron record (just as item barcode is hyerlinked).
Are we agreed on the other columns? Yes.
The Second accordion is Requests in progress. Is position actual position in queue or re-orderable queue? he position column in the reorder request queue reflects the position in the reorder queue.
Rename Position to Order?
We like the idea of not displaying order for in-progress display
Or in-progress queue could display "in-progress" for the "0" position/order
The title will drop order here, or reorder will put order here, and then we'll talk further about whether we're going to repurpose this column or extend that type column next week when we can also review, hopefully, the new request details page.

Meeting Outcomes

Functional Area	Product Owner	Planned Release (if known)	Decision Reached	Reasoning	Link to supporting materials
e.g. loans, fees/fines	Name	e.g. Q4 2018, Q1 2019	Clearly stated decision	Because... Because...	e.g. mock-up, JIRA issue

Browser not supported