Hello, Richard, thank you very much for your answer, some things seem like I supposed. Well, actually thats not too bad at all. The points you mentioned won't be easy to solve or workaround, but then this just needs to be done for my case. As the search is supposed to be one of the most important feature of our frontend users, it is legitimate to put a lot of work into it.
The unwanted content is a good point! Matteo, did you use Google Mini with restricted pages and so on, or in the internet, where everybody is allowed to see everything? I don't know if it is possible and maybe I'm wrong, but I can't imagine that google mini is able to index pages with respect to the magnolia acls. Rakesh, is the website intra- or internet? So for now, I maybe use the OpenMind Criteria Module (Thanks Federico, a thousand times faster sounds great ;)), and base the search on that. Reagrds, Florian On Fri, Feb 25, 2011 at 4:31 PM, Unger, Richard <[email protected]>wrote: > Hello Florian! > > > As far as I am concerned, the search is still a bit of a weak point in > magnolia. On the other hand, the requirements for search are very hard to > generalize, each site / organization will have its own ideas of how search > should work for their content. > > > > Basically, the magnolia-search leverages Jackrabbit’s built-in indexing. On > the one hand this is good, since all content is indexed and searchable, on > the other hand it poses some problems. > > > > The search works very well for the Backend (AdminCentral and Author > instance) where one can generally assume that editors simply want to find > some content for editing purposes, and are happy to search “everything”. > > > For the front-end (end user search), both the presentation of the results > and the search itself pose some problems: > > > > 1. How to deal with “unwanted” content – you don’t want to show the > content from hidden or protected areas in the search results, but the index > contains everything! How to be sure to exclude certain results is a bit of a > problem. Purists would say that things that should not be found, should not > be in the index. > > 2. How to deal with multiple workspaces (see older threads in this > mailing list)? – Basically, each workspaces (website, dms, data) has its own > index, and there is no straightforward way to combine results from different > searches, since their search-scores are not normalized to a common scale. > > 3. How to deal with HTML character entities (see older threads in > this mailing list)? – As an example, ä (for ä) is inserted > automatically by fckeditor, meaning a search for “Änderung” will not find > documents where this word was input via fckeditor, since it is stored > internally as “Änderung” and not converted automatically on indexing or > when searching. > > 4. It is also not clear how to combine Full-text search with other > forms of searching (for example, by category using the categorization > module). > > > > So it seems to me that magnolia comes with a good “starting point”, but you > will need to do a bit of work to get the search adapted to your specific > needs in each case. > > > > Regards from Vienna, > > > Richard > > > > > > > > *Von:* [email protected] [mailto: > [email protected]] *Im Auftrag von *Florian Fuchs > *Gesendet:* Freitag, 25. Februar 2011 13:18 > *An:* Magnolia User-List > *Betreff:* [magnolia-user] Experiences with Search functionality > > > > Hi List, > > I wanted to ask you about your experiences regarding the integrated search > functionality of magnolia. > > We are rebuilding our intranet on the base of magnolia, so we need a very > good search engine. (searching websites and documents as well) > (Unfortunately the simplesearchtag only searches through the Website > Repository.) > > What are your solutions? Do you all use google custom search for searching? > Is there an advanced-search-module? > > Or did really everyone reinvent a full blown search service? > > The requirements of a search engine are not that advanced, in fact I think > of searching through Website and Documents, using pagination, and showing a > result snippet.. > > I'm looking forward to your answers. > > Thanks, > Regards, > Florian > > > ------------------------------ > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
