Dan, I looked at it and it looks good to me. I have not worked with an ILS system that tried to load the information about which student is in which course to be able to limit access via that information. That, of course, changes a lot, so is not too easy to maintain. We've opted so far to try to put that through the course management system, but, hey, if you can do it, go for it. That kind of limitation has become very important when you scan in a copy of something for use by a class, as opposed to when you were just using hard copy circulated from the reserve desk. The RFC accommodates the preferred method of a URL to a licensed resource, that's good, too.
Frances McNamara University of Chicago -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Scott Sent: Saturday, July 12, 2008 1:43 PM To: Evergreen Development Discussion List Subject: [OPEN-ILS-DEV] Academic reserves RFC: second revision Hi folks: Thanks to everyone who responded to the academic reserves RFC; there were some excellent responses both on and off list. I've updated the RFC at http://open-ils.org/dokuwiki/doku.php?id=feature:academic_reserves doing my best to incorporate your comments. In this revision of the RFC, the scope has expanded from simply addressing existing items within the ILS to trying to address the most common requirements for electronic reserves. I do worry about feature creep, and am not trying to replace dedicated third-party reserves systems in the first iteration of the Evergreen reserves module, but your comments convinced me that there would be a significant improvement in process and flexibility if the system is capable of handling a broader set of reserve items. I would greatly appreciate another round of comments on the RFC - even if it's simply a matter of "sounds good" or "please stop wasting my time, you're so far off the track!". If it's the latter, then I'd rather hear it now than six months down the road :) -- Dan Scott Laurentian University
