Trouble logging in using correct library location

[GoogleCodeExporter]

Currently, we are using the 'eg_locg' cookie value to determine the library ID 
which is then mapped to authorization name as part of the credentials to log 
into OD. Two problems:

1. It looks like the search parameter 'physical_loc' takes precedence. If it is 
present, the eg_locg cookie is not updated, and therefore could be the value 
from a previous session, which could belong to a different location.

2. A patron may not be using the website belonging to the home library, but 
home library will only map to the correct authorization name.

Original issue reported on code.google.com by steven3...@gmail.com on 9 Jul 2014 at 7:54

[GoogleCodeExporter]

Fixed by getting home library (in long name format) from patron's preferences 
page and mapping long name to OD authorization name.

Was able to log into bh.testing1 using bwfakeexpired, after using the same 
username to log into bw.testing1.

Original comment by steven3...@gmail.com on 10 Jul 2014 at 7:00

• Changed state: Fixed