Page Comparison

• New Page in our Wiki: Agenda Items - SMEs please put in topics you would like to discuss
• TLR Subgroup (title level requests)
  • It might

• 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

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

• 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
    • Documentation from Marc Johnson about scheduling aged to lost - How to Schedule Age to Lost Processes
    • Aged to Lost Process Scheduling
  • A feature for a scheduler was created but is not developed yet

• Because...
• Because...