Page Comparison

Bulk edit documentation for Morning Glory 

Thank you (OLD ACCOUNT) Erin Nettifee and  @Bob Scheier, @Emma Gollner, @Christine Tobias and @Amanda Ros!

Morning Glory release notes

Bulk edit: 

• required configuration
• known limitations
• known issues

Magda 16:18  
So let's go to our agenda again. And let's move to the next part, which is the Morning Glory release notes. As you know, morning, Morning Glory was released on September 16th, and I would like to walk you through some points on the release notes. So first, the new app. There is only one a new app which is Bulk Edit in Morning Glory. And a quick overview of what we support. In the in-app approach, inventory items temporary and permanent locations and item statuses. In the CSV approach, user records. There are two sets of permissions that are required for this application, in-app edit and view , and CSV edit and view. Depending on those permissions, a user can access those applications. There are known there are Known limitations. As our performance tests discovered, in Morning Glory, you can only do a Bulk Edit of 2500 user records at the time. And for items, the limit is 10,000. This is a lot less than we were hoping for. Unfortunately, this is what it is for Morning Glory. We are looking at architectural changes to support a larger data set in the future.

Magda 18:54  
The last part here, module configuration, is for those who are hosting themselves. For everybody else, this is being set by the hoster. Those are the memory requirements for the container that runs the module data export worker, which is being used in Bulk Edit

Erin  19:01  
The performance test, the performance work that you were talking about, is tracked in a particular Jira?

Magda  19:09  
JIRA and reports. I will link the list. There is a new performance testing Jira that we started in the Morning Glory. Some of the work will spill over into Nolana. Starting next week, we will be working on bug fixes for the functionality that was already delivered and testing, performance testing, adding API tests, and adding automated tests for the UI. So, most of the tests can be run automatically.

Regarding the known issues, there are two Jiras that are linked to Bulk Edit. One which we discussed a couple of meetings ago, has to do with Bulk Edit results triggered by holdings identifiers. When the mapping between holdings and items is not one-to-one, it may happen that the list of identifiers is shorter than the list of matched items. This will need to be addressed in Nolana. We will be working on this functionality.

Then the next issue is a little bit more serious. When you update datasets larger or larger than 10,000 records, there is a significant delay of up to several minutes before the display of the preview screen, i.e., the "are you sure" form. We are working on improvements.

Erin  22:59  
Did you ever see it timeout, or would it just it would always come?

Magda  23:05  
We saw this, but it rarely happened rarely. So I cannot tell it never happened. Yes, we saw that happened. But if this is the case, you just need to must submit the Bulk Edit again. The data is not committed at this point. Any additional questions?

Erin  23:55
Jennifer has a question in the chat. "Does it affect any other operations happening at that time?"

Magda 24:34  
So the problems we saw with slowness are is caused by the mod data export worker that is being used. So separate from the inventory module or a data import module, there should be no interference. However, if somebody exports EDIFACT or circulation logs are being exported, or the bursar is being exported at the same time, it will have an effect.  However, in our tests, when we ran all of those three exports at the same time, EDIFACT, bursar, and circulation with a Bulk Edit of more than 10,000 records, that is when we say it affects other exports happening at the same time. Any other questions?

Magda 34:27
But I would like to start a conversation about the query tool that is needed. We actually started actually the last meeting. I have some high-level Balsamiq mockups that I would like to walk through and get your feedback on. Please feel free to interrupt me. So this is the balsamic implementation of rendering of our bulk editBulk Edit. This is something that we talked about--switching the order of the identifiers, put putting them on top, and then having the query or the identifiers below. So this is what is represented here. The two links at the bottom, save the query as, and open the existing list, ; these are out of the scope of our conversation , for now. This is something we will come back to later.

For the purpose of this conversation, we are on the Query tab in bulk edit. There is a new button called Build query. When the user clicks the button, it opens a new pop-up that looks like this. It's a long data entry textbox with a test button disabled.

Erin  37:06  
So what you are proposing is a redesign from what's currently implemented?

Magda  37:11  
Not really redesigning, adding. We will get to this. Basically, I'm adding the a new button that will allow us to build a query.

