2019-6-27 Resource Access Meeting Notes
Date
Attendees
- Andrea Loigman
- Kai Sprenger
- Sharon Wiles-Young
- Darcy Branchini
- Mark Canney
- Kim Ammons
- Cate Boerema (Deactivated)
- Emma Boettcher
- lisa perchermeier
- Kimie Kester
- Elizabeth Chenette
- Steven Turner
- Rameka Barnes
- William Weare
- (OLD ACCOUNT) Erin Nettifee
- Catherine Smith
- Anya
- David Bottorff
- Jana Freytag
Discussion Items
| Time | Item | Who | Description | Goals |
|---|---|---|---|---|
| 5 min | Housekeeping | Andrea Loigman |
| |
| 10min | Loans | Emma Boettcher | Anonymized and closed loans | At what point is information like patron group, effective location, etc. "frozen" on a closed loan? At anonymization? When closed? And what data is captured - values for those fields at the start of the loan, or at the end? |
| 45min | Requests | Cate Boerema (Deactivated) | Re-ranking requests | Review gap analysis ranking on UXPROD |
Meeting Outcomes
Functional Area | Product Owner | Planned Release (if known) | Decision Reached | Comments |
|---|---|---|---|---|
| e.g. loans, fees/fines | Name | e.g. Q4 2018, Q1 2019 | ||
| Loans | Emma Boettcher | Though information such as patron group or item's effective location may change over the course of the loan, it is most important for reporting to know what those values were at the time the item was loaned, as opposed to when the loan closed. | Very important for reporting, perhaps less important for viewing closed loan details. |
Notes
Andrea:
Reminder to update our Experience and expertise page
Reminder to add your institution's info to the Ave/Peak Notices in Bulk tab of the Patron Notices doc
Emma:
On the loan details screen, closed loans; at what point are details fixed or frozen? For example, "patron group" or "material location". Group agreed details should be fixed at the time of the loan close. For statistical reasons it is paramount that details are captured so that reports can be run on important elements like "patron group" at the time of the loan. The loan details screen display is not as important but logs need to be accurate. For example, if an item were checked out by a graduate student - that fact needs to be captured - in spite the fact the student subsequently becomes an alumnus.
Cate:
Together we reviewed several UXPROD features in the gap analysis to determine whether they can be reranked.
UXPROD-1558: Auto Ordering of Request Queue Based on Type. Can wait due to low utilization of both hold types (recall and hold) simultaneously.
UXPROD-113: Fulfilling delivery requests. Would it be possible to do a lite implementation for go-live? Need to record the fact patron is requesting delivery. Also, need to do notification about delivery method. What can we do minimally for go-live?
UXPROD-1320. Configure Allowable Item Statuses for Request Types. Group agreed when Custom Statuses are available in FOLIO then this feature is more desirable.
UXPROD-923: Requests in-app report: Pick list. Is the CSV export adequate initially? Includes all information needed.
UXPROD-236: Requests Permissions. Permissions for basic CRUD functions can be done easily. Permission for Action-based (e.g. cancel) will have to wait.
UXPROD-925: Requests in-app report: Hold shelf clearance. Is the CSV export adequate initially? Need to know what fields are available.
UXPROD-1242. Manually Reorder Request Queue. Need auto-sorting for institutions with both recalls and holds.