Date
...
Patty Kishman
Discussion Items
| Time | Item | Who | Description | Goals/Info | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2min | Administrivia | Charlotte Whitt & Laura Daniels are planning the work on a better display of the result list in Inventory, and if they should continue doing smaller improvements of the current display using the multi column list display (in the second pane) or maybe go for the long term solution, and implement the hierarchical display (UXPROD-491). They are planning a working session in a smaller group with maybe 2-3 members from each SIG. The kick off meeting could be this workshoplike meeting, where we together with Kimie write up our improvements, suggestions. See maybe Filip's UX live demo: https://ux.folio.org/prototype/en/inventory And after the workshop then Kimie would refine the UX mock ups, and we would follow up with a weekly meeting, maybe 3-5 weeks. Who wants to be part of that group? |
| |||||||||||||||||||||||||
| 15Min | Displaying User data in the checkout app |
| ||||||||||||||||||||||||||
| 15Min | Requests | Review
|
...
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 |
| e.g. mock-up, JIRA issue | |
Notes
Christine will ask at her institution to see if anyone there might be interested in joining the working group to discuss improving the display of instances / holdings / items in the inventory UI. Anyone from the RA SIG who might be interested in joining can let Jana know.
David brought up the question of having preferred pronouns for patrons be given a more prominent display than is currently possible from custom fields. The UXPROD for preferred pronouns was closed because it was thought that custom fields would serve for this, but the current limitation on usage of custom fields makes them insufficient for using them to record preferred pronouns. One approach would be to allow the designation of certain custom fields to appear in the patron info field. This could have other uses, and make custom fields more widely useful. It was decided, however, that it would be best to have preferred pronoun be in the core user record, as has been done with department. Erin pointed out that making custom fields more powerful could entail a lot of development work.
Having a preferred name field that, when present, could serve to over-ride the formal name would also be a desirable feature.
It was decided that there wasn't a way to allow patrons to access the User record and record their preferred pronoun themselves. It was also decided that preferred pronoun should be unassigned by default.
The group agreed that preferred pronouns were important to have for the checkout screen and in the user record, but not critical for notices.
David will bring the matter of having a dedicated field in the user record to the User SIG, and see that a new JIRA for this is created.
Brooks showed his suggestions on how to deal with the issue of a staff member extending the due date of an item that has a hold request or a recall on it (UXPROD-2972). Currently, renewals are blocked on such items, but it is possible for staff to extend the due date. Cornelia mentioned that there is warning text that appears if the due date is extended for an item with a recall on it, but there is no confirmation pop-up.
In Check-out or Actions module, there would be a pop-up that would display, informing staff that there was a request/recall on an item, and asking staff to Cancel or Confirm the due date extension. The name of the item would show, and would link to the request queue for the item.
In the case of extending due dates from the Loan list of a patron, there is also the case of a staff member selecting multiple items. In this case, there should be a separate confirmation pop-up for each item that has a hold request or recall on it. Brooks suggested that the buttons should say Skip and Confirm in this case, as otherwise Cancel might be misunderstood (even if the item name appears in the pop-up) as meaning that all the due date extension actions will be canceled. There was discussion on whether it would be problematic to have different language for this special case. Also, whether Skip might be misleading language for the last pop-up. Kimie will bring up the question of wording in the UI channel.
Brooks mentioned a bug with the date picker not populating fields. Brooks has not been able to replicate this bug, but will create a ticket for it after investigating further. Brooks also mentioned a bug with regard to adding a fee/fine to a user record – when the 'charge only' button is clicked, nothing happens. Brooks submitted a ticket for this.
Jana will put discussion of the findings of the next major Bugfest on a future agenda. Jana will let the RA SIG members know whether we are meeting on Thursday 3/25 (possibly to discuss documentation) or not.