Forum OpenACS Development: Re: Need help with Site-wide-search and search packages

Collapse
5: Re: Need help with Site-wide-search and search packages (response to 4)
Posted by Alejandro Beya on 02/18/04 07:06 PM
Hi Dirk! I was just about to send you and e-mail! I have been searching information about this issue and I came up with your OpenACS Search proposal. I found it very interesting. I was wondering if, since you wrote that, you had advanced work or if you knew someone who had finished porting to OpenACS 5 this package. This package is so important for Project/Knowledge that if we don't find the package for OpenACS 5 with Oracle, we will port it ourselves from OpenACS 4.x We wanted first to ask the community if this was done so we could save time. Dirk, greetings from Frank. Bests, Alejandro Beya alejandro.beya@project-open.com http://www.project-open.com/knowledge/
Collapse
6: Re: Need help with Site-wide-search and search packages (response to 5)
Posted by Dirk Gomez on 02/19/04 07:19 PM
I doubt you'll find the code useful. It requires short urls, central package_ids etc all of which is available on the site I was developping against.

Your best bet is to take ACES' site-wide-search which is imho the best freely availabe OpenACS/ACS site-wide-search implementation and port it to OpenACS5.

Collapse
7: Re: Need help with Site-wide-search and search packages (response to 6)
Posted by Andrew Piskorski on 02/19/04 11:21 PM
Dirk, you're saying the ACES site-wide-search package is substantially better than the Oracle site-wide-search currently in OpenACS CVS, and we should port it to OpenACS 5.x? Can you give us more info on why that is, and how that situation came to be?
Collapse
8: Re: Need help with Site-wide-search and search packages (response to 7)
Posted by Dirk Gomez on 02/23/04 10:47 PM
The code in the repository was the basis for site-wide search on the ShareNet
project and I recently talked to the guy who was the lead developer on this
and his comment was: "To save time you better start from scratch".

Here's the bit that I experienced (I worked on it as well):

* Its performance with real-life amount of data was simply awful.

* It didn't work with umlauts.

* It has a lot of weird, weird code like if's that are always true, dynamic
  ddl, abstraction layers etc.

Given that no-one has worked on it for more than two years it should be even
more useless to use it. E.g. it still indexes the forums packages which has
been deprecated a long time ago.

The ACES solution is the ACS3 solution which has worked in this way or another
on many ACS-backed sites, I worked about two years with it and I find it
pretty reasonable, so I think it is sound approach to port it.