-----John Haxby <[EMAIL PROTECTED]> wrote: -----
>To: [email protected] >From: John Haxby <[EMAIL PROTECTED]> >Date: 24.01.2006 20:52 >Subject: Re: access rights > >I'd suggest using a QueryFilter. > >What happens when the access rights for a document or a collection of > >documents change? How do you deal with new users? I'm asking >because I'm looking at the same problem but rather than attempting to > >keep the access rights in the index consistent with the access rights >in >the original store, I'm looking at using a QueryFilter that checks >the >original document for access. It's slow, but it can be cached. In my case the identity information is structured, rather than plain. Users are organized in the organisation tree and can belong to groups. Access rights (AR) are typically set for (sub)organisation or group, not for individuals (identity store is directory server). When the AR for documents are specified with respect to organisation or group, they do not tend to change. The source of the documents is a CMS. There is a publication handler, which ensures that new, or modified documents get into index as soon as possible. AR are stored in the documents. So, in the most cases the AR changes are reflected almost immediately. In the few others, the changes are reflected next day. The constraint is acceptable for the company. However, the main issue is performance. There are defined string timing requirements for displaying the search results. >This >question probably belongs on java-user though. Especially paragraph above ;-). I wrote to this list, because I was playing with the idea of excluding certain fields from score computation algorithm. I am not sure if the excluding can be done when the document is inserted into index, or if there is a possibility to exclude the fields (somehow) during the search. Perhaps, the idea of the fields exclusion is complete nonsense in respect to the lucene implementation. If so, I was hopping to get known. I already looked into sources and get lost a little, so I was hopping that someone will suggest where to look. Maros. > >jch > >Maros Ivanco wrote: > >>Hi, >> >> I try to implement acces rights mechanism on the top of the lucene. >My >>situation looks like this: Indexed documents have associated access >rights >>information. When I construct the query, I append a part, which >matches >>actual user identity with access rights in the documents. This way >the user >>gets only the documents s/he can really access, and the number of >hits is >>really the number of documents s/he can potentionally access. The >approach >>works (it respects access rights), but the access rights (AR) query >part >>also affects the score of the documents. I tried two approaches to >avoid >>the effect of AR query part. First, I tried to set boost factor of >the AR >>fields during the document indexation to zero. This way I was unable >to get >>any results. Next, I set boost factor of the AR fields to small >number >>(0.001). This way I get the results but the computed score is really >small >>(less then 1%) for the first document in the results. >>So, is there any possibility to effectivelly exclude certain fields >from >>score computation? >>Any idea regarding the access rights issue, suggestion for better >approach, >>... is welcome. >> >>Maros. >> >>P.S. >>I found this post on the user list: >>http://www.gossamer-threads.com/lists/lucene/java-user/14973?do=post >_view_threaded >> >>My approach is the number 3 in the post, but unfortunately no reply >deal >>with it. >> >> >>-------------------------------------------------------------------- >- >>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]
