Cross App Data Sync working group

Background and questions

| www.folio.org

1

Background

• Data sync issues raised in App Interaction SIG
• “Maintain relationship between apps when holdings/items are moved” 
• Collection of use cases across apps
• Analysis of expected behavior
• Involved TC - goal: find solution / pattern that would work for majority of use cases
• Working group was formed

​

​

| www.folio.org

2

Working group

• Members:
• Brooks Travis
• Charlotte Whitt
• Marc Johnson
• Martina Schildt
• Owen Stephens
• Raman Auramau
• Zak Burke

• Meetings every week on Mondays at 9 am ET
• Confluence space
• Google Drive
• Documents
• Use cases
• Proposal by Raman

| www.folio.org

3

Steps I

• Specified Source of Truth for each use case
• Grouped use cases into categories
• a. Copies of data to be updated
• b. Notify use of data in other apps
• c. Notify on deletion
• d. Block on deletion
• e. Notify on data update (maybe same as or similar to a.)

​

| www.folio.org

4

Steps II

• Discussing Proposal by Raman as possible solution
• Event publisher posts changes to a Notification channel
• Event consumer is responsible for
• reading updates from the Notification Channel
• subsequent processing of this event in accordance with its own needs
• Known: won’t solve use cases of category “d. Block on deletion“
• Currently discussing – needs input from SIGs/POs:
• Performance – acceptable delay for all data changes to be synced
• Reliability – time span in which the information about all data changes needs to be available to other applications that are depending on that data

​

| www.folio.org

5

Questions

• What is a tolerable delay for data to be in sync that is still workable?

​

• Which use cases require instantaneous access to the updated data?

​

• If data needs to be updated instantaneously, but is not, what are the impacts on your workflows?

​

| www.folio.org

6

Discussion and feedback

| www.folio.org

7