Comment 6 for bug 1402018

Tina Jordan, Leslie St. John, Chris Sharp, and I spent time looking at this during bug squashing day and were unable to come to any resolution related to the ticket because we are not seeing a problem on our production server - it is showing the copy locations we expect it to.

For example, one of the systems in our consortium is STATELIB, which has two branches - STATELIB-L and STATELIB-B. Our acquisitions users for the STATELIB system have working locations set to both STATELIB-L and STATELIB-B. When they log in to a workstation registered to STATELIB-L, they see available copy locations for both STATELIB-L and STATELIB-B. (See attached screenshot, which is from a PO for STATELIB-L. The user is logged in as an ACQADMIN type user on a STATELIB-L registered workstation, and who has STATELIB-L and STATELIB-B working locations.)