...
| Topic | Notes | ||
|---|---|---|---|
| 1 | Scott Perry Housekeeping
| Jennifer Eustis and Lynne Fors | |
| 2 | Development updates |
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.
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. | |
| 3 | Poppy UAT follow up | Error message consistency: field level errors and warnings vs. record level errors and warnings "No change in value" notification only if there were no changes to any field in the record. Informing only on the record level. Messaging is confusing. Is there a way to get information on what has been changed and what has not been changed only if there is no change in one of the actions? Possible best route to take is to give as much information as possible about what has been done to the records? General feeling that we would prefer to know exactly what was changed. Come back to this next time. | |
| 4 | Suppressing/Unsuppressing Bound-with Items | Bulk Edit - Suppressing/Unsuppressing Bound-with Items Documentation has been updated with more explanations and screenshots. Please provide feedbacfeedback. | |
| 5 | Bulk edit holdings notes - (UXPROD-4020) | Bulk Edit - Item, Holdings and Instance Notes |
...