Novell Cool Solutions

Calendaring Across Boundaries



By:

February 11, 2008 8:08 pm

Reads:2,684

Comments:2

Score:Unrated

Print/PDF

One of our Danish partners, and Novell Sysop, Tommy Mikkelsen sent me a link to a site over the weekend.  It spoke of a Danish effort to consolidate calendars.  It is a long standing effort to allow public sector workers to quickly share calendar information.  The estimates are that it could save up to $10 million per year if every one of Denmark’s public sector workers saved just one hour over the year when scheduling meetings.  This puts a real figure on the amount of time and money we all spend when trying to schedule meetings across company boundaries.  I experienced this pain recently trying to set up meetings with three of our partners who where coming into town (actually, it was our admin who experienced all the pain).  What this project does is link calendars in Exchange, Notes and GroupWise into a single central site.  It uses iCal and SOAP to integrate the calendars.

Tommy wrote the GroupWise connector for the project (he’s a smart cookie – I have used some of his other projects in other roles).  He didn’t mention it but I am assuming that he used the GroupWise 7 SOAP interface.  Now, my Danish is a little rusty so I can’t tell you what the project sites say but the source is available out there.

This cross boundary calendaring is a major feature of GroupWise Bonsai, which really validates the goals of the project.  Bonsai will allow users to subscribe to external iCal calendars so that they can view that calendar alongside their own in the client.  Users will also be able to publish their own personal calendars using the Calendar Publishing Host.  The Calendar Publishing Host creates an HTML version of the users’ calendar and publishes it to a website that your company hosts.  It also provides an iCal interface to the same data so that external users can subscribe to it. Finally, Bonsai will allow your users to publish their own Free/Busy information, as well as busy search any external users that publish their own Free/Busy information.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Categories: Uncategorized

2

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

2 Comments

  1. This new feature in Bonsai has been requested as an enhancement for many years. I’m so happy to see it finally make the list! I hope that Resource calendars can also be published – quite often people use resources for booking things and it’d be highly useful to be able to publish a resource’s calendar on a company’s intranet/extranet/website.

  2. By:Eric

    I will extend your question to this:
    Will your own additional calendar folders (not just primary calendar) be able to be published (hopefully multiple calendars can be published at the same time, as an option)? What about shared calendar folders and proxy account calendars that you have rights to (this covers resource calendars). For the latter question, obviously there would need to be some sort of “right” that says a user is allowed to publish.

Comment

Calendaring Across Boundaries



By:

February 11, 2008 12:00 am

Reads:3,621

Comments:0

Score:Unrated

Print/PDF

One of our Danish partners, and Novell Sysop, Tommy Mikkelsen sent me a link to a site over the weekend. It spoke of a Danish effort to consolidate calendars. It is a long standing effort to allow public sector workers to quickly share calendar information. The estimates are that it could save up to $10 million per year if every one of Denmark’s public sector workers saved just one hour over the year when scheduling meetings. This puts a real figure on the amount of time and money we all spend when trying to schedule meetings across company boundaries. I experienced this pain recently trying to set up meetings with three of our partners who where coming into town (actually, it was our admin who experienced all the pain). What this project does is link calendars in Exchange, Notes and GroupWise into a single central site. It uses iCal and SOAP to integrate the calendars.

Tommy wrote the GroupWise connector for the project (he’s a smart cookie – I have used some of his other projects in other roles). He didn’t mention it but I am assuming that he used the GroupWise 7 SOAP interface. Now, my Danish is a little rusty so I can’t tell you what the project sites say but the source is available out there.

This cross boundary calendaring is a major feature of GroupWise Bonsai, which really validates the goals of the project. Bonsai will allow users to subscribe to external iCal calendars so that they can view that calendar alongside their own in the client. Users will also be able to publish their own personal calendars using the Calendar Publishing Host. The Calendar Publishing Host creates an HTML version of the users’ calendar and publishes it to a website that your company hosts. It also provides an iCal interface to the same data so that external users can subscribe to it. Finally, Bonsai will allow your users to publish their own Free/Busy information, as well as busy search any external users that publish their own Free/Busy information.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Categories: Uncategorized

0

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS