Call number prefix and suffix interfaces do not always honor context ou

[Kathy Lussier]

Evergreen version: 2.2 RC1

When accessing Server Admin < Call Number Prefixes or Call Number Suffixes, the initial screen will only display the affixes belonging to the context OU, as is expected. However, once you click "Next" to get to the next page of affixes, it will display affixes belonging to other org units.

[Michele Morgan (mmorgan)]

This is still a problem in Release 2.5 and makes managing prefixes in a library almost impossible through the staff client. Here is a link to a very quick and dirty silent screencast of what one of our libraries sees in the call number prefix interface:

http://screencast.com/t/eEEb1wdmMZNG

[Michele Morgan (mmorgan)]

Still a problem in 2.7. Changing status to Confirmed, better late than never.

[Michele Morgan (mmorgan)]

This is still an issue in Evergreen 2.12, and 3.0. The prefix/suffix screens behave no better in the web staff client than in the xul client.

[Janet Schrader (jschrader)]

I tested this on our training server with release 3.5 as I didn't find any prefixes on https://bugsquash.mobiusconsortium.org/eg/staff/

This appears to be fixed in 3.5. I can confirm that I was able to page through multiple pages of prefixes, one of our libraries has over 400. It's like a miracle so someone else please test and prove this is true.

NOTE: Usability issue: the far left column numbering the prefixes only displays up to a 2-digit number; after #99 all you get is 1.., 1.., 1.. I didn't see a way to expand this column.