Magda  37:39  
And then, in the Poppy release, we will add additional record types. In Orchid, we will support just one record type. So in order to know what you have, there will be additional labels showing that you have access to users inventory items, circulation loads, and then circulation requests, etc., to build your query. You can still only edit one record type using Bulk Edit. But in Poppy, you will be able to access additional record types to build your query. Any questions or comments?

Orchid release

Poppy release

Magda  9:14  
The user clicks on the search textbox, and the list of available properties is displayed.

Magda  39:42  
The user selects the patron group, one of the available properties. Then the list of available operators is displayed. The list of operators will depend on the the selected field. We will start with equal, in, not equal, and not in.  The properties list is preserved so the user can go back and change it.

Erin 40:34  
Should we use words instead of symbols for consistency in that drop-down?

Thomas  41:05  
I think these are standard search operators, but still, I think I would just do equals, not equals, in, and not in.

Magda  41:17  
Okay, thank you. We selected the operator, and now we get the list the pre-populated list of available options.

Magda 41:19
So that would obviously be in place only for the controlled vocabulary. So if, in some case cases, the user selects a title, then obviously, we will not pre-populate the drop-down with all 10 million titles that the collection may have. Instead, we would present a text entry box. But for this example, we would pre-populate the combo with the existing values. For options that will have with hundreds of options like locations, for example, the drop-down like what already exists in inventory where what you type narrows down the list. Any question?

Magda  42:58
The next option is the Boolean operator whbch , which will automatically be displayed. And user can choose to continue to add to the query or just not select anything. Please note that once the first option is entered, the test button is enabled. It was disabled until now.

And here's the example when the user continued to build the query by adding a boolean operator.

Here's the example where the user wrote the query , and click the test button. The There is a gray areais the progress bar that shows that the records are being counted. And in this example, we have more than 100,000 records returned and with the notification, please narrow down your search. The question here is what should the number should be , and how we should handle that number. I do believe we talked about this at some point, and it was proposed that this would be configurable. However, we need to keep in mind that having a big number of records will definitely impact the performance of Bulk Edit.

Unknown Speaker  Erin  45:06  
Is this a number across the board for queries? Or is it like record by record type or?

Unknown Speaker  Magda  45:11  
that That would be across the queries? Okay. So this is something we definitely will talk about later. But I would like to you to keep it in mind. I see something in the chat. Let me take consistencies good.

Unknown Speaker  45:32  
Green. That's from the conversation about the

Unknown Speaker  45:36  
Okay. Okay, thank you. So no comments so far on this? Does anyone has like a quick feedback on the word? Oh, if this should be a limit of the bulk edit up.

Unknown Speaker  45:57  
I mean, I Does anyone have quick feedback on if there should be a limit for the Bulk Edit?

Erin  45:57  
I mean, I would think that it probably should , if we're talking about if we're talking about our current example, where we have a 25,010 1000, 000 limit. I would want 10,000 As this numberas the limit here.

Unknown Speaker  Magda  46:12  
It's correction every net Correction. Not 25,000 . But 2500 I'm sorry. So yes, this rather, it is 2,500. This is just a proposal, as . As I said, we'll definitely come back to this lighterlater. So here what is happening right now, we run the query. And the query returns 1000 Records right now. And we see the preview. This is the hated preview that  

So we hit the test button for the query, and the preview of the resulting 1000 records displays. This preview does not show all the records, but just some of them. And here you You have the option of selecting columns . So this is easy to select. To see what you want to see by checking and check and check unchecking the columns that you have. Once the preview is populated, there is a new button run the , Run query.

Image Added

So the run the query will actually when the user click Run the query, what we'll do it will go button will close the pop-up and bring the user back to the landing page, it closes the the pop up the login. And what is happening here the is:

• The query that was created in the

• pop-up is displayed here

• on the left side as read-only.
• The list of the

• identified matching records is

• listed.
• We can paginate

• through the results similarly to

• how this is done in inventory

• by 100 records.
• There is also the option of

• checkboxes where the users can narrow down their

• results by selecting checkboxes. So in our example, we have 1000 records that

• were found to match the query. But out of those

• 1000, Only 100 were selected. And again

• , there is the option of changing the columns. In this example, the user selected 100 records, and

• with these 100 records, there will be

• the standard behavior of

