User login
Quick Help
SVN Commit Log
Locum
rev 164: 06.07.10 10:33
submitted by: jblyberg
Small adjustment to the .ini file.
Fixed a bug in the syndetics code that prevented syndetics cache from timing out correctly.
Fixed a bug in the syndetics code that prevented syndetics cache from timing out correctly.
Connectors
rev 126: 06.12.10 1:53
submitted by: smaskit
refactor: replace all instances of self:: with $this-> in iii 2007 connector
License Informaiton
SOPAC, Locum, and Insurge are made freely available under the GNU Public License v3
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution 3.0 License
Search
New forum topics
Recent comments
- A viable alternative is
4 hours 29 min ago - Great things you've
23 hours 25 min ago - Many folks setting up
2 days 5 hours ago - Thanks for sharing
2 days 8 hours ago - SEO
2 days 11 hours ago - Nice post! thanks and keep on
2 days 12 hours ago - NM, i'm getting farther.
2 days 14 hours ago - Thanks you for the post.
2 days 16 hours ago - Thank you for taking the time to publish this information
2 days 22 hours ago - Awesome and interesting article.
4 days 6 hours ago



The current version does not support multiple pickup locations. Requests for holds will always fail under this condition. I am close to having a patch which implements this feature.
I have solved this problem by using the profile module. Enable this module, then define your pickup locations.
Here is a nice little video that show you how to do this.
http://www.youtube.com/watch?v=Vd6Qklh13Ss
Thanks to funding by The Palos Verdes Library District, CraftySpace CMS has updated SOPAC so it handles multiple branches in the following ways:
1) When a user is placing a hold, they will be presented with a pulldown to select at which branch they wish to pick up the item. (In a single branch situation, this step is skipped.)
2) As part of a user's profile, a user may choose a branch as their home branch.
3) If a user has selected a home branch, that will be the selected default in the pulldown mentioned in #1 above. (Currently, that is all that home branch is used for.)
4) The site admin can enable or disable having a home branch as part of the user profile.
These changes have been committed to the svn development branch, and will be part of the next release.