at 11 EST
- Dale Arntson
- Jenn Colt
- Chris Creswell
- Jackie Gottlieb
- Matthew Harrington
- Anne L. Highsmith
- Uschi Klute
- Ingolf Kuss
- Jon Miller
- Tod Olson
- Catherine Smith
- Michelle Suranofsky
- Ian Walls
- Patty Wanninger
Link to meeting: https://zoom.us/j/204980147
|5||Welcome and assign note taker.||Dale|
Welcome and request for someone to take notes, preferably, someone who hasn't done it in awhile
|35 minutes||Bulk API review||various|
We'll take a look at where we are at with bulk APIs, and what we need to do to move them along.
Some jiras of relevance:
And for some background and discussion from other sites (cited by Anatolii Starkov):
One complication with implementing bulk load APIs for all modules is that APIs call other APIs
|10 minutes||Downtime during migration||various||Tod asked in the implementers Slack channel and will bring it up in the next implementers meeting.|
Previous requirements discussions have assumed there can be no downtime. It'd be a lot easier if that weren't the case.
Jon Miller pointed out that the downtime requirements were more about performance of the data load so that no institution would have to spend more than a day down for migration.
Implementers are basically all planning to do their migration during the summer because it's less busy.
|5 minutes||Metadata fields in records||various|
Metadata needs to be possible to populate as you load in data. Currently it's usually overwritten.
This could be accomplished with a flag to the API, or just based on whether the metadata attribute is present in what's loaded through the API.
|5 minutes||Work prioritization||various||More discussion of prioritizing work -- we need to be careful what and how much we ask for or it won't get done. Some discussion of who makes the decision regarding development priorities when everything is critical.|
Tod will ask in the implementers meeting if zero downtime is a real requirement for implementers, or if a reasonable amount (less than a day) will be acceptable.