[Koha-devel] Search Engine Changes : let's get some solr

Ian Walls ian.walls at bywatersolutions.com
Mon Oct 4 15:56:33 CEST 2010


Wouldn't using Solr also give us the flexibility to use non-MARC metadata
schemas, like MODS, METS, Dublin Core or EAD?  Indexes could be defined for
the whole system, with mappings for each supported metadata scheme on how to
get the data into said indexes.

The increased flexibility seems like it would be worth the higher system
requirements, at least for folks who could afford a suitably powerful
server.  The installation process should provide options to help tune Koha
to the available hardware (light and fast OR heavier and more powerful).

Cheers,


-Ian

On Mon, Oct 4, 2010 at 6:38 AM, LAURENT Henri-Damien
<laurenthdl at alinto.com>wrote:

> Le 04/10/2010 11:04, Zeno Tajoli a écrit :
> >  Hi to all,
> >
> >> Any feedback/idea welcome.
> >
> > the main problem that I see is that Zebra is much more light
> > on RAM.
> > Solrs is needs  Java + an App server J2EE (Tomact, Jetty ?).
> > If we select Solr, can we setup a library with 512 MB of RAM in the
> > server ?
> >
> > Bye
> >
> >
> Looking at most users we know, the problem of little RAM is the least of
> their problems, the question about accurate facetting with correct
> encoding and the ease of use, add and display index is more of their
> concerns.
> So yes, problem of RAM, but it could be overcome with a common web
> service say on solr.koha-community.org for instance, people could
> provide on an external server to index and get search results from.
>
> We chose to base our POC on Data::SearchEngine If you want to know more
> details on dependencies.
>
> --
> Henri-Damien LAURENT
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>



-- 
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20101004/de5dbd4b/attachment.htm>


More information about the Koha-devel mailing list