Page Comparison

Ingolf will be the note taker today.

Introductions: new member Craig Boman.

Which issues need development and decision by the PC ?

Discuss List of Integrations .

These kind of issues are not yet represented in the Backlog. The Backlog so far focuses on UI application features. The List will be presented to the PC (Ingolf, Chris; today).

Texas has mostly custom-developed integrations.

Early result on load timings for the user module and their implications for other form of bulk loading.

• discuss needs for optimization and acceptance criteria

Tod reports that UChicago has done some testing in a cloud environment. Bulk user load took 2h 28m for 90,000 users. For a one-time load this is so-so, but extrapolated to bib loading (millions of records) this will be too slow. The bulk import calls the user model one at a time for each user. ..This could easily be optimized.

 Data migration is a big load of work to the SIG.

• what aspects of data migration will the SIG be responsible for ?
• what should be delivered by the SIG ?
•  how will the SIG involve other Subject Matter Experts (SMEs) from other SIGs to work on data migration ? (in what form and when will that happen ?)

It seems to me (Ingolf) that just one hour per week is not enough to discuss this (data migration) and work on this further. Can we choose one of the following solutions:

1. build a subgroup. A limited number of experts meet in addition to the regular SIG meetings, on a regular basis, and is concerned with questions of data migration.
2. The entire SIG meets more often, say, twice a week.
3. The SIG meetings take place weekly and cover data migration issues, but the SIG meetings will be longer (90 minutes).