[OGo-Developer] task::qsearch & acccess

[Helge Hess]

On 16.11.2007, at 20:36, Adam Tauno Williams wrote:
> I've created a "job::qsearch" command like the "person::qsearch" and
> "enterprise::qsearch"; as LSQualifierSearchTaskCommand descended from
> LSQualifierSearchCommand.  That was actually pretty easy. :)      
> This is
> really useful to us since we use the task application as a knowledge
> base.  The search capabilty regarding tasks in the mainline is really
> primitive.
...
> (A) Is this something that can be committed to the mainline?

Sure why not, doesn't hurt anything else?

> (B) Of course jobs provide no access control, ergo...

Hm ...

> <0x0x8456c7c[SkyAccessManager]> found no access handler for entity Job
> GID <0x0x84b4b0c[EOKeyGlobalID]: Job 10502400>: {}

Thats just a warning. I thought I removed in in HEAD, but apparently  
not.

> ... in the logs.  And this presents a problem as using just the
> todo/delegated/archived lists a user can't weasel into someone else's
> tasks.

Hm, yes, probably.

> If (A) then is creating a OGoTaskAccessHandler object for use by the
> OGoAccessManager in the Tasks bundle acceptable?

Sure.

>   - Access provided if user is the creator or executor (incl. executor
> via team)
>   - Access provided if task is assigned to a project to which the user
> has "r" access.

Sounds good. We sometimes (events?) also do 'l' access which just  
means that the user can see the thing but has no full access.

> Currently task::qsearch only searches the task's core information.   
> Down
> the line I want to search annotations,

Job annotations are in the database or in the FS?

> and possibly properties,

Si.


Sounds good!

Thanks,
   Helge
-- 
Helge Hess
http://www.helgehess.eu/