2020-10-15 Resource Access Meeting Notes

Date

Oct 15, 2020

Attendees

@Sharon Wiles-Young

@patty.wanninger

@Cynthia Lange

@Cheryl Malmborg

@Monica Arnold

@Andy Horbal

@Andrea Loigman

@David Bottorff

@Kimie Kester

@Joanne Leary

@Emma Boettcher

@Molly Driscoll

@Anya

@Cornelia Awenius

@Brooks Travis

@Rameka Barnes

@Cate Boerema (Deactivated)

@mey

@Jana Freytag

Discussion Items

Time	Item	Who	Description	Goals/Info

Time	Item	Who	Description	Goals/Info
2min	Administrivia	@Jana Freytag	Holiday (Jana): 26th-30th Oct. Next Week: MM SIG going to come and talk to us about bound-with materials	Notetaker - @Rameka Barnes
20Min	Jira Issues: Users App	@patty.wanninger & @Maura Byrne	Clarifing some Jira Issues: Fielded Search: UXPROD-2092 Boolean/Query Search for Users UXPROD-1015 Make it more clear which fields are being search in a User search UIU-1027 https://folio-org.atlassian.net/browse/UXPROD-206
20Min	Patron note on request	@Cate Boerema (Deactivated)	I'm writing stories for Patron note on request (UXPROD-1800). - Review mockups: https://drive.google.com/drive/folders/1IeMw_4zTnFzRMRDOv3mcZvGhpAy63qBV - Notes from last discussion suggests that "Note would not be editable after request is created". What if note was created in error or mistake was made? What if things change over time? Do we need to worry about that? - What does this look like from a discovery standpoint? Would be interested in seeing demo or screenshots from current systems

Meeting Outcomes

Functional Area	Product Owner	Planned Release (if known)	Decision Reached	Reasoning	Link to supporting materials	Comments

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
Requests	@Cate Boerema (Deactivated)	TBD	SMEs really don't want these notes editable after the request creation to prevent patrons from changing things after fulfillment has begun and saying "but I put it in the note". Mockups look fine Let's change the label from Patron note to something like "Patron message to staff" or "Patron comments" to better distinguish from staff note API should support creation and viewing of patron comments but most discovery/OPACs people have today don't allow patrons to see these comments after they have created them Definitely want to have this data as a token in all request slips Nice-to-have it display in "Awaiting pickup" popup at Check-in Not necessary to have it display in the "In transit" popup at Check-in (especially since that popup isn't aware of whether the item is in transit for a request or in transit home)

Notes

Patty Wanniger: Jira Issues: Users App –

UXPROD 2092- Improved/"Fielded" searching in User app with Explicit Truncation - The addition of fielded search is a drop down format identical to the search in the inventory app. Search allows first/last name, barcodes, and emails. Boolean search allows you to combine searches, such as name and barcode etc. for exact matches.

Cate Boerema- Patron note on Request-

Reviewed UXPROD 1800- Patron note on request – Cate showed mockups. Mockups are fine

Questions from Cate:

Do we think patron notes should be edited after submitting/creation? No

In terms of Discovery, are users able to view patron notes/comments after they are submitted? No, most libraries discovery only allow users to add comments but not see their comments.

Label for patron note will be changed to “Patron message to staff” to better identify difference between staff note and patron note labels.

Pop up notes questions:

Should patron notes display in check-in? Yes

Should it display notes in the “In Transit” popup at check-in? Not needed, popup note wouldn’t be certain when checked-in whether the request was in route to its home location or for a request.