Advanced search

[Rakesh Vidyadharan]

AFAIK JackRabbit does not expose direct Lucene querying.  Does Magnolia allow for advanced search (boolean, wild card etc)?  If not, how do users typically handle advanced search requirements?  Google appliance or repurposed lucene query parser or some other techniques?

Thanks in advance for all tips.
Rakesh

---

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

[Rakesh Vidyadharan]

I see that there is  a cmsu:simplesearch tag that seems to be along the lines of what I need.  I will use that as a base and see what else I need to do.  Any ideas on a “unified” search across all (or at least some selected) workspaces, returning results sorted by relevance across workspaces?

Rakesh


On 20/10/2009 10:46:03 AM, "Rakesh Vidyadharan" <rakeshv@...> wrote:

AFAIK JackRabbit does not expose direct Lucene querying.  Does Magnolia allow for advanced search (boolean, wild card etc)?  If not, how do users typically handle advanced search requirements?  Google appliance or repurposed lucene query parser or some other techniques?

Thanks in advance for all tips.
Rakesh

---

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

---

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

[Jan Haderka-2]

On Tue, 2009-10-20 at 22:02 -0500, Rakesh Vidyadharan wrote:
> I see that there is  a cmsu:simplesearch tag that seems to be along
> the lines of what I need.  I will use that as a base and see what else
> I need to do.  Any ideas on a “unified” search across all (or at least
> some selected) workspaces, returning results sorted by relevance
> across workspaces?

Writing tag similar to the cmsu:simplesearch that would execute multiple
queries (one per workspace) and combine the results?

The problem is that out of the website workspace, the content is usually
not directly displayed so even if you get a hit, you have to somehow
device a connection between the piece of content that generated a hit
and the web page (content in the website workspace) as part of which
such a hit should be displayed ... and this will be different from
workspace to workspace or even from content type to content type in case
of data module. Hence you as a designer of the site and the content have
to make that leap and write it yourself.
Should you be able to come up with some general solution to the issue I
believe others would be interested in seeing it as well. ;)

Cheers,
Jan

>
> Rakesh
>
>
> On 20/10/2009 10:46:03 AM, "Rakesh Vidyadharan" <rakeshv@...>
> wrote:
>
>         AFAIK JackRabbit does not expose direct Lucene querying.  Does
>         Magnolia allow for advanced search (boolean, wild card etc)?
>          If not, how do users typically handle advanced search
>         requirements?  Google appliance or repurposed lucene query
>         parser or some other techniques?
>        
>         Thanks in advance for all tips.
>         Rakesh
>        
>        
>         ______________________________________________________________
>         ----------------------------------------------------------------
>         For list details see
>         http://www.magnolia-cms.com/home/community/mailing-lists.html
>         To unsubscribe, E-mail to:
>         <user-list-unsubscribe@...>
>         ----------------------------------------------------------------
>        
>
>
>
> ______________________________________________________________________
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

[Matteo Pelucco]

Jan Haderka ha scritto:

> The problem is that out of the website workspace, the content is usually
> not directly displayed so even if you get a hit, you have to somehow
> device a connection between the piece of content that generated a hit
> and the web page (content in the website workspace) as part of which
> such a hit should be displayed ...

My question is:  "why" is so necessary to query other workspaces?
I think that one solution can be to integrate in Magnolia (as a
separated module) something that thinks like Google: we are in a world
of pages: no matter where the "source content" is, we can try to index
the aggregation state of content.

Why not considering SOLR?
* http://lucene.apache.org/solr/

If a content from a data module is displayed in a website page, it
should be caught by solr indexing.

It is just a point of view...

Matteo



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

[Rakesh Vidyadharan]

On 21/10/2009 5:26:01 AM, "Matteo Pelucco" <matteo.pelucco@...> wrote:

My question is:  "why" is so necessary to query other workspaces?
I think that one solution can be to integrate in Magnolia (as a
separated module) something that thinks like Google: we are in a world
of pages: no matter where the "source content" is, we can try to index
the aggregation state of content.

Why not considering SOLR?
* http://lucene.apache.org/solr/

If a content from a data module is displayed in a website page, it
should be caught by solr indexing.

It is just a point of view...

Matteo

Yes, solr is an option.  The reason we do not have Magnolia styles pages for a lot of our content is that these are primarily data components.  We have about 20K books and 15K authors and about 5K of other related data to display, and we do not maintain each of them as a Magnolia page, but as data nodes.  We could of course just add the data to the website workspace instead of maintaining our own books workspace, but I did not want to create any confusion among the content editors if they see all these nodes when you log on to the admin interface (that is assuming that the admin interface lists non page/paragraph type data in the website tab).

There are JSP’s at present that displays the specified author/book etc. and there is also a complete book index page that a crawler can index.  Our current site uses a google appliance, so we already have that in house.

Rakesh

---

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

[Matteo Pelucco]

Rakesh Vidyadharan ha scritto:

> The reason we do not have Magnolia styles pages
> for a lot of our content is that these are primarily data components.
>  We have about 20K books and 15K authors and about 5K of other related
> data to display, and we do not maintain each of them as a Magnolia page,
> but as data nodes.  

Ok, it is reasonable.
In this case, because books / authors is one of the "core contents" of
your webapp, I can think that the most convenient way to have search is
to develope a custom search. But in this case you will have to manage
also the "back reference" to real web pages, your JSPs..

M.


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------