2020-02-17 Resource Access Meeting Notes
Date
Feb 17, 2020
Attendees
@Andrea Loigman
@David Bottorff
@Donna Minor
@(OLD ACCOUNT) Erin Nettifee
@William Weare
@Jana Freytag
@Brooks Travis
@Emma Boettcher
@Joshua Lambert
@Kimie Kester
@Cheryl Malmborg
@Schwill, Carsten
Andy Horbal
@Mark Canney
@tpaige@umass.edu
@Elizabeth Chenette
@Joanne Leary
@Darcy Branchini
@Holly Mistlebauer
@Brian Arrigo
Discussion Items
Time | Item | Who | Description | Goals |
|---|---|---|---|---|
5min | Housekeeping | @Andrea Loigman |
|
|
15min | Fines/fees | @Holly Mistlebauer | Finalize decisions on who owns fines/fees. Discuss fine/fee connection to service points. | |
15min | Item state | @Emma Boettcher | Order closed item status | Determine behavior when an item with the status Order closed is checked out, checked in, requested, etc. |
20min | Item state | @Emma Boettcher | Custom item statuses (Availability) | Determine what needs to be configurable about custom item statuses |
5min | Meeting structure | @Anya |
| SIG is aware of the new purpose of the new meeting structure that will start on 2/20. |
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 |
| e.g. mock-up, JIRA issue |
|
Notes
Fines/fees (Holly Mistlebauer)
Who owns the billed fees/fines?
1. Finalize decisions on who owns fines/fees.
2. Discuss fine/fee connection to service points.
Locations can have more than one service point;
Concern: extra layer of abstraction;
Ex: holdings offsite; owning library wants to collect the fee/fine;
This is the MVP approach; we’re too far along.
What doesn’t work in this scenario? Are there onsite examples?
Fee/fine owner’s document:
https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=5669209
Effective Location Logic:
https://folio-org.atlassian.net/wiki/display/RA/Effective+Location+Logic
For now, we’ll stay with this decision: location gets the fee/fine; the two points at the top are how this is being developed.
RE: discussion from last meeting; what if a location has not been associated w/ a service point, or a service point has not been associated with a fee/fine owner—and there’s a fee or fine generated—what happens?
Holly created a “central admin” to create a default for these fees/fines.
What happens when you have a fee/fine associated with a catalog renewal? It will stay use effective location. Ex: item on reserve, fine/fee goes to reserve.
Item state -- Order closed item status (Emma Boettcher)
Follow-up from question at WOLFcon;
Item status: order closed
Item has been ordered, but not received, and the order has since been closed;
Record may be deleted or the item could still be received.
Check-out?
Check-in?
Should this be a status? Should it be a process instead?
Solution by ACQ? Change to order closed.
Should the item appear at circ, we need to be able to circ; we should not allow requests;
Alert for ACQ?
Does ACQ need a specific item status for this?
What’s ideal? If an order was closed: item status: unavailable; process status: in process?
What’s the RA objection? It’s not an item state (but it is a more specific version of not available);
Couple of questions: (1) the label itself; (2) specificity
We need to be able to undo this (check it out; check it in);
Determine behavior when an item with the status Order closed is checked out, checked in, requested, etc.
Outcome:
Check-in/check-out? yes
Requests? No
Missing, withdrawn, long missing? no
Item state in FOLIO:
https://folio-org.atlassian.net/wiki/display/FOLIOtips/Item+State+in+FOLIO
(Thanks Erin for this).
Meeting structure (Andrea for Anya Arnold)
SIG is aware of the new purpose of the new meeting structure that will start on 2/20.
Meeting will start 15 minutes later; agenda driven by early adopters.