2022-2-8 Bulk Edit Working Group Meeting Notes

• Magda: So let's start as simple bulk edit. I'm going to use a file of user barcodes.

• Magda: We select the file to upload which populates the list of the matching records.

• Magda: A preview list is displayed. The columns are status, last name, first name, barcode, patron group, and username.

• Magda: We can play with the hiding and showing columns as we discussed before

.

• Magda: Now we download the records that much our list of identifiers that we submitted.

• Magda: And here is the CSV file that is being created.

• Erin: Do you get all the columns are just the ones that show up in the preview.
• Magda: All of them.
• Magda: Let's update all these users to the faculty Patron Group.

• Magda: Please note that I'm not using the identifiers. I'm using the values of the group. And let's save the file.
• Magda: And let's start bulk edit.

• Magda: We choose the file.

• Magda: We click the "save and close" button. Once clicked, we get the notification that the data will be committed.

• Magda: We get the progress bar showing the upload progress.

• Magda: And we then get the confirmation notification (the typo will be fixed).

• Magda: This is the first obvious bug. The preview of the records matched is not displaying. This will need to be added. This was missed in implementation.

• Magda: Let's go back to the users app and if the updates happened.

• Magda: Barcodes 123, 456, & 789 were all successfully changed to Patron Group Faculty.

• Sarah: Does the file name have to stay the same? Often I changed the name of the file in this situation adding "edited" to the edited version.
• Magda: Yes at this point in development that file name has to match.
• Magda: If you go to the Export Manager App you can see all the files we uploaded.

• Magda: Is keeping the file name unchanged a problem?
• Erin: I think where the problem maybe is the fact that it looks like that filename has UUID in it. I do not consider that to be a readable name

• Erin: If it was something where maybe it was like a date string or something where I could easily identify what had happened. And then maybe there was a string at the end if you needed it.  I think that would be acceptable, but right now I wouldn't consider that acceptable.
• Magda: I agree.
• Lita: I didn't catch that it had to be the same file name because the screen just said browse to choose a file. So, I figured you could choose any CSV file.
• Magda: In the requirements, the file name was supposed to be in the format: date, the word matching records, and then the name of the file that was used to trigger  the bulk edit. So this was one of the bugs that we need to be addressed.
• Magda: I agree with you. It is very difficult to work with and it doesn't make sense. Especially if in a couple of weeks you would to go back to the file. How do you identify it?
• Erin: And the export manager UI does not give enough information to be able to understand what you were doing at that point.
• Erin: Lloyd's question in chat: "is there a way to see the records just changed without looking them up individually?" You can see on the screen where it says "preview" it is not showing anything and it should. So that's one of the bugs that Magna mentioned she was going to follow up on.
• Bob: Is there some requirement that there's a correlation between the the file you download and the file you then upload? Or can you upload any file?
  
• Magda:  I would like to show some errors and trigger some errors (Madga added some text data in a date field in her test file and began uploading it to bulk edit).
• Erin: I will say that I do not find that intuitive at all. The save and close is how you know it uploaded successfully.
• Magda: So what would you like instead?
• Erin: A progress bar?
• Sarah: or green toast?
• Magda: By the way here is the example from the invalid data I entered. And you should be able to also download the bad data. But there is currently a bug. I will show you the download error in another screenshot shortly.

• Magda: Let's go back to your input about it not being intuitive (here Magda takes us to the screen just after we upload the file to be matched against in bulk edit. She stops after selecting the file. This is where the group feels the UI is not very clear if the file has been uploaded yet or not?)
• Erin: I think that Sarah's suggestion of a green toast success if that could happen, would probably be the easiest because that is how other apps give you a success message. That would be my suggestion. I agree with Sarah on that.
• Magda: Does anyone else have an opinion?
• Sarah: Just to confirm here, at this image, has the file not been successfully uploaded at this point?
• Magda: At this point, nothing happened yet. You selected the file and the system knows you selected the file. You click "save and close"
• 
• Magda: And now it is telling you that this is the file. You select that we are going to change the number of records that are in the file. And it tells you that if you click "save and close" at this point, the changes are coming. If you pick cancel, nothing will happen.
• 
• Erin: On the prior popup there's a suggestion and the button says "upload" instead of "saving close."
• Magda: So I have noted the change from "save and close" to "upload" and green toast to show the file has successfully been uploaded.
• Erin: This might be a place to ask Kimie Kester. She may have some input here. I don't know if there are other apps that have this kind of workflow yet, but I don't think so.
• Magda: I will reach out to her.
• Magda: In data export and here we could have the window close after you select the file to upload and then go right to the next popup. The reason I did it in a couple of steps is I wanted to make it as conscious a choice for the user as possible.
• Magda:  if you find more typos, please reach out to me when you play with this. Because I see some of them, I don't see all of them, so anything you find will be helpful.
• Sarah: I think the issue with the previous screen is that it doesn't show you what you've just done anything. I think the previous screen is very non-intuitive. It is not even the button it is that it does not even say upload.
• Magda: The "save and close" is really more like continue. The upload is happening when you choose the file. Then it perhaps should say continue instead of "close and save." That would make more sense.
• Bob: It would be good to have a preview of the records to confirm that the correct file has been loaded before any changes are committed.
• Sarah: I don't think I need to see an entire preview, but I want to see the file name. On the file upload part of the process, it should confirm the file name after you select it. Also on the previous popup, it looks like you could choose multiple files. Can you do that?
• Magda: No it will not allow you to do that.

• Magda: From the conversation we had so far, I also noticed that it would be nice to have a back button because I keep canceling to start again. It would be so much easier to have a back button to start over again.

•  Magda: Just to make sure we are all understanding what is happening. All that we have done in the Lotus release is called a proof of concept or what I call the pilot project. So it means that this is an experimental approach. We know that the CSV approach was not liked by many, and that's why we are going into the In-app approach with Morning Glory. But we will continue to make enhancements to a CSV approach in addition to what we have done because I do believe there's value in this approach. It gives this a lot of freedom and functionality, but we also know users will need to know what the implication of their actions are. So let me close this and show you an example of a very simple query.

• Magda: With the query, parsing is not fully functional yet as expected. There is a JIRA for this.
• Magda: (Magda showed a demo of a simple query and an example with invalid data uploaded. The Error preview section of the screen in the UI is not working there is a bug. But you can download the errors to a spreadsheet.)
• Erin: Is any of this going to be worked on in Buckfast?
• Magda: Before the bugfes we will address some of the bugs. And then the plan is, for now, to include this in the bugfest unless you prefer not to have it in bugfest? Then we will still have our bulk edit environment where we can play around. So, this is actually your call.
• Erin: I can't think of any reason why we wouldn't want this tested in bugfest, but I don't know if anybody else has any thoughts on that. It can't hurt to have more people looking at it.
• Magda: I absolutely agree.
• Erin: It just means somebody has to write the tests.
• Magda: The tests are actually already written. On a high level, but we have tests that are already written and I'd be more than happy to get the feedback. And as I said, I hope between now and our next meeting you will be able to play a little bit.  Is there anything that you would like to bring up?
• Bob: I just want to say it's so exciting to see the progress.
• Magda: Thank you. It is exciting for me and for the team. I'm, I'm happy to hear you are excited to. Please bear in mind we are just starting the journey. So, be patient with the bugs, but find them so we can address them as well.