• Bulk Edit, meaning you can save those 100 records into the CSV file. And then, when you start

• Bulk Edit, the edits will only affect those 100 selected records.

Image Added

Mark  49:24  
comments make that does the checkboxes. When you get your search results, they automatically come pre populated like all checked and then you you selectUnknown Speaker  are the checkboxes automatically prepopulated?

Magda  49:40  
I would say I will say yes that it they will be populated. But this can be discussed in the details . We will not get to check boxes in Arcade Orchid, that's for sure. But I would say yes, let's populate and then buy sell Selecting that prepopulate and by selecting the top checkbox, it will unselect the whole 100 that is are displayed.Unknown Speaker 

Magda  50:09  
Okay. Yeah, I think that's a good idea too. And the other comments?Unknown Speaker  50:25  
So 25  
So the question I have for this group is, if we get because this a rendering of the of the records, we can implement this also for the identifiers. Once you submit the list identifiers, instead of those top 10, you would get this behavior as well have the list that you can paginate. But the question I have for this group is, what makes what is reasonable to

Unknown Speaker  51:03  
paginate?

Unknown Speaker  51:04  
Through if you have 10,000 records that match your search criteria? Will you be paginating? By through those 10,000? By hundreds? No,

Unknown Speaker  51:18  
I would I I'm only paginating. To verify that. I'm, I didn't do something dominant what is a easonable number to paginate? If you have 10,000 records that match your search criteria, will you be paginating through those 10,000? By hundreds?

Erin 51:18  
I'm only paginating to verify that I didn't do something dumb. I might page through the first part of it. But I'm not going to page through the entire set. Anybody who would records?Unknown Speaker 

Leeda  51:35  
I would think our filtering and things like that would be done in outside the system in a spreadsheet.

Unknown Speaker  Erin  51:42  
Right? You mean you might want to you might want to download the entire set? Yeah, which you'll be able to do, but you're not going to paginate through that in that UI.?

Unknown Speaker  Leeda 51:52  
Yeah, totally agree with that.

Unknown Speaker  Magda  51:56  
So how many records? Should we actually what what will be the cutoff number of ? How many records that will be rendered to mean?

Unknown Speaker  Erin  52:10  
I? I guess I'm just thinking like, to To me, that screen looks normal at paginating through 100. Right? And then it pulled 100 records or pulled 1000 records. And I would, probably expect that if I clicked 10 times I would paginate through all the records. But I wouldn't probably do that very often. I'm sorry that I know , that's kind of like a wishy-washy answer. No,Unknown Speaker 

Unknown Speaker  Erin 53:28  
Sure, that makes sense.

Unknown Speaker  Bob  53:31  
The thing is, I might I might want to see the end of the results in the file results. Because just to make sure if I'm looking for any anomalies.

Unknown Speaker  Erin  53:43  
Yeah, that also makes sense. You know, if I'm expecting to get results all the way through to ZTE orUnknown Speaker  Z.

Bob  53:49  
office, I don't know how these are. I don't know how they're coming back, you know, I'm just seeing the results are coming back. I just see the top of the file. So maybe there 's are no problems with the top of the file. But you know, halfway down the file, there's a bunch of errors for some reason, where I'm getting things back that I shouldn't or that I didn't expect.

Unknown Speaker  Magda  54:05  
Yes. So the other option would be to sort it the the other way around. However, this is an expensive operation, the sorting of 10,000 records that we need to be mindful of. So it may make more sense maybe to add another link that will take you to the last one.

Unknown Speaker  Bob 54:29  
Can we can we export this to look at it in a spreadsheet?

Unknown Speaker  Magda 54:32  
Yes. So this is the Yeah, the The existing behavior of the of the spreadsheet that we have is preserved. So you can still can send save the list of matching records. Save the list of matching record, as you do right now in bulk editBulk Edit.

Unknown Speaker  Bob  54:51  
I would probably do that. You know, because I would want to see a whole bunch just look for any problems. So read

Unknown Speaker  55:00  
So do you see the value in adding this , of adding that preview? Or not? Really? Because you would still go to the

Unknown Speaker  55:09  
I think people were were expressing an interest in Yes, still seeing more than 10. You know, so I think this is valuable, but it doesn't have to go to the, you know, 200,000 200,000 Records. In my opinion,.Unknown Speaker 

