2022-1-11 Bulk Edit Working Group Meeting Notes

DEVELOPMENT STATUS

• Magda: Unfortunately the main piece that will populate the results in the Bulk Edit app is still in progress. So when we look at the development scrum board, the front end pieces that we need are:
  • UIBULKED-12 - Populating preview of matched records based on identifiers search

  • UIBULKED-16 - Populating preview of matched records based on query search

  • UIBULKED-13 - Populating error accordion
  • UIBULKED-22 - Completion of the bulk edit

• So this the work that is in process and it's been was blocked for a while by the backend work. That backend work is done. Now we are waiting for the front end to be finished. So that's why there was not much you can see in the app. But to make you feel a little bit more comfortable about the progress I would like to take a look at the features that cover the work for the user data pilot project, UXPROD-3225.Edit.

• The work  is being covered in three separate features:

  • Preliminary work - this was the UI work that puts the elements on the page. This is already completed.

  • Identifying, user records for bulk edit - the stories are either in progress or in code review, meaning they should be available soon.

  • User records - bulk edit - pilot implementation - most stories are closed with a handful in review. Those that are in review are waiting for the other elements to be completed in order to be verified. Do you have any questions about that?

• Erin: Magda, we can't see anything yet.
  • Magda: You can through the API. Most of the work is done. And when you click on the record you can see examples of how the requests are built. So if you want to venture into the API you can do this. Most of this work is done. As of today, you cannot see this functionality in either of the environment. I can only say the solution is pretty close to being completed, but UI is not there yet.
• Erin: But we just don't have an idea of when?
  • Magda: We have the idea and the optimistic approach that it should be done by the end of this week. The realistic approach is by the end of the next week when the sprint ends.
  • Erin: Okay. Okay. That makes sense. Thank you.

ACCEPTANCE TESTING ENVIRONMENT

• Magda: So this brings us to be to the next bullet, which is acceptance testing. I don't know if anyone had the chance to take a look at this. The environment has been a setup. And it's based on the Kiwi boxes environment with the user data. We control this environment. So it means it's not refreshed nightly. The data that is there is there. Once we complete the UI development of Bulk Edit, we will deploy it to this environment. And I will let you know when this happens which will probably will be sometime next week. The users are the same that are in the Kiwi bugfest. So if you participated in Kiwi Buckfast, you should have your logging there. This is the case for me.
  • https://bulk-edit-perf.ci.folio.org/
• Magda: If you have any problems with logging in let me know and I will help. I don't want to share the admin password to protect the data, etc. If you think this is being paranoid let me know and I can share the admin password. But otherwise, I think we should all have access to this environment.
  • Erin: That makes sense to have us working as actual users and not using the admin account Magna.
  • Lita: I'm curious, the Kiwi accounts that come over, will they have the same permissions? I had a superuser account on Kiwi with all permissions. Would it be the same permission set on this one? And will Bulk Edit permissions be rolled into that?
    
    • Magda: No you would need to add Bulk Edit permissions to this account They are not assigned by default.

SCENARIOS FOR USER ACCEPTANCE TESTING

• I would like to ask for your help with providing scenarios that you think should be a part of the user acceptance testing.

• This is the link to the survey to provide your suggested scenarios.

  • Please submit your suggestions before the end of the week (January 14th)
  • https://forms.gle/K1JyUGaAWEKqBAd66

• Bob: Is there a suggested format.

  • Magda: I  was thinking you can be descriptive here. Based on the feedback I will create test cases in Test Rail. And they will go through the mechanics of entering test cases there.  But also I think for our acceptance testing, we can agree on a spreadsheet that will be available to all of us and where we can record our findings. Would that work for others? I assume the quiet means agreement.
    • Erin: I think that makes sense. I think we just want to make sure that we are looking at the user acceptance testing scenarios that go back to what we described as the requirements as well.
    • Magda: Yes, exactly. I don't want to impose my scenarios. But, if I don't get your responses. I will put whatever I think is appropriate. But definitely, I would like rather hear from you.
• Erin: Magda, are we doing user acceptance testing separate from bugfest?
  • Magda: Yes we are, and I would like to start by the end of the sprint, January, 21st at the latest, hopefully, we can start next week.
  • Magda: I would like us to start playing with the app we build so we have more time to address issues hopefully before bugfest.

Permissions implemented in scope of UIBULKED-11 (known permission issues: UIU-2486 - Getting issue details... STATUS and UIU-2075 - Getting issue details... STATUS )