Webstaff UI issue in the volume/copy editor
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.2 |
Won't Fix
|
Undecided
|
Unassigned | ||
3.3 |
Won't Fix
|
Undecided
|
Unassigned | ||
3.4 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
In the Volume/Copy editor, it's hard for users to tell what volumes/copies already exist, and which are in the process of being created.
I just worked with a member of our staff who was trying to add a volume on a bib record for which a volume already existed. Instead of doing this:
1) Open the bib record.
2) Press "Add Volume"
3) Check the pre-populated call number and add a barcode
4) Fill out the item-level data and hit "Save and Exit".
They were doing this:
1) Open the bib record.
2) Press "Add volume"
3) Seeing the call number (which happened to be the same as the existing call number) and assuming that that entry referred to the copy we already have in the system. They assumed that the barcode field was empty due to a bug in the Web client, rather than being a totally new copy.
4) Pressing the "Add volume" button again and becoming frustrated when the "Save and Exit" button didn't work.
Looking at the interface, there's no way I could possibly fault them. I've attached a screenshot, in which I challenge folks to try to guess whether this is a new volume/copy or an existing one.
I'm not sure what the best UI intervention might be, but I'm looking forward to lots of great ideas from our brilliant community. :-)
tags: | added: usability |
Changed in evergreen: | |
status: | New → Confirmed |
tags: | added: webstaffclient |
tags: | added: cataloging |
Changed in evergreen: | |
assignee: | nobody → Jason Etheridge (phasefx) |
Changed in evergreen: | |
milestone: | none → 3.2-rc |
Changed in evergreen: | |
milestone: | 3.2-rc → 3.2.1 |
Changed in evergreen: | |
assignee: | nobody → Dan Wells (dbw2) |
Changed in evergreen: | |
milestone: | 3.2.1 → 3.2.2 |
Changed in evergreen: | |
milestone: | 3.2.2 → 3.2.3 |
Changed in evergreen: | |
milestone: | 3.2.3 → 3.3-beta1 |
Changed in evergreen: | |
milestone: | 3.3-beta1 → 3.3-rc |
Changed in evergreen: | |
milestone: | 3.3-rc → 3.3.1 |
Changed in evergreen: | |
milestone: | 3.3.1 → 3.3.2 |
Changed in evergreen: | |
milestone: | 3.3.2 → 3.3.3 |
Changed in evergreen: | |
milestone: | 3.3.3 → 3.3.4 |
Changed in evergreen: | |
milestone: | 3.3.4 → 3.3.5 |
Changed in evergreen: | |
milestone: | 3.3.5 → 3.4.2 |
Changed in evergreen: | |
milestone: | 3.4.2 → 3.4.3 |
tags: | added: signedoff |
Changed in evergreen: | |
milestone: | 3.4.3 → 3.4.4 |
Changed in evergreen: | |
assignee: | Dan Wells (dbw2) → Galen Charlton (gmc) |
milestone: | 3.4.4 → 3.5.1 |
importance: | Undecided → Medium |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Jane -- does the work on bug 1739087 provide enough of a visual cue here? New vols/copies will have the x next to them for removal before saving; if you are editing you should not see the x.