On 21/10/2009 5:26:01 AM, "Matteo Pelucco" <[email protected]> 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: <[email protected]> ----------------------------------------------------------------
