Housekeeping Please add your name to the list of attendees Please turn on Transcript option for the meeting Bulk edit WOLFcon meeting is scheduled on August 31 at 4PM CEST (10 AM ET). It is planned as a hybrid meeting (zoom and in person)
| 00:01:24.450 --> 00:01:25.32 Magda Zacharska: Hello, everyone. I have a question. I don't see myself as a host, so whoever is the host of the meeting, could you please enable the transcription? This will help Bob with taking the notes. 00:03:44.550 --> 00:03:47.100 Magda Zacharska: We don't have everyone, but we have enough so we can start. The transcript is on, so hopefully, this will help Bob Scheier with his meeting notes. Magda Zacharska: I am recovering from COVID, and I'm still coughing, so at some point, I will need to mute myself. 00:04:40.620 --> 00:04:44.850 Magda Zacharska: I share my screen, please let me know if you can see the meeting notes. Magda Zacharska: Thank you, we have 17 people in the meeting I don't see 17 names in the attendees least please add your name to the list, so we know who has attended. 00:06:27.450 --> 00:06:48.540 Magda Zacharska: The transcript this on and the last housekeeping item is the welcome meeting for Bulk Edit is scheduled for August 31 at 4 pm Eastern Central European Time, which translates to 10 am US Eastern Time. That will be Wednesday, not Tuesday, and if you can attend the meeting, that would be great, this is a separate meeting, so if you cannot be in Hamburg, you can join by Zoom. So the question for the group is anyone from the group planning to attend in person? 00:07:16.530 --> 00:07:17.820 Erin Nettifee: I'll be there virtually. Aaron Weller and Christine Tobias (in chat) are saying that they will both be there in person. Magda Zacharska: for everyone else who will not be in person and who will like to contribute to the meeting in some way, is there anything you would like me to discuss or bring up during the meeting is marked as a work working meeting, so I hope to get additional feedback and requirements. Is there anything you would like me to present or bring to the group's attention? 00:08:21.960 --> 00:08:24.750 Erin Nettifee: Are you asking that now, or are you asking people to think about it? Magda Zacharska: You can say it now, or you can reach out to me on slack later. Erin Nettifee: I think it might be helpful as you're thinking about that group to somehow surface in this wiki space. A schedule of what's planned because you have talked about that in slide decks. Sort of what will come in this release, and this is what will come in this release. I think actually having that in a wiki page would be really helpful for people, so that would be like a central place to go. 00:09:47.940 --> 00:09:55.110 Magda Zacharska: I was looking at this yesterday actually while working on the presentation for the welcome. A high-level roadmap
Erin Nettifee: So is that what you're going to maintain this spreadsheet? Magda Zacharska: I will create a website or a conference page. Erin Nettifee: I mean, if this is the this is the Info, I'll just put it on the page for you, and then you can edit it. Magda Zacharska: Okay sounds good. Magda Zacharska: So, if you have any other comments about what makes sense to bring up during the welcome, please let me know either now or later. I will be following up on the Slack Channel.
|
Development updates Bulk Edit Morning Glory Known issues (as of August 9, 2022): | 00:11:09.870 --> 00:11:19.920 Magda Zacharska: The biggest part of the development updates is obviously morning glory. We discovered several issues. Here is a list of those issues. They are highly technical, and not all of them, but most of them. We discovered if someone runs Bulk Edit in the Bugfest and exports EDIFACT, eHondings, Circulation logs, or bursar. 00:12:10.950 --> 00:12:13.500 Erin Nettifee: So something is happening on the export manager side? Magda Zacharska: Yes, those jobs were being filed and then not being processed. We discovered there are problems with the concurrency of those records. That's why we spent a significant amount separating those jobs and queuing them and also testing the behavior. What are the limits of the records we can safely process at the same time? So If we, for example, lower the number of records that are being processed, will this eliminate the problem, and what are the safe limits? 00:13:16.650 --> 00:13:25.710 Magda Zacharska: Right now, the safe limits are 2500 user records at the same time and 10,000 records for items. And as I said, some work is still in progress and will need to be released and tested in Bugfest. We have two other environments that we are using for testing. One of them is the performance task force Prokachka (spelling??) test and our Bulk Edit performance testing. So there is a lot of testing happening on this. Do you have any questions? 00:14:02.760 --> 00:14:03.600 Erin Nettifee: So, the Morning Glory release is at the end of the month. Is the goal still to get everything that we had planned into Morning Glory, or are you thinking that we might need to back it out or ... Magda Zacharska: The plan is to get this into the Morning Glory. The determination will probably be made by the end of this week if we limit the number of records that can be updated simultaneously. Erin Nettifee: Would it be a limit that the app would enforce? Would it be expected that the users would know not to go over this number? 00:14:46.560 --> 00:14:46.920 Magda Zacharska: Most likely, we will ask the user to know, and this will be included in the release notes. And once I have the data, I will definitely make everyone aware. Erin Nettifee: Is there anything you think we could have done to catch this before Bugfest? The answer might be no, but I'm just wondering if we might have changed our approach. Magda Zacharska: I think the challenge here is the coordination between three development teams. Efforts need to go into the teams that work on eHoldings, and Export and the teams that work on EDIFACT export. Obviously, you know when you look back, you know what the right thing is. We started experimenting with large data pretty early, and as you see, I linked to the performance tests (see links in the left column). If we do only user records, we can easily do 10,000 records, however, if we increase the number, it affects other areas. So we need to be cognizant. Magda Zacharska: Regarding the known issues. The first one is "implement logic for record counts when items bulk edit is triggered by holdings id." This is the label when we count the records, how many records were submitted, how many records were (Magda could not open Bugfest) ... 00:17:51.630 --> 00:18:02.790 Magda Zacharska: When we upload the records--in my example, I submitted a list of 10 records, and it states that 10 records match. And here are the 10 records.
Magda Zacharska: If we submit a Bulk Edit by submitting Holdings UUIDs. I can send a list of two holdings ids and have 10 records matching the search criteria. How we report this on screen is why we have this story, UIBULKED-122. I will bring it up at one of our meetings at some point, and we will discuss what is the best approach. 00:18:50.160 --> 00:19:04.470 Magda Zacharska: The second known issue, MODEXPW-203, is the "'fail to upload file' error with a large amount of Users barcodes," this is happening when we attempt to update approximately 100,000 user record identifiers. Magda Zacharska: Since we know we will limit the number in Morning Glory, that is going to move to Nolana, and we will be addressing it in Nolana. The last know issue in the list, MODEXPW-202, is "Incorrect number of records changed on the confirmation banner." I am not comfortable marking it as a known issue, but we don't have the resources to address it.
00:19:49.290 --> 00:19:49.830 Magda Zacharska: Once the update is completed. The preview of records changed displays. But we see in the error counts are zero, and also, the records successfully change is zero. This is happening because UI is not waiting for the back-end to respond. If the user clicks the refresh, the correct number is displayed. This is most likely a known issue for Morning Glory. Any comments or questions? Magda Zacharska: Due to the slowness of my machine, I'm not going to open the links to the performance reports. If you are interested, please feel free to follow the links. The most important one is the "combined tests: Combined test for data export worker (Morning Glory), which covers exports of other record types. This is what is the closest to the real-life scenario that those will be executed concurrently, so those are still in progress, but the report started to be created. Any other comments or questions before we move on to reviewing the user acceptance testing feedback? 00:22:26.970 --> 00:22:30.030 Erin Nettifee: I don't have any I don't know if anybody else does feel free to chime in.
|
