2023-8-8 Bulk Edit Working Group Meeting Notes

Scott Perry Housekeeping

• Attendees  - please add your name to the list of attendees
• Meeting host -  please turn on Transcript option for the meeting 
• No meeting on August 22nd
• Who can take notes today?
• Other topics?

Jennifer Eustis and Lynne Fors

  Development updates

• Development status
• Development team scrum board
• Issues from Orchid UAT 
• Issues from Poppy UAT 

• Change in the name of Bulk edit (CSV) to Bulk edit (Local)
  • The term CSV was misleading and often misunderstood. This has already been done. This is available for User records only. This approach was deprioritized for Inventory Bulk Edit actions.
• Instance column name (UIBULKED-275)
  • The instance column contains title and instance UUID. Suggest changing this to how it appears in the holdings record (Instance: title, publisher, dates). Could the name of the column have in parentheses what is included in the information?

Everyone approves of this change.

Suggest have column for each note type separated and populated for those with data. Could we do icons instead of using bold for notes for staff? It's hard to find an icon for things. Any note can be staff only. Kimie will think about it and talk to Magda about this more. Implementing an icon may be more difficult than changing the font. It would make more sense to have, Staff Only: . Could the suppressed icon be reused? Would could add another column with this information? Having verbage would be better if we needed to export these data. The notes are repeatable. Madga likes the approach with the parentheses and having this after the note. We will try this the first time around and see how it goes. Is each note separated by a semicolon? Yes. Having the parentheses would mean: Note: My action note (Staff Only) ; Note: My copy note. We could also use the pipe as this is less common. We can use pipes instead of semi-colon. Note: My action note (Staff Only) | Note: My copy note. The space is difficult to troubleshoot when you look at notes. The double pipe is the best approach but this is difficult in Excel. The single pipe is already implemented.

We agreed to have separate columns for notes with the separator being a pipe. If the note is staff only, then we spell this out in parentheses, (Staff Only) appearing after the note.

• Change note type expected behavior

It is expected that the note type to change from current type to specified note type and stop there. These actions would take place at the same time and not in a sequence creating a loop. Suggestion: A tool tip at the Actions header to explain what happens. Would we do this kind of chain in actual workflows? Unlikely. Could see a chain to change the note type and whether it was a staff note or not; needs further investigation. How do we communicate to user that changing the note type will change all notes of that type? Tool tip at Actions header. Needs further investigation. Sierra allowed nesting actions; this method could create more issues and confusion. Will come back to this later.