2023 Meeting notes

2023 Topics

DateTopic(s)NotesLead(s)

Loan-related comments





Usability of using actual cost for lost items



2023-01-12Unassigned fee/fine featuresGo through Holly's dashboard https://folio-org.atlassian.net/secure/Dashboard.jspa?selectPageId=12627
2023-01-19PO assistance groupCollecting Ideas / brainstorming
2023-01-23Unassigned fee/fine/patron block features
2023-01-26

Multiple fee/fine charges or actions (pay, waive, transfer, error or refund) on a single notice for a patron 




2023-01-30

Patron notices to proxy

Future fees/fines

UI: Show columns on Fee/fines option


2023-02-13Open Discussion Round
all
2023-02-27Recalls

Show & Tell

Questions & Discussion

2023-03-06Open Discussion Round
all
2023-03-09Bugfest

Goal: assisting each other in bugfest testing, talking through test cases and processes

Come with any questions you might have about testing or just reserve this time for doing your testing in company.

2023-03-16Lotus HF1: Automated Block for Max Amount Owed Not Removed When Aged to Lost Item Returned
2023-03-20SIG Survey results and what we want to do with them
2023-03-23TLR recalls 
2023-03-30 Open Discussion Round
all
2023-04-06 Open Discussion RoundScheduled notices: What happens in FOLIO?all
2023-04-13 Notices on automated fees/finesDiscuss option for notices for actioning on automated fees/fines
2023-04-20 Planned features for PoppyFeature overview slides 
2023-04-27 Open Discussion Round

Which subgroups are active?

Status of patron notices for bursar transfer and message tokens? (Laurence)

Is this a bug with fine/fees? (Susan)

all
2023-05-04 Open Discussion RoundA walk through the features:

Laurence Mini asks about typical user stories for Issue 1353

Susan Kimball: a Bug in Chrome in Nolana - FOLIO does not detect your service point

all
2023-05-08 Patron noticesAdding "User address" section to the patron notice tokens.
2023-05-11 Title Level RequestsKick off User acceptance testing starting May 15th
2023-05-15 RA SIG OnboardingPlease have alook at the Recording of this meeting if you want to know about our SIG: Recording of 2023-05-15
2023-06-05 Multiple fee/fine actions
2023-06-12

Allow proxy to make requests on behalf of sponsor(s) via opac/discovery


Notices




Present the (Poppy?) lastest notice development + ask a few questions 

2023-06-15

WOLFCon 23 Planning

Open Discussion round



2023-06-29

Notices- Continuation from Monday


fee/fines


2023-07-10 Request Anonymization
2023-07-13 Update request queue page namesSteph Buck presented a slide deck with proposed changes to wording used on screens for Requests (View, Reorder, and Queue). These were suggestions stemming from user acceptance testing for title level requests.
2023-07-24 Open Discussion round
  • WOLFCon Session planning
  • Gaps we would like to discuss
  • Questions from the group

Gaps that came up during the meeting resulting in our Gap list of RA SIG

  • SIP2
  • Fee-Fines
  • Item status
  • 3 part item state
  • Recalls receiving separate notice
  • age to lost policies
  • bundle request notices based on shelf expiration date
all
2023-07-27 Gap list discussions

Gaps that came up during the meeting resulting in our Gap list of RA SIG

  • SIP2
  • Fee-Fines
  • Item status
  • 3 part item state
  • Recalls receiving separate notice
  • age to lost policies
  • bundle request notices based on shelf expiration date
all
2023-08-07 Open Discussion round

WOLFCon Planning

Gap List discussions

all
2023-08-14 Open Discussion round

WOLFCon Planning

Gap List discussions

all
2023-08-31 Open Discussion round

WOLFCon Planning

Gap List discussions

all
2023-09-07 Sort page request pick slips by call number
2023-09-21 Limit number of requests per patron The topic of this meeting was request limitations and how fine grained they should be, or how fine grained do institutions need them to be. Based on the conversations Jira(s) will be created.
2023-10-05 Item cost fieldDiscuss the possibility of adding an item cost field to the item record to support Actual Cost functionality
2023-10-12 Gap List - Planning and moving forward
  • Moving forward, we will work in small groups (break out sessions) on the various features on the Gap List.
  • More of a group effort but one person can act as a guide/leader. 
all
2023-10-16 Loan CommentsPresent the poppy feature to the group
2023-10-26 Bug fest

