2020-07-13 Resource Access Meeting Notes

Date

13 Jul 2020

Attendees

Discussion Items

Time	Item	Who	Description	Goals/Info
2min	Administrivia	Andrea Loigman		Notetaker - Joanne Leary
5min	Users	Andrea Loigman	Feedback on custom fields	Is there feedback for Khalilah on User acceptance testing for custom fields in Users
20min	Item Status	Emma Boettcher	If an item has at least one Needed for on it and a Process, should this information be presented in one modal or two?	Decide how needed for and process info should display in Check In app
20min	Item records	Cate Boerema (Deactivated) & Kimie Kester	On the fly records	Review "on the fly" record mockups and approve so we can begin development: https://drive.google.com/drive/folders/1yUAeP4cDMsexe1hy1IaFWdNh6GTfN8iL

Meeting Outcomes

Functional Area	Product Owner	Planned Release (if known)	Decision Reached	Reasoning	Link to supporting materials	Comments
e.g. loans, fees/fines	Name	e.g. Q4 2018, Q1 2019	Clearly stated decision	Because... Because...	e.g. mock-up, JIRA issue
item status	Emma Boettcher		Display all item states information together if pertinent at Check In	Gives the user the most context for what they're doing as they check in items		Needs more attention to design, usability testing

Notes

Item status display upon checkin (Emma):
What should happen when an item being discharged has multiple actionable components? Should the system simultaneously display all components (available; needed for; process) with a single modal allowing the operator to continue or cancel the discharge? Or is it preferable to display one component at a time, with a corresponding modal?

Consensus is that all three components should display at once, with a single modal, to give the operator a clear picture of what is happening to the book. Ideally, the button labels should convey the consequences of each choice.
If the book has an outstanding request, that component should be made more prominent
If the discharge is cancelled, that action should be logged
We recommend that simultaneous display vs. sequential display of status components be user tested

Creating On-the-fly records (Kimie and Cate):
Refers to UXPROD-1057. In situations where the operator must create a record in order to check it out or put it on reserve, where should the action button ("New Fast-add Record") be located? What apps need to have this functionality?

For checkouts (such as for circulating a new issue of a journal), the group agreed that it should be located in the Checkout App, preferably below the topmost section, nearer to the Search section rather than where the End Session button is.
For creating equipment or personal copy records, the button needs to be part of the Inventory App, but must be structured in such a way that users can be blocked from blanket permissions to create standard records in Inventory. This might be be accomplished by defining a special space within Inventory.
Courses App should likewise have a Fast Add button that takes the operator to the Inventory app
In all cases, a marker should be added to the record that indicates the record was created through Fast Add. There is a cataloging standard that distinguished between actual inventory and non-standard inventory.
Fast Add records should have a Suppress from Discovery setting, configurable at the tenant level, which can be toggled on and off from the default setting
The Fast Add function uses a form; the form should include a more obvious Check-in Note field

Cate may have more questions at a future meeting.