Michael Wechner wrote:

Andrew Golightly wrote:

On a related note...

When I edit a document and click 'save' I always get this msg:

"message: index taotest-authoring doesn't exist"

The document is always saved and updated. But it looks like lucene is having trouble indexing it..



this is a bug and I promised to fix it soon ;-)

Hey Michael. We have some colleagues here starting to add content, so until the bug is fixed, could you please tell us how to disable the indexing? thanks! A



My publication config and data is external to my build directory. The error only seems to come up in this case. I.e. when the publication is buried within Lenya, everything seems to work ok. In fact I've answered my own question re indexing now :) Internal searching works fine when my publication is within lenya.

So it looks like this is a bug?



sounds like a bug as well. Will try to fix this as well, because it's really annoying indeed :-)

Michi


A

Andrew Golightly wrote:

Doug Chestnut wrote:



Andrew Golightly wrote:

Hi guys,

A few questions on searching/indexing..

1) In lenya1.2.x there was a search script in tools/bin called index-publication.sh That script seems to have moved in lenya 1.4. Where did it go?




There is an index usecase now. It is in the Lucene module. It is currently called as an "exit usecase" for other usecases (edit, publish, etc...). There has been talk of changing this to use some sort of trigger mechanism so as to untie the Lucene modules from the other modules/and core usecases. There are two indexes, one for the authoring area and one for the live area.




So how do I actually index my documents now? Is there a way to manually do this? I've had a look at the default publication and copied in lucene_index.xconf, and the config/search and config/cocoon-xconf directories. Are they supposed to automatically index themselves now?



2) I was reading this posting (http://article.gmane.org/gmane.comp.cms.lenya.devel/15013/) and was wondering whether the external/google search is implemented or a todo? It seems to be a todo from testing it..




external searches work with opensearch. I believe that the "external" search function in 1.4 is linked to a static sample opensearch document. This really needs some work. Currently you have to edit the lucene modules sitemap to specify an external opensearch source.




Has anybody done this? To say, specify google as the external source?



3) I was reading Solproviders notes on searching in Lenya and their own impl version (http://solprovider.com/lenya/searchpurpose). The thing we're particularly interested in is: "Remove "Members' Only" documents if not authorized." Is this implemented in lenya 1.4? As the documentation on the implementation they provide seem to talk only about improving lenya1.2.x




Nope, not yet. I have thought about this a little. I guess that you could do this two ways: -Index the acls with the docs in the lucene index. This would be a real pain to maintain. -evaluate each search result before display, This might be a little too much processing. It wouldn't be too bad I guess to evaluate the "view" role of results set at a time (build a set of X docs that the current user has the role of "view" for). This would make your total hits an estimate, and I guess would throw your rank off.


thanks!
Andrew

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to