Skip to end of banner
Go to start of banner

2021-11-30 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 15 Next »

Attendees (please add your name):

Magda Zacharska Robert Scheier Amanda Ros (OLD ACCOUNT) Erin Nettifee Monica Arnold Jennifer Eustis Christine Tobias Sara Colglazier Erin Weller Jenn Colt 

Note taker:

Robert Scheier

Meeting Recording: 


Discussion:

TimeTopicNotes 

Housekeeping:

  • Please add your name to the attendees list
  • Make sure Transcript option is turned on during the meeting



Development updates:




Bulk Edit Pilot - expectations - continue discussion 

So far we discussed and I believe we agreed upon :

  1. Small but reliable functionality that is limited to the user records as defined in in the scope of UXPROD-3225 
  2. Evaluated by Bulk Edit Working Group, SIGs, Product Council and  Technical Council: 
  3. Available for acceptance testing in a separate environment that will contain larger dataset and will not be refreshed nightly (RANCHER-63)

We still need to discuss:

  • Should it be included in Lotus release?
  • Next steps



Mitigation of Bulk Edit UX issues 

Slide 9:

  • Query-based, itemized, combination (for example: change location of the following holdings that are not currently checked out) 

Slide 16:

  • Long term -  we will support both in app and local editing
  • Short term  - local editing for the pilot program

Slide 17:

  • Provide a more transparent way of understanding what FOLIO did when batch processing
  • Better understanding of what a failure means -- did it revert the record, delete the record, invalidate the record?
  • Itemize failures so it’s easy to identify affected records, e.g. “record #XXXXXX failed,” not “7 of 10,000 changed failed”
  • Pay particular attention to global failure where feedback is especially spare
  • Give some indication, if possible, of how failure can be avoided
  • Provide some indication on how to re-try or follow-up from a failure

Slide 19

  • Optimize .csv files for understandability
  • Make it very clear which fields can or should be edited and which should be avoided  (in app or local edits?)
  • Provide some degree of instruction on how to make changes to commonly edited fields like status and location (in app?)
  • Give users the power to rollback changes upon upload if files are corrupted or mistakes were made (pre-update records stored in S3)
  • Anticipate potentials error and provide warnings, e.g. “Is this correct?,” “Are you sure?”

Mockup- file upload | Mockup - are you sure | Mockup - delete modal | Mockup - delete errors


Survey review:




Future discussion topic (time permitting):

  • Bulk Edit of the linked records
  • Scheduling edits



  • No labels