2018-10-18 Resource Access Meeting Notes

5min

Housekeeping

@Andrea Loigman

15min

Deceased flag

@Chris Manly

Determine if a flag for deceased patrons is needed.

5min

Next steps for overrides

@Emma Boettcher

10min

In transit for pick-up

@Cate Boerema (Deactivated)

Item status use cases

Approval of use cases

25min

Paging requests

@Cate Boerema (Deactivated)

Item status use cases

Approval of use cases

e.g. loans, fees/fines

Name

Clearly stated decision

• Because...

• Because...

e.g. mock-up, JIRA issue

Requests

@Cate Boerema (Deactivated)

"Pickup location" in Request record can be renamed "Pick up service point" for clarity

• Because the pickup location menu actually contains service points - the developers were quite confused by this

• While "pickup service point" is not language people would like to expose to patrons, they can easily relabel in patron systems

Requests

@Cate Boerema (Deactivated)

Rows 3 - 7 of this document are approved

Item status use cases

Need follow up discussions on what data is captured when an item is checked in and how that data displays (should be on the item record somewhere)

Requests

@Cate Boerema (Deactivated)

Rows 9 - 13 of the same document are approved

Item status use cases

• Need follow up discussion on what "Needed for" values should be triggered by recalls (and holds, for that matter)

• Need follow up discussion on how the system knows when and how much to truncate due dates for recalls

Loans

@Emma Boettcher

Mockup approved (first pass)

• Adequately addresses scenarios from most of the SIG & first implementer (Chalmers)

Does not adequately address scenario of needing to assign different due dates to non-renewable items, but will address later