Date
...
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
1. Unavailable status: circ actions - Emma Boettcher
One result of last week’s discussion = need to split CDL off from ETAS. Options:
- Change status of CDL items to an existing or in-development status that is requestable + loanable with confirmation
- In process?
- Unavailable, if unavailable was requestable?
- Checked out
- Change status of CDL items to a new status such as Unavailable (requestable), Temporarily Unavailable, Embargoed, or Restricted
- Keep status of CDL items as is and differentiate them by use of circ rules and related fields
Emma is wary of new status solution for reasons of scope creep.
Feeling that adding a new status which is unavailable (for check out) but requestable would cause no harm and potentially make life much easier down the road.
Duke is using an Aleph-specific function to handle CDL now, for which there is no analog in FOLIO.
Aside from scope creep, is there any reason NOT to develop a new status? Answer = developer time, other things might not get done.
At MSU, CLD items are manually checked out and a red sticker is applied to it. They are only including reserve items in their CDL program. Comment that this is one of the ways CDL differs from ETAS, which is more of an “all or nothing” proposition.
Option #2, new status = group’s preferred solution. Next question: what do we want the status to be named? Consensus choice = Restricted, with Embargoed as a second choice.
Question about whether or not staff should be notified about items which are suppressed from discovery upon check in. Consensus opinion = yes.