Default read access group for Zidestore-originating events

[Samuli Seppänen]

Hi!

Is there are way to set the default read access team for appointments
created by _Zidestore_. For example for events synced from a mobile
phone to OGo? Setting the default read access team for new appointments
created in the WebUI is easy with

  scheduler_default_readaccessteam groupname

but that doesn't seem to affect Zidestore's behavior. Have I missed some
defaults?

Samuli
--
OpenGroupware.org Users
users@...
http://mail.opengroupware.org/mailman/listinfo/users

[SebastianR]

users@... wrote:

> Hi!
>
> Is there are way to set the default read access team for appointments
> created by _Zidestore_. For example for events synced from a mobile
> phone to OGo? Setting the default read access team for new appointments
> created in the WebUI is easy with
>
>   scheduler_default_readaccessteam groupname
>
> but that doesn't seem to affect Zidestore's behavior. Have I missed some
> defaults?

I am not perfectly sure, but I think, what ever the user has configured in
the webui prefereces, will be used when uploding appointments via zidestore.

Sebastian

--
OpenGroupware.org Users
users@...
http://mail.opengroupware.org/mailman/listinfo/users

[Adam Tauno Williams-2]

> > Is there are way to set the default read access team for appointments
> > created by _Zidestore_. For example for events synced from a mobile
> > phone to OGo? Setting the default read access team for new appointments
> > created in the WebUI is easy with
> >   scheduler_default_readaccessteam groupname
> > but that doesn't seem to affect Zidestore's behavior. Have I missed some
> > defaults?
> I am not perfectly sure, but I think, what ever the user has configured in
> the webui prefereces, will be used when uploding appointments via zidestore.

I believe that is true since r1945, 2007-05-07
<http://www.whitemiceconsulting.com/node/117>

But that is write access;  I don't think there is a default for read
access,  at least not one applied by ZideStore.   If
"scheduler_default_readaccessteam" isn't applied you could open a bug
report.   ZideStore's access model is based on if you write it to a team
or personal folder.   Events created in the personal folder are personal
and events created in a team folder have access assigned to that team.
At least that is what I recall from when I tested it.  I don't know what
[if anything] the Overview folder does but (IMO) applying the default
would make sense.

I think ZideStore works this way because it descends from ZideLook and
Outlook does its folder hierarchy thing.
--
          Consonance: an Open Source .NET OpenGroupware client.
 Contact:awilliam@...   http://freshmeat.net/projects/consonance/

--
OpenGroupware.org Users
users@...
http://mail.opengroupware.org/mailman/listinfo/users

[Adam Tauno Williams-2]

> > > Is there are way to set the default read access team for appointments
> > > created by _Zidestore_. For example for events synced from a mobile
> > > phone to OGo? Setting the default read access team for new appointments
> > > created in the WebUI is easy with
> > >   scheduler_default_readaccessteam groupname
> > > but that doesn't seem to affect Zidestore's behavior. Have I missed some
> > > defaults?
> > I am not perfectly sure, but I think, what ever the user has configured in
> > the webui prefereces, will be used when uploding appointments via zidestore.
> I believe that is true since r1945, 2007-05-07
> <http://www.whitemiceconsulting.com/node/117>
> But that is write access;  I don't think there is a default for read
> access,  at least not one applied by ZideStore.   If
> "scheduler_default_readaccessteam" isn't applied you could open a bug
> report.   ZideStore's access model is based on if you write it to a team
> or personal folder.   Events created in the personal folder are personal
> and events created in a team folder have access assigned to that team.
> At least that is what I recall from when I tested it.  I don't know what
> [if anything] the Overview folder does but (IMO) applying the default
> would make sense.

Here it is in ZideStore/SoObjects/ZSAppointments/SxDavAptCreate.m -
<quote>
  /* read-access-group */

  if ((tmp = [[self appointment] pkeyOfGroupInContext:_ctx]) != nil)
    [self->changeSet setObject:tmp forKey:@"accessTeamId"];

  /* write access */

  tmp = [[[self appointment] container]
defaultWriteAccessListInContext:_ctx];
  if ([tmp isNotEmpty])
    [changeSet setObject:tmp forKey:@"writeAccessList"];
</quote>

So read access, the "accessTeamId" attribute is based solely on the
folder you write too;  probably wouldn't be to hard to fix.

