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 Donald Depoorter leeda.adkins@duke.edu Amanda Ros (OLD ACCOUNT) Erin Nettifee Sara Colglazier Monica Arnold Kimie Kester Scott Perry Thomas Trutt Jenn Colt Jackie Magagnosc Christine Tobias gongd@msu.edu
Note taker:
Robert Scheier
Meeting Recording:
https://drive.google.com/file/d/1NthOtUquu5_GXnRDPgqSvVMozMcCNjpJ/view?usp=sharing
Discussion:
Time | Topic | Notes |
---|
| Housekeeping | - Please add your name to the attendees list
- Should we cancel our next meeting (December 28)?
|
| Announcements | - Product Council recommended including Bulk Edit Pilot in the Lotus release.
- Technical council requested additional documentation - which is expected considering that the deadline for the core platform modules is February 4th
|
| Development updates | |
| Mitigation of Bulk Edit UX issues | 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
|
|