Review of Pilot Features: | - Magda: Please feel free to post questions or comments about the pilot features. I will be adding additional features as our meetings progress for additional functionality.
|
10:34 | | - Magda: This is an umbrella feature meaning it has a couple of features associated with it. One is already in progress.
- Magda: The scope of this story we will support the searching user by user group, and identifying records by providing barcodes.
- Magda: And within the edit, we will support removing user permission, updating expiration date, updating patron group, updating email.
- Magda: If we go with the approach of downloading and uploading files, which is the most likely approach for the pilot, then you will be able to edit other fields as well.
- Magda: The pilot project will cover the following elements:
- Identify records for editing
- Edit record(s): add data, remove data, update data
- Review changes
- Confirm changes
- Commit changes
- Log committed changes
- Handle exception (including notifying users)
- Magda: Once the pilot work is done we will need to review this. And the question is who will we review this with. Do we review with the product council, technical council, or will this group review it?
- Magda: Based on findings we will recommend implementation for other areas.
- Magda: The question I have is who will make the decision that the work that was completed is OK for further implementation. The answer to this will be part of another survey that I will send to you later this week.
|
10:37 | | - Magda: The first feature is already in progress. It is the preliminary work for project setups in GitHub, Jira, and adding specific UI components to the Bulk Edit page which is already available on snapshot. But it also contains several spikes, the areas that developers need to investigate the best possible approach for development. Based on this more technical stores or features we will be building in order to deliver the functionality.
|
10:38 | | - Magda: It will consist of two options, search using a list of user barcodes or other identifiers as time permits and searching by user group.
- Erin: Going back to the umbrella UXPROD. Even the limited Bulk Edit scope is a little bit too big. The permissions records are not part of the core user record which would introduce significant complexity. Are we at a stage where we can pull this back even further? What do you think?
- Magda: I am glad you brought this up. This is one of the questions I had on my list to ask. And this question also applies to permissions, fees, and fines. It also applies to all other records: inventory, all the reference data, instances, holdings, items, and relationships. We will be talking about this probably during the next meeting. But, yes it is possible the list will be narrowed down.
- Erin: I am in favor of that, but I do not remember what the context was from the UM discussion.
|
10:41 | UXPROD-3318 (User records - bulk edit - pilot implementation) | - Magda: This involves a lot of unknowns here because the final implementation of this will depend on the findings of the spikes that the team will be working on in this and the next sprint.
- Magda: In the scope of this feature are:
- The user will be able to save the file with the records that match the search criteria
- Make the changes locally and upload the modified file so that the changes are posted
- The system will handle exceptions
- The system will notify the user about the exceptions
- Magda: Out of scope of this feature are:
- Bulk Edit updates to other than user records, e.g., inventory records, fees and fines, permissions (we will come back to this as mentioned above).
- Bulk deletions are not in the scope of the pilot project.
- Magda: Questions are:
- Handling permissions
- Handling fees and fines
- Handling loans
- Erin: No questions but just a comment. It is kind of related to permissions that I am very nervous about bulk editing anything that is involving finances, and anything involving business logic which is both fees and fines and loans because you don't want to edit the underlying record in such a way that it violated the overall business logic that would have managed it if it was one by one.
- Magda: I am also very concerned about data confidentiality, who can do what, who can see the data, and I am also very concerned about the impact of Bulk Edit because if we do not do it right we can introduce a lot of problems for the underlying data. So those are things that we need to be very cautious about. I would like to have the permissions as restrictive as possible. So limit access, especially in the beginning, to those that know what they are doing, and then as the application matures address those. This is definitely on our list of things to discuss.
- Thomas: Are you thinking that Bulk Edit will have its own permissions that will override other apps' permissions?
- Magda: This is something we will need to discuss. To be honest I did not even think of overriding other permissions. Do you have a use case for that?
- Thomas: I was mainly thinking in the realm of user's settings. I know that there are very finite permissions for editing users. If someone has permission in the Bulk Edit APP that allows them to edit user data, it might bypass the security settings that are already in place in the Users App. I'd prefer that the opposite happen, that Bulk Edit looks at the user's permissions and then does not allow them to change data that they do not have permission to do in the other app.
- Magda: This is a very good point, thank you.
|
10:45 | | - Magda: The team that will be working on Bulk Edit is Firebird. They are located in Belarus and other parts of Europe. Besides Bulk Edit the team works on Data Export, OAPMH, circulation logs. So their plate is full. At this point, Bulk Edit, and data export of holdings are the highest priorities. But they will need to be supporting these other areas as well. As you can see there are already several Bulk Edit stories in progress or completed.
|
10:46 | | |
| | - Magda: Our next item is to review the feedback but I do not think we have time to do this today. I will post in chat and link to responses in Slack. But I have a very basic question. many of you in your comments refer to something as global updates. What do you mean by global updates?
- Bob: I'll take that. That refers to the terminology in Sierra. That is what we call bulk edit in Sierra.
- Leeda: It's the same in ALEPH. That feature is called, I believe, Global Changes instead of bulk.
- In Chat: 01:01:38 Sara Colglazier (MHC/5C): Yes, for ALEPH Global Changes
- Magda: The other question is for you Robert. You posted a recording of the edits in Sierra. There is no sound. Is that because I don't know how to turn on the sound or you recorded without sound.
- Bob: I did not speak during the capture.
- Magda: It was easy to follow to some point but then I got lost a little bit. So, I will reach out to you with some follow-up questions for you if that is OK.
- Bob: Sure, yup.
- Magda: We are at the top of the hour. Thank you so much for your time and feedback we has a really good question I will send a couple of more surveys or at least one. See you all in two weeks.
|
| Future discussion topic (time permitting): - SMEs expectations from the Pilot Project
- Bulk Edit Permissions
- Max number of records to be edited via User Interface
- Scheduling edits
|
|