Page Comparison

App Interaction SIG request:

• Define and describe the architecture for how to keep data in sync across multiple apps
• Define and describe the architecture for seamless push and pull of data between apps (interaction)
• Wikipage:AppInt:Data synchronization

Invitation: I would like to invite you to a related discussion with the App Interaction SIG on Friday, June 11th at 11:15 am ET / 4:15 pm UK / 5:15 pm CET.

→ Quick update on that and preparation for the meeting tomorrow

--------

FYI: The live captions are uploaded here: https://drive.google.com/drive/folders/0B7G8S7WF6N20NkVtc0x6ZmwxaGc

Another look at our updated gap analysis: Gesammelte Gaps deutscher Institutionen (in English)

https://folio-project.slack.com/archives/C3G05TF3R/p1622637942064600

1. On scenario is where an overdue item gets a recall, and the library has configured recalls to change the due date but to _not_ extend the due date. This triggers the scheduled notices to be regenerated based on the original, already past, due date. The patron gets a recall notice and all courtesy and overdue notices scehduled to be sent up until the date of the recall.
2. The other scenario is where you migrate overdue loans using the check-out-by-barcode API. When the loan is created, scheduled notices are generated based on the due date, which is already in the past. The notices with the nexRunTime in the past are sent out along with other delayed notices.