Web Client: Replace Barcode link missing from Cataloging Menu

Bug #1528912 reported by Terran McCanna
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Opinion
Undecided
Unassigned

Bug Description

In the current staff client, Replace Barcode is found under both the Circulation and Cataloging menus, but in the web client it is only on the Circulation menu.

My preference would be to have it on both menus, but if it is only going to be on one menu then I would prefer the Cataloging menu as it is more of a cataloging function (even when a circ person does it).

Revision history for this message
Mike Rylander (mrylander) wrote :

An explicit goal is to reduce clutter wherever possible especially so that documentation and training can be uniform where workflow is not impacted, and removing duplicate, unexplained menu entries is one of the ways to do that. I don't have a strong opinion on which menu should hold the Replace Barcode entry, though having it near other item-related entries such Item Status does make some sense to me -- there aren't really any entries on the Cataloging menu that are strictly about items.

Other opinions, anyone?

Revision history for this message
Kathy Lussier (klussier) wrote :

I'm in agreement with Terran that it makes more sense to include it in the Cataloging menu rather than Circulation since it generally is a cataloging function.

Revision history for this message
Rogan Hamby (rogan-hamby) wrote : Re: [Bug 1528912] Re: Web Client: Replace Barcode link missing from Cataloging Menu

I disagree. We usually have circulation staff replace barcodes because
it's inefficient for us to send the items back to central cataloging
departments. For us grouping it with circulation (or at least in item
status) makes perfect sense.

On Wed, Dec 23, 2015 at 5:33 PM, Kathy Lussier <email address hidden>
wrote:

> I'm in agreement with Terran that it makes more sense to include it in
> the Cataloging menu rather than Circulation since it generally is a
> cataloging function.
>
> --
> You received this bug notification because you are subscribed to
> Evergreen.
> Matching subscriptions: evergreenbugs
> https://bugs.launchpad.net/bugs/1528912
>
> Title:
> Web Client: Replace Barcode link missing from Cataloging Menu
>
> Status in Evergreen:
> New
>
> Bug description:
> In the current staff client, Replace Barcode is found under both the
> Circulation and Cataloging menus, but in the web client it is only on
> the Circulation menu.
>
> My preference would be to have it on both menus, but if it is only
> going to be on one menu then I would prefer the Cataloging menu as it
> is more of a cataloging function (even when a circ person does it).
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1528912/+subscriptions
>

Revision history for this message
Kathy Lussier (klussier) wrote :

And I think this is why we currently have this action in two different menus - because in some libraries it makes more sense to put it in cataloging and in others it makes more sense to put it in circulation.

I don't feel strongly about either location, but I would like to raise the question of whether it is necessary to remove every instance of redundancy in the web client menus. I agree that eliminating redundancy can simplify the client and reduce clutter in the interface. However, we can also think of it as offering multiple points of access to a function that is used by different departments in a library.

Some people will naturally gravitate to cataloging while performing this function while others will jump to circulation. Yes, we can train people, but if it is a function that a particular staff member rarely performs, they will inevitably spend time poking around trying to find the right menu.

In his article on reducing redundancy, Jakob Nielsen speaks to the idea of appropriately using redundancy to offer alternative navigation paths. https://www.nngroup.com/articles/reduce-redundancydecrease-duplicated-design-decisions/

The idea is that there are always a few items in a web application that could fall within a few categories and that the application shouldn't force the user to take just one path to get there. I think there are a handful of actions that fall within this category: replace barcode, search the catalog & item status are ones that immediately come to mind.

Revision history for this message
Terran McCanna (tmccanna) wrote :

I can see the argument both ways. Even when it is Circulation staff that performs the task, I still consider it a cataloging function. Changing a barcode is changing a property of an item in the catalog, it is not related to the process of checking items in and out. For those libraries that have their tech services staff do it (ours vary from system to system), it would seem counter-intuitive for them to go to the circulation menu to find it.

However, grouping it with Item Status also makes sense to me for the libraries that have their Circulation staff do it.

At the end of the day, if it's not in both places, it will be a small training issue for some libraries, which isn't the end of the world.

Revision history for this message
Terran McCanna (tmccanna) wrote :

Well put, Kathy. I vote for this particular action being in both places.

Revision history for this message
Jason Boyer (jboyer) wrote :

I would normally be all for it being in both places (especially if it meant not adding a preference to put it here or there...) but since the web client is made entirely of .tt2 files, I see no reason to try to please everyone with the defaults. Libraries that care can move it from one menu to the other or add it to both.

I would also vote that it be circ only, because if a cataloger is holding on to it they're likely going to do more than just edit the barcode. Anyone can throw a sticker on items, so they can change just the barcode somewhere else.

Revision history for this message
Kathy Lussier (klussier) wrote :

Whatever route we decide to go, I concur that we should NOT add a preference for where to place it.

Revision history for this message
Terran McCanna (tmccanna) wrote :

>>Whatever route we decide to go, I concur that we should NOT add a
preference for where to place it.<<

Agreed!

Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
<email address hidden>

Revision history for this message
Rogan Hamby (rogan-hamby) wrote :

Agreed.  Twice.  Can I agree three times?

---Sent from iPhone

>>Whatever route we decide to go, I concur that we should NOT add a

preference for where to place it.<<

Agreed!

Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
<email address hidden>

--
You received this bug notification because you are subscribed to

Evergreen.

Matching subscriptions: evergreenbugs

https://bugs.launchpad.net/bugs/1528912

Title:

  Web Client: Replace Barcode link missing from Cataloging Menu

Status in Evergreen:

  New

Bug description:

  In the current staff client, Replace Barcode is found under both the

  Circulation and Cataloging menus, but in the web client it is only on

  the Circulation menu.

  My preference would be to have it on both menus, but if it is only

  going to be on one menu then I would prefer the Cataloging menu as it

  is more of a cataloging function (even when a circ person does it).

To manage notifications about this bug go to:

https://bugs.launchpad.net/evergreen/+bug/1528912/+subscriptions

Andrea Neiman (aneiman)
Changed in evergreen:
status: New → Confirmed
Galen Charlton (gmc)
Changed in evergreen:
importance: Undecided → Wishlist
Revision history for this message
Kathy Lussier (klussier) wrote :

I'm wondering if we can close this bug now or mark it as Opinion since we appear to be marching forward with the web client without a strong push to move this menu item.

Changed in evergreen:
status: Confirmed → Opinion
importance: Wishlist → Low
importance: Low → Undecided
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.