[Cosmo-dev] Multiply Calendars ?
bcm at osafoundation.org
Tue Jul 25 14:30:01 PDT 2006
On 7/25/06, Adam Procter <Adam.Procter at luton.ac.uk> wrote:
> I have set up my cosmo with one user (me).
> I am using iCal to publish my calendars and people subscribing are
> using iCal.
so to be clear, using the cosmo repository browser, you can see two
resources inside your home collection, one named "Holiday.ics" and the
other named "Moonlighting.ics", right?
> I have two calendars that I wish to only show some people one and
> some the other.
> I can publish for example a Holidays calendar into the default folder
> (type Calendar) and I can assign a ticket for the Calendar folder and
> people can subscribe to the Holidays cal
hang on now. what exactly do you mean by "type Calendar" and "Calendar folder"?
when iCal publishes a calendar, the resulting resource in cosmo is not
a calendar collection. it is not labeled as "Calendar" in the
repository browser, and it does not have any contents. it's just a
if you are seeing a resource of type "Calendar" in your home
collection, you must have created this resource with some client other
than iCal. did you perhaps log into scooby? scooby autocreates a
calendar collection named "Scooby" the first time you log in.
> If I then publish another cal say Moonlighting calendar to the
> default folder (type Calendar) it will merge with the Holidays cal on
> the people subscribing macs.
> Because they are using the same ticket / same location
again, not sure what you're actually saying here. what do you mean by
"people subscribing macs"? what do you mean by merge? are these people
using iCal to subscribe to your calendars? what exact urls (you can
replace the actual tickets with xxxxx or whatever) are they
> Yet if I go into each .ics file and give it a ticket of its own, this
> works fine , until I make updates to the calendar as this wipes the
> ticket and I have to give it a new one which is no good without
> telling all the subscribers to change there URL.
if you publish an iCal calendar to a server, then you use another
client to change that calendar on the server, iCal will actually
delete the calendar from the server and re-upload its old copy back to
the server. this would cause the behavior you're describing.
iCal only lets the person who publishes the calendar make changes to
it. likewise, it does not allow you to make any changes to calendars
to which you have subscribed. i fully expect iCal will get better over
> I have tried to put each cal in a folder but this does not work as
> the main folder appears to be a special type (Calendar) where as any
> new folders I create the type is just Folder and iCal will not accept
> a Subscribe URL with ticket to these folders.
this is sort of the heart of the matter. iCal does not speak the
caldav protocol, which is what the "Calendar" collections are used
for. iCal has its own thing that it calls "webcal", where it puts up
your entire calendar as a single resource named "whatever.ics". that
resource will be labeled as a "File" in cosmo, not "Calendar".
> Can anyone point me in the right direction?
have a look at <http://wiki.osafoundation.org/bin/view/Documentation/CosmoWithiCal>
for a little more information on how to use iCal with cosmo.
More information about the cosmo-dev