2021-07-14 Meeting notes

Date

Attendees

Goals

  • Magda Zacharska will walk us through Bulk User Edits
  • Björn will discuss the roadmap

Discussion items

TimeItemWhoNotes
5 minNote-takerAmelia has agreed to take notes

Additionally, during this time, Maura shared the link to the folder for common test cases.

40 minBulk User EditsMagda Zacharska
  • A Bulk Edit Workgroup has come up with several pilot projects to make sure Bulk Edits work correctly.
  • Bulk Edits are defined as:
    • Changes to one or more properties of a record that apply to one or more records and are applied simultaneously
    • UM-SIG believes that Bulk Edits should be able to be done via the UI.
  • The funtional areas where Bulk Edit is necessary are:
    • Inventory
    • Circulation
    • Users
    • Acquisitions
    • ERM
    • SRS
    • Courses
    • Tags
  • All of these functional areas have similar workflow needs for a Bulk Edit.  They are:
    • Search for records, and select records to be edited
    • Records are edited, data is either added removed or updated
    • Changes are reviewed and confirmed then committed
    • Then changes will need to be logged and have exceptions handled
  • There should be other ways to select items
    • Importing a list of items matching on any unique identifier
    • Searching for items
    • Manual selection
  • The pilot projects will be in either Users of Inventory.  The pilot project involving Users will work with these initial features:
    • Start with searching and selecting users by user groups or a use of barcodes
    • Edits: remove permissions, update expiration date, update patron group, update email
  • If the pilot works, UM-SIG gave a list of other functions that are desired.
    • Patron blocks and Expiration Dates are future desired search parameters
    • Patron blocks and bulk password reset are future desired edits
  • Full pilot scope will be determined after development resources are secured
  • Project goal:  full implementation of Bulk Edit across FOLIO by 2023
  • Project needs a SME working group for verifying and determining requirements
    • Determining priorities, must have scenarios, and nice to have scenarios
    • We were presented with making a working group or using SIG meeting time to do this work.
    • Decision: This work will be done in time set aside in UM SIG meetings starting in August.
      • We will set aside about 15 minutes per meeting, and we'll have to be disciplined about time.
  • UM can have conversations about whether there should be a Bulk Edit App or if Bulk Edit actions should be implemented individually to each app.
15 minRoadmapBjörn
  • Björn presented a document that showed the roadmap, which was a purely informative diagram showing what was being worked on, what was scheduled to be done in the future, and when things would be completed.
  • The document was purely for informational purposes, and doesn't reflect any decisions or policy changes.
    • Everything in the document is subject to change.
    • The document will not be shared, because anything on it could change at any time, so no one could rely on the data there at any time.
    • The document was shared in the meeting, so if anyone wants to see it they can watch the recording of this meeting.
  • As an added note, Björn will be stepping away from the Roadmap team and will no longer be the PC Liaison for UM-SIG.  We are grateful for his many efforts in both areas.

Action items

  •