2019-08-05- Data Migration Subgroup Agenda and Notes

Welcome and request for someone to take notes, preferably, someone who hasn't done it in awhile. Michelle will take notes.

Report from Tod on whether any early implementers need to do a gap load in their migration to Folio:

Early Implementer meeting notes with discussion details – see "Survey about migration scenarios - "Big Bang" vs. "Trickle" Migration plans"

General discussion about: 2 phase migration...e.g. bib records first...and frozen, are API deletes really needed (for migration)? ...is gap loading needed?  The 'MVP' may require a larger downtime during migration in the spirit of a true MVP.  Acceptable since it is an MVP?

Mention of a requirement for sync. between a union catalog and FOLIO and union catalog will be integrated as a knowledge base (Ingolf)  – similar to what Chalmers is doing.  There may be some potential for re-use of the Chalmers functionality.  Chalmers use case is exchanging 'inventory' records.

Continued discussion on bulk API requirements.

Some jiras of relevance:

• How to design batch API (General recommendations),
• UXPROD-1826 - APIs for batch uploads and downloads Draft 
• FOLIO-2050 - SPIKE Design batch create / update API endpoint standard Draft 
• UXPROD-1826 - APIs for batch uploads and downloads Draft 
• MODINVSTOR-295 - streaming POST holdings Open 
• MODINVSTOR-296 - streaming POST items Open

And for some background and discussion from other sites (cited by Anatolii Starkov):

https://evertpot.com/http/207-multi-status
https://apihandyman.io/api-design-tips-and-tricks-getting-creating-updating-or-deleting-multiple-resources-in-one-api-call/
https://medium.com/paypal-engineering/batch-an-api-to-bundle-multiple-paypal-rest-operations-6af6006e002
https://developers.google.com/gmail/api/guides/batch