--
OpenGroupware.org Users
users@...
http://mail.opengroupware.org/mailman/listinfo/users

[Samuli Seppänen]

>>> Is there are way to set the default read access team for appointments
>>> created by _Zidestore_. For example for events synced from a mobile
>>> phone to OGo? Setting the default read access team for new appointments
>>> created in the WebUI is easy with
>>>   scheduler_default_readaccessteam groupname
>>> but that doesn't seem to affect Zidestore's behavior. Have I missed some
>>> defaults?
>> I am not perfectly sure, but I think, what ever the user has configured in
>> the webui prefereces, will be used when uploding appointments via zidestore.
>
> I believe that is true since r1945, 2007-05-07
> <http://www.whitemiceconsulting.com/node/117>
>
> But that is write access;  I don't think there is a default for read
> access,  at least not one applied by ZideStore.   If
> "scheduler_default_readaccessteam" isn't applied you could open a bug
> report.   ZideStore's access model is based on if you write it to a team
> or personal folder.   Events created in the personal folder are personal
> and events created in a team folder have access assigned to that team.
> At least that is what I recall from when I tested it.  I don't know what
> [if anything] the Overview folder does but (IMO) applying the default
> would make sense.
>
> I think ZideStore works this way because it descends from ZideLook and
> Outlook does its folder hierarchy thing.

I think I'll file a bug report on this. I'll test what happens to the
permissions if I upload ICS'es to different Zidestore folders. I suppose
  uploading to a public folder will make the included events public.

Samuli
--
OpenGroupware.org Users
users@...
http://mail.opengroupware.org/mailman/listinfo/users

[Adam Tauno Williams]

On Wed, 2008-05-28 at 13:33 +0300, Samuli Seppänen wrote:

> >>> Is there are way to set the default read access team for appointments
> >>> created by _Zidestore_. For example for events synced from a mobile
> >>> phone to OGo? Setting the default read access team for new appointments
> >>> created in the WebUI is easy with
> >>>   scheduler_default_readaccessteam groupname
> >>> but that doesn't seem to affect Zidestore's behavior. Have I missed some
> >>> defaults?
> >> I am not perfectly sure, but I think, what ever the user has configured in
> >> the webui prefereces, will be used when uploding appointments via zidestore.
> > I believe that is true since r1945, 2007-05-07
> > <http://www.whitemiceconsulting.com/node/117>
> > But that is write access;  I don't think there is a default for read
> > access,  at least not one applied by ZideStore.   If
> > "scheduler_default_readaccessteam" isn't applied you could open a bug
> > report.   ZideStore's access model is based on if you write it to a team
> > or personal folder.   Events created in the personal folder are personal
> > and events created in a team folder have access assigned to that team.
> > At least that is what I recall from when I tested it.  I don't know what
> > [if anything] the Overview folder does but (IMO) applying the default
> > would make sense.
> > I think ZideStore works this way because it descends from ZideLook and
> > Outlook does its folder hierarchy thing.
> I think I'll file a bug report on this. I'll test what happens to the
> permissions if I upload ICS'es to different Zidestore folders. I suppose
>   uploading to a public folder will make the included events public.

Did you file a bug for this?

If you do please include a link to this thread
<http://mail.opengroupware.org/pipermail/users/2008-May/018919.html>

I think the good behavior would be to apply the default defined read
access when the appointment is written to the Overview folder.  I
suspect that is the folder usually used for sync of calendar events and
it doesn't represent a specific permission context (like public,
private, and Team folders do).
--
          Consonance: an Open Source .NET OpenGroupware client.
 Contact:awilliam@...   http://freshmeat.net/projects/consonance/

--
OpenGroupware.org Users
users@...
http://mail.opengroupware.org/mailman/listinfo/users

[Samuli Seppänen]

Adam Tauno Williams ha scritto:

