2021-05-20 Resource Access Meeting Notes

2021-05-20 Resource Access Meeting Notes

 

Date

May 20, 2021

Attendees

 

@Martina Tumulla

@Sharon Wiles-Young

@julie.bickle

@Marie Widigson

@(OLD ACCOUNT) Erin Nettifee

@Erin Weller

@Cornelia Awenius

@Schwill, Carsten

@Joanne Leary

@David Bottorff

@Andrea Loigman

@Thomas Trutt

@Elizabeth Chenette

@Monica Arnold

@Andy Horbal

@Laurence Mini

@Cheryl Malmborg

@lisa perchermeier

@Darcy Branchini

@Robert Scheier

@Amelia Sutton

@Christine Tobias

@mey

@Jana Freytag

 

Discussion Items

Time

Item

Who

Description

Goals/Info/notes

Time

Item

Who

Description

Goals/Info/notes

2min

Administrivia

@Jana Freytag

Upcoming National Holidays:

Some EU-States:  Mon 24th of May

(Those interested in TLR can use this link to meet on 24th of May https://uni-goettingen.zoom.us/j/91648437420?pwd=ZmRYL203L0orbDFxLzlOK05ock56dz09)

USA: Mon, 31st May

-- This meeting is cancelled

 

  • New Page in our Wiki: Agenda Items - SMEs please put in topics you would like to discuss

  • TLR Subgroup (title level requests)

    • It might

 

 

  • Notetaker: @Jana Freytag

20Min

Process performance testing for notices

@Darcy Branchini

 

  • Process performance testing for notices (Darcy):

    • Process starts at midnight: 3,000 notices per hour are send

    • the whole process is tested: all scheduled notices, triggering, creating, sending notices

    • performance will also be depending on locale servers

    • Darcy will add the performance testing to the Iris notices documentation

    • Notice types:

      • Session depending notices: Check-in/-out, triggerd by item status chenge (pick-up, etc.)

      • Scheduled notices: overdue, hold-shelf notices, ...

    • Do we need differently configurable sending times for batch notices

    • Chicago need to be able to send ca 10,000 notices per hour

    • Scheduled  blocks are currently send in a first-come first-served manner

    • Which mod is involed: it's not in mod-configuration

      • Darcy will add this to the documentation as well

20Min

Configure a specific time (or time period) for scheduled notices to be sent

@David Bottorff

Discuss https://folio-org.atlassian.net/browse/UXPROD-2110

  • Configure a specific time (or time period) for scheduled notices to be sent UXPROD-2110

    • Timing and automated blocks will be negativly effected by this

    • Erin in Chat: Well, you're using overdue notices anyway, right? Since aged to lost can't send multiple items? I would argue multiple items should go first

    • Carsten: Scheduler for Jobs and reporting in SUB Hamburg

    • Some of the Batch jobs (aged to lost) already have an external Scheduler working

    • A feature for a scheduler was created but is not developed yet

 

Other topics

 

 

  • Side note (Carsten): Batch deletion of users in a scheduled way (Delete user after x number of years)

 

Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Reasoning

Link to supporting materials

Comments

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

  • Because...

  • Because...

e.g. mock-up, JIRA issue