[OGo-Users] Default calendar attributes (Participants, Resources, Read, Write)

[Adam Tauno Williams]

> We created a team "montage" and a resource "montage", we also want to
> the team montage to only see the items which apply to the team montage
> (so not the items which apply also to the user private, or team "all
> intranet", so not the other items the user has access to).

There is no user "private",  those are just objects restricted to the =20
user by permssions.  I think the drill down view of the calendar will =20
provide this.

> The only way we figured out this can be done is by tagging each calendar
> item "montage" with the resource montage and use this resource as a
> view.
> You now have two options: "Resource: Montage" and "Resource Category:
> Montage". In the later it is not possible to create new items, in the
> first this is possible.

Of course;  you can create events tied to a category,  the category is =20
only an organizational assist.

> If we now create a new calendar item we get the following default
> settings:
> Search Participants: needs to be filled in (two steps to get team
> montage)
> Search Resources: montage (has the right setting)
> Read access: All Intranet (user has to select montage from the drop
> down)
> Write access: Montage (this has been set in the user prefs)
> So the user is forced to execute three steps, for settings he already
> wants to have (90% ahead of the time).

If you use the drill down calendar view the participants will default =20
to the participants viewed (your montage team).  I don't understand =20
the way in which you are using the resource.

> Next to this the user still has to be member of the "All Intranet" group
> because he also needs to access all general calendar items.

Yes.

> Is there a way to organize this a bit more elegant? Our users are
> complaining they have to fill in too many unnecessary (at least in their
> experience) values.

Try the drill down calendar view.

> It all boils down to user defined default values, better would be also
> resource defined default values and/or team defined default values.
> This means default values change depending on the view.

And they do.

> The view defines
> with which work group the user is working and therefore the access
> requirement for the collaboration.

Default write access for a user is defined in their preferences.