From: Steven M. <smc...@nl...> - 2007-11-21 22:58:52
|
On 22/11/2007, at 4:43 AM, Andrew Nagy wrote: > > Maybe we could try a vote as to what everyone thinks is the best > option. > I would put my vote towards using MySQL to store the full MARC record. My reasons: 1. It's what we've done already :) 2. MySQL is made for storing data, SOLR is made for indexing. MySQL is much easier to backup, recover. With SOLR, I imagine you don't backup / restore, but recreate the indexes. 3. You've already got MySQL for storing user data 4. Its easy to implement and doesn't require any immediate change to the vufind presentation layer. But I guess there's no reason why there can only be one solution. In creating an interface to MySQL as the datasource Mark created a record access driver which implements functions to get and write a record. This is defined in our config.ini. Supporting a record access driver approach has implications for the importer, however - I guess for each driver created, a corresponding import interface is also required.... In the longer term, I think I would advocate some extra power in the vufind model layer to cope with the record. (Our) marcxml is unwieldy to manipulate using xslt alone. > Thanks! > Andrew > > > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > VuFind-General mailing list > VuF...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-general ---- Steven McPhillips <smc...@nl...> IT Business Systems National Library of Australia |