Architectural changes moved to Kiwi feature

After internal conversation, decided to deprioritize some of these architectural changes for Juniper, in favor of bugfixes and automated tests

Based on number of stories and total points, we likely will need to split this feature, and continue the work in R3

Hi We'll be putting together details on the wiki in the next week or two. We started with Creates for SRS Bibs, and all 3 Inventory record types. Now we are also working with multiple updates to the same records. We have 5 job profiles that should result in successes for all updates, 1 job profile that will fail for holdings and item updates, and 1 job profile that will fail on item updates. We are not yet making them as varied as you'll encounter in a real use case. Another large part of the testing is related to processing time, so we want predictable results before we start introducing more unpredictability. That whole walk before you run thing.

With a few adjustments to environment setup details, a load of 50K creating or updated 50K SRS, Instances, Holdings, and Items completes in ca. 2.5 hours. We think there are still some steps that we can take to improve that performance, but the devs are still analyzing the various runs, adjusting settings, and trying again. More soon, I promise!

I am curious to know what kind of testing has happened on the data that was loaded in the 50k import.  Has anyone tested updating or overlaying those bib and/or order data?  In other words, was the load successful in that those data are now actionable and effective? 

I am also interested to know how long it took to load the 50k bib records.

Thanks!