[OPEN-ILS-GENERAL] BRrrrrrrrrrr

2012-11-06 Thread Donald Butterworth
Wise Ones,

When setting up Organizational Units in 2.3 a sample hierarchy is included
that uses the Organization Unit Policy Codes: CONS, SYS, BR, AND SL. Is
there a reason why these codes could not be changed so that they would be
more intuitive in our local setting? Here is what I have in mind

CONS = ASLAN (Asbury Library Automation Network)

SYS1 = ATS (Asbury Theological Seminary)
BR1 = BLF (B.L. Fisher Libray)
SL1 = SA (Seminary Archives)
SL2 = BL (Beeson Leadership Library)
BR2= MDD (Maxie D. Dunnam Campus Library)

SYS2 = AUL (Asbury University Libraries)
BR3 = DFK (Dennis F. Kinlaw Library)
SL3 = UA (University Archives)
BR4 = AUF (Asbury University Florida Campus Library)

Anybody know if this will cause a problem, before I pull the trigger?

Don

Don Butterworth
Faculty Associate / Librarian III
B.L. Fisher Library
Asbury Theological Seminary
don.butterwo...@asburyseminary.edu
(859) 858-2227


Re: [OPEN-ILS-GENERAL] Display Holds Queue Position in TPAC?

2012-11-06 Thread Lindsay Stratton

We are running 2.2 and the TPAC, and hold queue position does display. I don't 
know how it is configured, but I think it is pretty much default behavior - we 
have not customized any of that display, at any rate. 


In the patron account  items on hold list queue position is in the Status 
column and looks like Waiting for copy / 21 hold on 41 circulating copies. 


Screen shot here: 
http://plum.pls-net.org/twiki/bin/view/Evergreen/OpacMyAccountHolds 


FWIW, the queue position value *appears* to be static, indicates the number of 
holds placed before your hold, and does not adjust as other holds are filled. 
It certainly does not have any relationship to hold fulfillment (unless, I 
guess, one is using first-in-first-out hold fulfillment!) 

Hope this helps. 


Lindsay Stratton 
Training Coordinator 
Pioneer Library System 
2557 State Rte 21 
Canandaigua, NY 14424 

http://www.pls-net.org 


- Original Message -


From: Ann Young you...@santacruzpl.org 
To: open-ils-general@list.georgialibraries.org 
Sent: Monday, November 5, 2012 4:53:17 PM 
Subject: [OPEN-ILS-GENERAL] Display Holds Queue Position in TPAC? 

Hello, 


We just upgraded to Evergreen 2.3 and in doing so moved from the old JSOPAC to 
the TPAC. In the old OPAC we had been able to display the holds queue position 
in My Account by modifying myopac.js (changing var showHoldQueuePosition = 
false to true). Is there any possible way to show the queue position for 
patrons in the TPAC? I understand that there are potentially issues with the 
accuracy of the queue position, but our patrons are very anxious to have this 
functionality available to them. 


Thanks for any help, 


Ann Young 
Systems Coordinator 
Santa Cruz Public Libraries 
224 Church Street 
Santa Cruz, CA 95060 
(831) 427-7707 ext. 7766 




Re: [OPEN-ILS-GENERAL] BRrrrrrrrrrr

2012-11-06 Thread Jason Etheridge
Don, I see no problems with that.  One convention that PINES came up
with (or inherited from their previous system) was to combine the
system shortname with the branch shortname to expose a bit of the
hierarchy at a glance when looking at a specific lib, and to reduce
the chance of collision with shortnames.

So for example, you may want to consider:

ASLAN
- ATS
-- ATS-BLF
--- ATS-BLF-SA
--- ATS-BLF-BL
-- ATS-MDD
- AUL
-- AUL-DFK
--- AUL-DFK-UA
-- AUL-AUF

-- Jason


Re: [OPEN-ILS-GENERAL] BRrrrrrrrrrr

2012-11-06 Thread Rogan Hamby

SCLENDS did the same thing.  We came up with the same convention
independently.  It also helps a lot when doing various manipulations of
report data.

-- 


Rogan Hamby
Manager, Rock Hill Library
803-981-5853

York County Library System
http://www.yclibrary.org | http://www.facebook.com/yorkcountylibrary


“You can never get a cup of tea large enough or a book long enough to suit
me.” 
― C.S. Lewis http://www.goodreads.com/author/show/1069006.C_S_Lewis





On 11/6/12 10:38 AM, Jason Etheridge ja...@esilibrary.com wrote:

Don, I see no problems with that.  One convention that PINES came up
with (or inherited from their previous system) was to combine the
system shortname with the branch shortname to expose a bit of the
hierarchy at a glance when looking at a specific lib, and to reduce
the chance of collision with shortnames.

So for example, you may want to consider:

ASLAN
- ATS
-- ATS-BLF
--- ATS-BLF-SA
--- ATS-BLF-BL
-- ATS-MDD
- AUL
-- AUL-DFK
--- AUL-DFK-UA
-- AUL-AUF

-- Jason