Public Folder Calendar Problem

[Alan Jones]

Its possible that this is design thing rather than an actual bug, but
I seem to be having a problem with calendars contained in Public
Folders and Entourage. My searches of mailing lists, websites, and
newsgroups have turned up nothing so I thought that I might post and
see if anyone else has seen this.

If a user schedules an appointment on a calendar in a shared folder
and invites several people to the meeting, an Entourage user who
accepts the appointment does not receive a corresponding calendar
entry on their personal calendar. If the appointment is scheduled out
of someones personal calendar this doesn't happen. It seems limited
to Public Folders. Has anyone else seen this behavior, and if so has
a workaround or fix been developed?

 

[William Smith]

Its possible that this is design thing rather than an actual bug, but
I seem to be having a problem with calendars contained in Public
Folders and Entourage. My searches of mailing lists, websites, and
newsgroups have turned up nothing so I thought that I might post and
see if anyone else has seen this.

If a user schedules an appointment on a calendar in a shared folder
and invites several people to the meeting, an Entourage user who
accepts the appointment does not receive a corresponding calendar
entry on their personal calendar. If the appointment is scheduled out
of someones personal calendar this doesn't happen. It seems limited
to Public Folders. Has anyone else seen this behavior, and if so has
a workaround or fix been developed?

Hi Alan!

I can't say if this is a bug or by design but I'm trying to understand
why you'd do this with a calendar in public folders rather than your own.

If this is a group calendar, such as a calendar for a resource such as a
conference room, then it would make more sense to set up the resource as
a user and then the meeting organizer would invite the resource as if it
were a regular user.

If I'm missing your question please let me know. Also, please explain
what you're trying to accomplish with your method of using a public
folder calendar.

bill

 

[Alan Jones]

Hi Alan!

I can't say if this is a bug or by design but I'm trying to understand
why you'd do this with a calendar in public folders rather than your own.

If this is a group calendar, such as a calendar for a resource such as a
conference room, then it would make more sense to set up the resource as
a user and then the meeting organizer would invite the resource as if it
were a regular user.

If I'm missing your question please let me know. Also, please explain
what you're trying to accomplish with your method of using a public
folder calendar.

bill

William,

Thanks for the reply. Your assumption is correct, this is a group
calendar for scheduling a resource (a conference room in fact). I'm
basically following the methodology described at
http://www.slipstick.com/calendar/skedresource.asp under the "Public
folder (direct creation)" heading.

I know that setting up the conference rooms as mail enabled resources,
and using an event sink would be the best option, but there are a
couple of reasons not to do that. These calendars were here when I
inherited this server, and there is a great deal of data already in
them. So I'm somewhat hesitant to completely nuke the folders and
start from scratch. Additionally, we have several people here who
create appointments in these calendars that aren't actually in the
meetings, so I can't see how you would create an appointment that
would work in that scenario, unless those individuals were delegated
access to every person's calendar in the building.

Does that make the scenario any more clear?

Thanks,
Alan

 

[William Smith]

William,

Thanks for the reply. Your assumption is correct, this is a group
calendar for scheduling a resource (a conference room in fact). I'm
basically following the methodology described at
http://www.slipstick.com/calendar/skedresource.asp under the "Public
folder (direct creation)" heading.

I know that setting up the conference rooms as mail enabled resources,
and using an event sink would be the best option, but there are a
couple of reasons not to do that. These calendars were here when I
inherited this server, and there is a great deal of data already in
them. So I'm somewhat hesitant to completely nuke the folders and
start from scratch. Additionally, we have several people here who
create appointments in these calendars that aren't actually in the
meetings, so I can't see how you would create an appointment that
would work in that scenario, unless those individuals were delegated
access to every person's calendar in the building.

Does that make the scenario any more clear?

It does.

Question: Why is the old history for a resource important? Even if
you're trying to keep history of who's invited, you're not capturing who
really attended.

If you're trying to keep history the you could possibly keep the
calendar and hide it from users. Then create a new calendar and set it
up as a resource to accept meetings.

Delegates don't need access to everyone's calendars, just those who
would be creating the meetings. The scheduling feature built into
Entourage allows the appointment maker to see when folks are free and
busy. This should be all he needs.

Logically, conference rooms or other resources don't invite folks to
meetings. People do.

Hope this helps! bill

 

[Alan Jones]

It does.

Question: Why is the old history for a resource important? Even if
you're trying to keep history of who's invited, you're not capturing who
really attended.

If you're trying to keep history the you could possibly keep the
calendar and hide it from users. Then create a new calendar and set it
up as a resource to accept meetings.

Delegates don't need access to everyone's calendars, just those who
would be creating the meetings. The scheduling feature built into
Entourage allows the appointment maker to see when folks are free and
busy. This should be all he needs.

Logically, conference rooms or other resources don't invite folks to
meetings. People do.

Hope this helps! bill

Bill,

Thanks for the suggestions.

Alan