| Date added | Topic | Person | Time required | Scheduled date |
|
|---|
| 2021-05-21 | demo of UChicago's Pull List app (which creates unified pick list from ILS, Illiad, Relais, etc.) No hurry on this, but I know some folks were interested in seeing this as a possible model for something that could be developed on the FOLIO platform | | 20 min | 2021-05-27 |  |
| 2021-05-24 | Discussion about equipment management (requested from multiple participants on 5-24-2021)
- how libraries are thinking about managing equipment in FOLIO
- other software options libraries might have used or are considering using if not FOLIO
- migration considerations for equipment
- circulation considerations for equipment
| | 45 min | 2021-06-07 | |
| 2021-05-24 | Discussion of integration with online payment services - how many libraries currently offer online payment options? how many would like to do so?
- what are libraries that offer online payment options doing now?
- what would the priority be for FOLIO to integrate with online payment services?
| David Bottorff | 30 min | 2021-05-27 | |
| 2021-06-21 | Update on: - Notices scheduled in the past being sent:
| Jira |
|---|
| server | FOLIO Issue Tracker |
|---|
| serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
|---|
| key | CIRC-1163 |
|---|
|
- Printer management
| | 5-10 min (depending if questions) | 2021-06-28 | |
| 2021-07-19 | Patron notice features - candidates for deletion | Jira |
|---|
| server | FOLIO Issue Tracker |
|---|
| jqlQuery | issuetype = "New Feature" AND "Epic Link" = UXPROD-18 AND labels in (delete_candidate) AND status != Closed ORDER BY fixVersion ASC |
|---|
| count | true |
|---|
| serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
|---|
|
| | 10 min | 2021-07-19 | |
| 2021-07-19 | Patron notice send errors in circ log | | 15 min | 2021-07-29 | |
| 2021-08-17 | Request for help collecting information about calendar size (in current system, FOLIO, or both) | | 10 min | 2021-08-23 | |
| 2022-05-09 | The pros and cons of logic branching and advanced conditioning in notice and slip tempates: - Add the preferred name token to the list of patron notice tokens -
| Jira |
|---|
| server | FOLIO Issue Tracker |
|---|
| serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
|---|
| key | UICIRC-462 |
|---|
|
- Anonymous request identifier for staff slips and notices -
| Jira |
|---|
| server | FOLIO Issue Tracker |
|---|
| serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
|---|
| key | UXPROD-2435 |
|---|
|
- Add token "Today's date" to staff slips + formating options -
| Jira |
|---|
| server | FOLIO Issue Tracker |
|---|
| serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
|---|
| key | UXPROD-3224 |
|---|
|
| | 20 min | 2022-05-16 | |
| 2022-05-09 | Multiple fee/fine charges or actions (pay, waive, transfer, error or refund) on a single notice for a patron - | Jira |
|---|
| server | FOLIO Issue Tracker |
|---|
| serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
|---|
| key | UXPROD-2252 |
|---|
|
Check the use cases again + compare them against what is technically (reasonably) feasible. | | 45 mins | 2022-05-23 | |
| 2022-06-17 | MODEMAIL-73 - Retry sending email on temporary failure (4xx) → Explain and discuss the consequences. | Julie Bickle | 30 mins | 2022-06-23 | |
| 2022-12-21 | | Jira |
|---|
| server | FOLIO Issue Tracker |
|---|
| serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
|---|
| key | UXPROD-3937 |
|---|
|
There are a number of questions for the SIG. I'll post them in the Slack channel, but I would like to hear people's comments in person, as well:
- For scheduled notices: Should the notice be linked to the recepient (i.e. proxy) immediately when the notice is created? Or should the recipient be determined just before sending the notice, in case the proxy-sponsor relationship changes after the scheduled notice is created?
- This setting affects ALL notices tied to that loan or request, i.e. loan, requests and fee/fine notices. Is this ok?
- When looking in the circ log: Do you need to know that this notice was sent to the proxy, rather than to the sponsor?
| | 30 mins | 2022-01-30 | |
| 2023-01-18 | | Jira |
|---|
| server | FOLIO Issue Tracker |
|---|
| serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
|---|
| key | UXPROD-2252 |
|---|
|
I will present a plan for how this could work, and would need SIG feedback. I'd like to squeeze this into Poppy (scope close date = 17 feb) - so could I please present this on 26 Jan?
I should have a deck to share already by 20 Jan. | | 45 mins | 2022-01-26 | |
| 2023-03-27 | I will present Poppy features that Vega has planned to work on. Maybe with Julie Bickle if she is available (Stephanie Buck : Julie is available  )
| | 30 mins | 2023-04-20 | |
| 2023-04-03 | There are currently no topics for 13th April - could I please use that time to discuss option for notices for actioning on automated fees/fines? | Julie Bickle | 45 mins | 2023-04-13 | |
| 2023-05-04 | Adding "User Address" section to the patron notice tokens. Two questions:
- Where to add those tokens - what looks and feels best?
- Criterium for population = “Use as primary address” selected
| | 30 mins | 2023-05-08 | |
| 2023-05-15 | Could I please have a session to thrash this topic out again: Multiple fee/fine actions in a single notice. The next session I would be available is 1st June.
I'll prep better and add more detailed questions, but so far here are the notes I have: Possible solutions: - Per 1 button (e.g. charge, pay, etc.) - all the currently ticked open fee/fines are bundled.
- A shopping cart check-out: all actions taken in that session are bundled, i.e. receipt.
- "Here are all your open fees/fines"
- Button to send this in the user UI?
- Recurring? If so, what frequency + when to stop?
| | 45 mins | |
|
| 2023-05-15 | Developing functionality to enable Discovery layer for proxy requesting on behalf of sponsors. Edge API updates needed to make this possible | Jira |
|---|
| server | FOLIO Issue Tracker |
|---|
| serverId | 6ccf3fe4-3301-368a-983e-20c466b11a49 |
|---|
| key | UXPROD-3930 |
|---|
|
via EDS or other discovery layer. Is there interest in getting this prioritized, especially since this work is only the first step in getting it functional in discovery layers? | Susan Kimball | 15 mins? | |
|