Amanda 55:25  
unless you take away our exploitability, which it doesn't sound like you're going to do it,

Unknown Speaker  55:32  
can you Amanda, can you repeat,

Unknown Speaker  55:35  
I'm saying, you know, as As long as we will continue to be able to export the data into an Excel spreadsheet. , I don't see it as as a problem . You know, because we're , we're all used to manipulating the data in Excel. So it would probably be probably easier for us to find those anomalies. And Bob is disagreeing with me?

Unknown Speaker  56:11  
No, I was looking at my screen, because there things were going bad No, no, not at all.

Unknown Speaker  56:21  
So I mean, given the fact that we can export it, I'm, you know, like I said, I'm not, in the beginning, I'm probably going to flip through a few pages just to make sure that it looks like I expect it to but I'm still going to download the data. So you know, I am not going to, this I'm probably going to flip through a few pages just to make sure that it looks like I expect it to, but I will still download the data. So you know, I am not going to. This is not the hill that I'm going to die on about how many records , we need to be able to flip through scroll page through.

Unknown Speaker  Bob 56:54  
Yeah, I mean, it seems to me that both are valuable tools for looking at the data and what should dictate how much data should be displayed as is the system performance.

Unknown Speaker  Magda 57:10  
So this is this is a very good point, Bob, because we have to keep two things in mind. The , the performance displaying those dis records , it will definitely have an impact on on the performance. But if this is something that needs to needs to happen, we will need to take it into account. But also to develop this functionality. It's not a simple thing, this is a lot of a UI development. So

Unknown Speaker  27:50  
the

Unknown Speaker  27:52  
if you feel that you need this, then we will obviously us allocate resources to build it. If you think this is a nice to have that but you can that you can live without it, then we will allocate the resources differently.

Unknown Speaker  28Erin  28:13  
I think if If we can say something that's like, we will show you the first 500 records if you want. If you got more back and you want to see with the option to download the entire record set , download the exportif you got more than that in your results. If we can be say something that concretely in the documentation, I think that is fine for where we are at right now. I think, eventually, people are going to will expect the full pagination because that's what you get , in applications like Gmail , that's what you get in, in, you know, other other and other online tools. But I think I think if you can, as long as there's a way to get to the information, and as long as it's not like here's five records, if you want the rest, download the spreadsheet. I think that is okay.Unknown Speaker  58:57  
I see Sara's question in the chat. That. Yeah, this is only

Magda  58:57  
I see Sara's question in the chat. That. Yeah, this is only my rendering of a few records. In fact, as Erin suggested, mentioned, this is the scroll down that will show you the rest. This is actually how the inventory works as well. On the screen, you don't see that 100 Unless you usually have a very small fontresult. And I know Sarah, you were you were the person who was asking mostly about this. Do you have any other comments?

Unknown Speaker  Sara  59:37  
questions, requests?Unknown Speaker  59:41  
No, I just wanted to make sure because somebody mentioned 10 or something at some point. I just wanted to make sure ensure that we were that it was actually, as I was seeing it, that there was a scroll bar scroll bar that would take us through the first 10 100 and that it wasn't in debate about the 100 it was We're but more about whether we can do pagination. I guess I'm from other systems and others here to use all of and there was like on Aleph there is a pop-up modal that would pop out. And you could scroll you could just skim through. And then, you could also download it and put it in Excel to to manipulate it in detail. And so I guess the pagination, and while pagination works, it is a very, very cumbersome and folio, it takes forever to get from one page to the next page to the next page, right? So.Transcribed by https://otter.aivery, very cumbersome and FOLIO. It takes forever to get from one page to the next page and to the next page, right?

Magda 60:01
So would you rather have a thousand on one page instead of pagination?

Sara 60:33
I would prefer that, but I understand this is costly. I just did not want to go back to 10 selected.

Magda 60:48

I hear you. The simpler way right now is to change the preview from 10 to 100 and then download the rest to see more. We have two minutes left, so we are not going to get to permissions. We will get to that at the next meeting, or I will reach out to you on Slack. If you have more feedback, feel free to reach out to me. Thank you. Bye.