User login
Quick Help
SVN Commit Log
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
I found a couple of comments by John to be useful in thinking about how SOPAC is architected:
Core SOPAC functionality consists of providing tags, reviews, ratings, and RSS. Any other functionality should probably be split off into either a sub-module, or an external module.
One test for whether some sort of data should go into the insurge database tables is whether it will add value for the larger insurge community. If it is only valuable for a specific library, the data should probably be stored elsewhere.
As a group, we decided that for now we will use the drupal.org issue queue not only for SOPAC, but also for locum and insurge. All developers are encouraged to use that issue queue. This includes adding feature requests for items that one is developing oneself so that others know who is working on what.
Current active development work for Q2/Q3 2009:
John (Darien Library):
-Incorporating support for associating multiple cards to a single account
-Ability to "friend" someone/reviewer (ala Summer Reading)
-Preliminary work on multi-branch
-Item-level location
-RSS
-Checkout history
Ryan, Eric (AADL):
-Item-level location
-Multi-branch
-Cover cache script
-Wishlists (initial foray into netflix)
Sid (Craftyspace):
-Control panel UI to Locum/Insurge config
-Sub module to put Locum/Insurge into Module subdirectory
-Multi-brach pickup location handling
One more thing I'd like to add to the list, and I'm already pretty far along on, is the ability for Locum to handle diacritics (see http://thesocialopac.net/node/44).