[dev] Horde Unified Search

Chuck Hagenbuch chuck at horde.org
Wed May 10 21:40:41 PDT 2006


Quoting august huber <a at pbx.org>:

> I am about to begin work on unified search for horde, and would like
> comments on my current design ideas.

Great!

> Requirements:
> * Ability to tie into 3rd party search engines: IE Google Search Appliance,
> Lucene, Datapark search
> * Flexible ACLs: Users should only see results they have access to.
> * Indexer notification and queuing of new objects

Sounds good.

> To meet these requirements I propose creating a module which exposes the
> contents and metadata of all horde objects (calendar items, notes, mail
> messages) in their raw form to the search spider, but when accessed by an
> authenticated user, they are redirected to the appropriate location in the
> associated module.

I don't really follow what you mean about access by an authenticated  
user vs. by the spider.

> The module could expose all the data via path components IE:
> /horde/search/search.php/username/modulename/objectid
> so that ACL's can easily be established in the search index via the path
> name

You have shares to deal with, also, not just usernames...

> I think most of the API functions to expose the data are already there, but
> I don't really see API calls to return an application URL for the objects .

There's some of this in the /show calls.

> Any comments or idea would be most appreciated.

I'm still not sure where you're checking permissions. It sounds like  
you want to leave that to the apps, but then what about exposing  
search results to the user that they can't see?

-chuck

-- 
"we are plastered to the windshield of the bus that is time." - Chris


More information about the dev mailing list