Discuss the tests.

Ask questions.

bring up new features / improvements

all
2023-11-02 Bug fest

Discuss the tests.

Ask questions.

bring up new features / improvements

all
2023-11-09 First Gap List Working Session
The First topics are:
  • Anonymization - Cornelia will take the lead.  This topic will be postponed
all
2023-11-13 Reminder Fee Feature PresentationSee UXPROD-2015 and related issues
2023-11-16 Changes in request policy

Presentation and discussion of UXPROD-2689 

2023-11-27
  1. 1 Gap List Working Session

Continuation



2023-12-07 Automatic renewals

This is the continuation of the gap list working group meeting.

Jira: Automatic renewals

2023-12-11

Helper features







fee/fines

WOLFCon 23 Topic:

Talk about helper features

Talk about the Checklist Feature that was thought up by the Open Access SIG. Do we have use cases for this in 'our' Apps?

The other is the history tracking feature that was just added to invoices could be used in other areas.




2023-12-18 Bound withHow would RA like bound-with titles to be displayed in the Check-out, Check-in, Request screens, Patron notices and probably more places?


2023 Agenda Items


Date addedTopicPersonTime requiredScheduled date

 

Patron Block Condition: outstandig fee/fines by maximum No. days ; Maximum days by overdue 25 Minutes

 


14 Nov 2023

Discuss setting shelving lag time by location instead of service point UXPROD-527 - Getting issue details... STATUS

Cheryl Malmborg30 minutes

 


 

Present the poppy feature to the group


UXPROD-3913 - Getting issue details... STATUS

30 Mins

 

(tick)
2023-09-25Discuss the possibility of adding an item cost field to the item record to support Actual Cost functionality30 mins?

 

(tick)
2023-08-31

Expand on the specs for sorting page slips by call number: UXPROD-2683. Thomas Trutt thinks that this will be 3 requests: Add data to the request record, Sorting the notices by a specific field, and adding a token to the slips. Claire Hoag (CU Boulder) and Susan Kimball have expressed interest in this feature.

15 mins?2023-09-07(tick)
2023-08-31

Talk about helper features

Talk about the Checklist Feature that was thought up by the Open Access SIG. Do we have use cases for this in 'our' Apps?

The other is the history tracking feature that was just added to invoices could be used in other areas.

20minsafter the demo in App interaction SIG
2023-06-21Update request queue page names20 mins2023-07-13(tick)
2023-06-07

Present the (Poppy?) lastest notice development + ask a few questions on some things I have found: 
UXPROD-3573 - Notify user when item(s) are charged aged to lost (automated f/f) with ACTUAL COST / Scheduled notices Closed  

UXPROD-3740 - Notify user when item is returned, and ACTUAL COST gets cancelled / Scheduled notices Closed

UXPROD-3998 - Bundle aged to lost fee/fines into a single notice (“Multiples”) when charging: Overnight Closed

UXPROD-3999 - Bundle overdue fines into a single notice (“Multiples”) when charging: At check-in Closed

45 mins

 

(tick)
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:

  1. Per 1 button (e.g. charge, pay, etc.) - all the currently ticked open fee/fines are bundled.
  2. A shopping cart check-out: all actions taken in that session are bundled, i.e. receipt.
  3. "Here are all your open fees/fines"
    1. Button to send this in the user UI?
    2. Recurring? If so, what frequency + when to stop?
45 mins

 

(tick)
2023-05-15

Developing functionality to enable Discovery layer for proxy requesting on behalf of sponsors. Edge API updates needed to make this possible  UXPROD-3930 - Allow proxy to make requests on behalf of sponsor(s) via opac/discovery Open  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?

15 mins?

 Susan Kimball  

(tick)
2023-05-04Adding "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 mins2023-05-08(tick)
2023-04-03There are currently no topics for 13th April - could I please use that time to discuss option for notices for actioning on automated fees/fines?45 mins2023-04-13(tick)
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 (smile) )

30 mins2023-04-20(tick)
2023-01-18

UXPROD-2252 - Multiple fee/fine charges or actions (pay, waive, transfer, error or refund) on a single notice for a patron Open

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 mins2022-01-26(tick)
2022-12-21

UXPROD-3937 - Send patron notices to the proxy who checked out the item or requested the item Draft

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 mins2022-01-30(tick)