From: Andrew N. <as...@gm...> - 2009-06-15 20:11:01
|
Yeah - the ILS driver system does need to be generalized - or have the ability to be more specific to the system that it is talking to. This is where I was hoping Jangle would solve the problem. I would like to fully remove the driver model from VuFind and replace it with Jangle. Just calling one object to do the dirty work for us. Ross - how do we get the VuFind drivers into Jangle for this use? (I talked to you about this at Code4Lib). If we can use the community efforst of ILS communication much like we are using SolrMarc for marc importing - that's less duplication of effort. We have a lot of the dirty work done for us - oracle calls to voyager, api calls to alepha, api calls to SirsiDynix, screen scraping for III. Im sure Jangle could benefit from this. Andrew On Sun, Jun 14, 2009 at 8:30 PM, Greg Pendlebury <Gre...@us... > wrote: > > Indeed. I've been thinking lately that the driver object might need to be > wrapped inside a 'Business Logic' sort of object where > libraries can ignore the sql and horrible technical stuff from the lower > level and concentrate on what needs to be in the user interface. It's only > the start of an idea really and not something we're looking at changing any > time soon. > > When I first started working here I'd come from a Library where the > terminology was all completely different (request, reserves holds etc) and > both are different from what VuFind looks like out of the box. So ideally I > think the driver should know how to talk to your ILMS and the logic layer > knows how YOUR library uses (or abuses) an install of that ILMS. > > > Greg Pendlebury > Electronic Services Officer (Systems Team) > Division of Academic Information Services > University of Southern Queensland > Phone: +61 7 4631 1501 > Fax: +61 7 4631 1841 > > -----Original Message----- > From: Ross Singer [mailto:ros...@gm...] > Sent: Monday, 15 June 2009 10:17 AM > To: Greg Pendlebury > Cc: vuf...@li... > Subject: Re: [VuFind-Tech] A few questions about Drivers > > On Sun, Jun 14, 2009 at 7:43 PM, Greg > Pendlebury<Gre...@us...> wrote: > > > The broader issue is that this code won't be encapsulated within your > driver, you have to dig into the php code that builds the front end and the > ajax code as well. When I first started I naively thought we should move it > all into the driver... but I'm not so sure anymore, I think the driver > writing portions of your gui is worse then spread out business logic. The > balance of those two factors makes the change not so simple. > > This is a very good point (and I hope it didn't seem I was arguing > otherwise!) -- the driver absolutely should not drive the view. > > That being said, what the driver is is certainly a model class and probably > should be treated as such -- by this I mean with a formal model. I realize > that every ILMS will probably behave differently, but, in my mind, the goal > of the model would be something for the driver developers to work towards as > much as possible. When we realize where the averages are, we tweak the > model to conform to that. > > Right now the view is built with the expectations of a very specific model > (namely Voyager and, to a degree, Villanova's implementation of Voyager), > but if that model was abstracted a bit, there's no reason the view couldn't > be, as well. > > I'm not saying this is easy or can be figured out overnight... > > -Ross. > > This email (including any attached files) is confidential and is for the > intended recipient(s) only. If you received this email by mistake, > please, as a courtesy, tell the sender, then delete this email. > > The views and opinions are the originator's and do not necessarily > reflect those of the University of Southern Queensland. Although all > reasonable precautions were taken to ensure that this email contained no > viruses at the time it was sent we accept no liability for any losses > arising from its receipt. > > The University of Southern Queensland is a registered provider of > education with the Australian Government (CRICOS Institution Code No's. > QLD 00244B / NSW 02225M) > > > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech > |