Skip to end of banner
Go to start of banner

2022-3-8 Bulk Edit Working Group Meeting Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »


Attendees (please add your name):

Magda Zacharska leeda.adkins@duke.edu (OLD ACCOUNT) Erin Nettifee Christine Tobias Amanda Ros Erin Weller gongd@msu.edu Jackie Magagnosc Monica Arnold Scott Perry Kimie Kester Sara Colglazier Robert Scheier

Note taker:

Robert Scheier

Meeting Recording:

Discussion:

TopicNotes 

Housekeeping

  • Please add your name to the attendees list
  • Please state your name when you join the conversation to help with meeting notes

Magda: Just some quick housekeeping. Please add your name to the list of attendees and to help Bob with notetaking, please state your name when you participate in the conversation.

Development updates

  • Magda: Frist status updates. The bulk edit developers are living in some of the cities that are in the news of the war. Nobody expected this. Obviously, there were a lot of challenges.
  • Magda: The other challenge is that some of the engineers not on my team, the Firebird team, could not work to the full extent. So we need to rely on other teams like devops to set up all the environments. This time it is falling on the Firebird on my team's responsibility. They don't know this. They need to learn. They are learning the new functionality as they go. So things are just happening much slower.
  • Magda: When we partnered last time, which was almost a month ago, I told you we will be doing a workshop today. We are not going to do the workshop today because the environment is not update updated. The engineers tried to do this in bulk edit, they were not able to do it for today.
  • Erin: You are talking about the rancher environment?
  • Magda: Yes, the bulk edit rancher environment. It is the older version, so you can see some things improved, but you cannot compete with the whole process. The majority of bugs that were on the list are addressed including the titles and the renaming of the files. I can show you quickly in the snapshot environment. I would say it works as expected.
  • Magda: The development scrum board, I think it is updated to the new sprint. We are starting to work on Morning Glory. In the works, you will see bulk edit permissions. Those are the bugs that we will be working on in morning glory as well.
  • Magda: The Pilot project status. We are not going to include a bulk edit in bugfest. The reason for this is we did not have enough time to test it. And as Jen mentioned in the early stages of our meeting, we all agreed, we don't want an application that is not fully tested.
  • Erin: So, that means there is no there's no bulk edit app and Lotus?
  • Magda: Yes, that's correct. We will update bulk edit in rancher with the latest code, and this is the environment we will use to complete our user acceptance testing. Then when we have this feedback we will include this in the Morning Glory release.
  • Magda: For Morning Glory there are three features that we will be working on.
    • One that I listed here is Bulk Edit - in-app approach - item locations, temporary and permanent
    • Bulk Edit - in-app approach - item statuses, in inventory
    • Bulk Edit performance testing including bugs uncovered.
  • Magda: I would like to do a quick walk-through of the functionality that we have done that is visible in snapshot. I would like to show you that the issues that you brought up during our last meeting have been addressed. So, I'll do a quick demo.
  • Magda: The first one that was brought up the naming convention of the files. It was using the UUID and now it is the file is human readable, i.e., "matched recrods."
  • Magda: (after Magda edited the Patron Group field in the matched records Excel sheet she was able to edit the file name to distinguish it from the original downloaded match file). This was also something that was not available the last time I demoed this.

Magda: (after Magda uploaded the edited match file, the response message now says the file has been uploaded to be more clear what is happening at this stage). This was also a change that was proposed to makes it a little bit more visible that we are just uploading the file here.

  • Magda: And this is the warning that we are about to change the records if the Commit Changes button is clicked. Also the type has been fixed.

  • Magda: And then confirmation that the records have been updated. The typo has been fixed as well. And we can see a preview of the changes. 

  • Magda: So this is a quick review of what we delivered. It's obviously more than this, there is error handling.
  • Magda: I would like us to go to other elements on the agenda for today, because I need your feedback on a couple of things before we started doing Morning Glory.
  • first, the developer as to just to change the order of the, of the elements on the landing page. And I would like to hear, uh, what you think about this. Let me make it a little bit bigger so you can see.

Proposed modification to the landing page

Action menu - support for in app and CSV approach 

Pilot Project UAT  


Future discussion topic (time permitting):

  • Bulk Edit of the linked records
  • Scheduling edits




Chat and Notes:

Kimie Kester (noted post meeting via Slack): I checked with a developer, John Coburn , Stripes-Component-Lead for FOLIO, and he said the button at the top of the left-hand pane, in our case, Identifier and Query, is called a ButtonGroup.I said a Segmented Button because I have heard other Devs and UI people call it that but officially they call it a ButtonGroup: https://ux.folio.org/storybook/?path=/story/buttongroup--basic-usage

  • No labels