Re: [VuFind-General] Minor VuFind refactoring

[Wayne G. <ws...@wm...>]

My vote is to put it either in the excisting index, but perhaps
another solr index would make more sense for this data. It's reltively
trivial to create a JNDI solr instrance with multiple indexes (say one
being named solr and the other vufind-data). You get the same data
speeds you have with the current index, and just call another index to
pull the information.

Wayne


On 11/21/07, Andrew Nagy <and...@vi...> wrote:
> > -----Original Message-----
> > From: vuf...@li... [mailto:vufind-
> > gen...@li...] On Behalf Of Chris Delis
> > Sent: Wednesday, November 21, 2007 10:44 AM
> > To: vuf...@li...
> > Subject: Re: [VuFind-General] Minor VuFind refactoring
> >
> > Not only are there potential filesystem issues, it also severely
> > limits our flexibility in hardware configuration, e.g., we may end up
> > splitting VuFind off into a web tier farm and this will cause
> > headaches, I'm sure.  In any case, we would like to see some sort of
> > new approach (storing the data in either in one or multiple fields in
> > SOLR or in mysql) in VuFind main development.  If this doesn't happen,
> > we will most likely implement our own solution anyway out of pure
> > necessity :-).
>
> Yes - I see that this is a major problem with larger institutions and I
> agree that something should change to make this easier.
>
> Here is a summary of options:
>
> * Keep everything as is and force larger institutions to solve the problem
> themselves
>   - not a very friendly approach :(
>
> * Create a non-indexed field in the SOLR repository for the full marc record
>   - could cause solr performance to decrease
>   - will increase size of lucene index
>   - use of index in "inappropriate" ways
>
> * Add all marc fields to the SOLR schema
>   - potentially hundreds of fields
>   - institutions use fields differently
>   - could cause solr performance to decrease
>   - allows greatest flexibility in customizing search algorithms at
> individual institutions
>
> * Store marc records in local database
>   - MySQL
>   - Use Native XML Database: eXist, Berkeley DBXML
>   - Use an embedded database such as SQLite
>   - Allows for an easy accessible location for reimporting/reindexing if
> ever necessary
>
> * Use ILS for Marc store
>   - Kills ILS abstraction (cannot use vufind when ILS is down)
>
> How about this as an alternative - a configuration option for the importer.
> Allow for local filesystem storage of records or within SOLR?
>
> Maybe we could try a vote as to what everyone thinks is the best option.
>
> 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
>