> On Wed, 2008-05-28 at 13:33 +0300, Samuli Seppänen wrote:
>>>>> Is there are way to set the default read access team for appointments
>>>>> created by _Zidestore_. For example for events synced from a mobile
>>>>> phone to OGo? Setting the default read access team for new appointments
>>>>> created in the WebUI is easy with
>>>>>   scheduler_default_readaccessteam groupname
>>>>> but that doesn't seem to affect Zidestore's behavior. Have I missed some
>>>>> defaults?
>>>> I am not perfectly sure, but I think, what ever the user has configured in
>>>> the webui prefereces, will be used when uploding appointments via zidestore.
>>> I believe that is true since r1945, 2007-05-07
>>> <http://www.whitemiceconsulting.com/node/117>
>>> But that is write access;  I don't think there is a default for read
>>> access,  at least not one applied by ZideStore.   If
>>> "scheduler_default_readaccessteam" isn't applied you could open a bug
>>> report.   ZideStore's access model is based on if you write it to a team
>>> or personal folder.   Events created in the personal folder are personal
>>> and events created in a team folder have access assigned to that team.
>>> At least that is what I recall from when I tested it.  I don't know what
>>> [if anything] the Overview folder does but (IMO) applying the default
>>> would make sense.
>>> I think ZideStore works this way because it descends from ZideLook and
>>> Outlook does its folder hierarchy thing.
>> I think I'll file a bug report on this. I'll test what happens to the
>> permissions if I upload ICS'es to different Zidestore folders. I suppose
>>   uploading to a public folder will make the included events public.
>
> Did you file a bug for this?
>
> If you do please include a link to this thread
> <http://mail.opengroupware.org/pipermail/users/2008-May/018919.html>
>
> I think the good behavior would be to apply the default defined read
> access when the appointment is written to the Overview folder.  I
> suspect that is the folder usually used for sync of calendar events and
> it doesn't represent a specific permission context (like public,
> private, and Team folders do).

Yep, I did file a bug report. The setting that might affect this is the
"Write access" in Calendar preferences, but there's no "read access". I
tried all the defaults and calendars there are in vain.

The bug report is at

http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1979

Samuli
--
OpenGroupware.org Users
users@...
http://mail.opengroupware.org/mailman/listinfo/users

[Adam Tauno Williams]

> >>>>> Is there are way to set the default read access team for appointments
> >>>>> created by _Zidestore_. For example for events synced from a mobile
> >>>>> phone to OGo? Setting the default read access team for new appointments
> >>>>> created in the WebUI is easy with
> >>>>>   scheduler_default_readaccessteam groupname
> >>>>> but that doesn't seem to affect Zidestore's behavior. Have I missed some
> >>>>> defaults?
> >>>> I am not perfectly sure, but I think, what ever the user has configured in
> >>>> the webui prefereces, will be used when uploding appointments via zidestore.
> >>> I believe that is true since r1945, 2007-05-07
> >>> <http://www.whitemiceconsulting.com/node/117>
> >>> But that is write access;  I don't think there is a default for read
> >>> access,  at least not one applied by ZideStore.   If
> >>> "scheduler_default_readaccessteam" isn't applied you could open a bug
> >>> report.   ZideStore's access model is based on if you write it to a team
> >>> or personal folder.   Events created in the personal folder are personal
> >>> and events created in a team folder have access assigned to that team.
> >>> At least that is what I recall from when I tested it.  I don't know what
> >>> [if anything] the Overview folder does but (IMO) applying the default
> >>> would make sense.
> >>> I think ZideStore works this way because it descends from ZideLook and
> >>> Outlook does its folder hierarchy thing.
> >> I think I'll file a bug report on this. I'll test what happens to the
> >> permissions if I upload ICS'es to different Zidestore folders. I suppose
> >>   uploading to a public folder will make the included events public.
> > Did you file a bug for this?
> > If you do please include a link to this thread
> > <http://mail.opengroupware.org/pipermail/users/2008-May/018919.html>
> > I think the good behavior would be to apply the default defined read
> > access when the appointment is written to the Overview folder.  I
> > suspect that is the folder usually used for sync of calendar events and
> > it doesn't represent a specific permission context (like public,
> > private, and Team folders do).
> Yep, I did file a bug report. The setting that might affect this is the
> "Write access" in Calendar preferences, but there's no "read access". I
> tried all the defaults and calendars there are in vain.

Applied a change in r2117.  ZideStore should now apply the read access
team specified in the scheduler_default_readaccessteam default when an
appointment is created in the /Overview folder.

> The bug report is at
> http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=1979
--
          Consonance: an Open Source .NET OpenGroupware client.
 Contact:awilliam@...   http://freshmeat.net/projects/consonance/

--
OpenGroupware.org Users
users@...
http://mail.opengroupware.org/mailman/listinfo/users