Skip to end of banner
Go to start of banner

2021-10-19 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 18 Next »

Attendees (please add your name):

Magda Zacharska, leeda.adkins@duke.edu Monica Arnold Autumn Faulkner (OLD ACCOUNT) Erin Nettifee Jackie Magagnosc Robert Scheier

Meeting Recording (once available):

Discussion:

TimeTopicNotes
10:02Introductions and Expectations
  • Magda: Please add your SIG affiliations to the list of working group members column on the Bulk Edit Homepage list of working group members so I can reach out to subject area experts as needed.
  • Magda: I represent you while talking to developers. But I also represent developers while speaking to you. I need to find a balance between what is needed and what can be implemented.
  • Magda: We will be starting with a pilot project or proof of concept as some like to call it.
  • Magda: I will reach out to you with a survey asking what your expectations are for this pilot project, and how you would determine that this project is a success.
  • Magda: We will not cover bulk deletion. We will be working on bulk edits for user records only in this pilot program.
  • Erin: Is there anyone from the User's SIG here?
  • Magda: There are but they are not attending today's meeting. I will be sending the recording to them.
  • Bob: Since we are focused on users when I provide feedback do you want us to keep it focused on user records. Or can I provide feedback on other kinds of records I work with?
  • Magda: Yes, other kinds of records. That is the reason the group is cross SIG. I need you to bring to my attention when there are things specific to areas other than users.
  • Magda: I want to concentrate on communication. Please let me know if you do not understand or I am not clear in my statement. We need to be on the same page.
  • Magda: Play with the application once features are developed. Early feedback is the most valuable feedback because we have access to development resources. They can address the issues in a week or two. If we start getting feedback once the software is released, addressing the issues is delayed until the next release. Provide feedback as early as you can.
  • Mark: Do we have a release date?
  • Magda: Yes, the plan is to have a release with Lotus.
  • Christy: Is there any expectation for when this is going to expand beyond users?
  • Magda: The plan is to have some basic functionality available by January for the pilot project. We will review and adjust and then every release, every three or four months, we will move to the next functional area. This group will decide the order of development. Based on use cases so far, the next area to be developed will be items. I would like to start with the most simple and move toward the more complex and leave MARC to the end when I will understand your needs better and the development team will be more experienced and able to build more complicated things faster.
10:31

Housekeeping:

  • Notetaker 
10:34Review 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 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 will be built to deliver functionality.

Review of Pilot Features:


Survey results overview

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



  • No labels