Add and Configure Additional Calendar Suites

Introduction

The quickstart includes the Calendar Suite MainCal.  You can think of a Calendar Suite as a window through which you manage and view your public events.   For many sites, the MainCal Calendar Suite is sufficient.  It's a full-sized window through which all public events are managed and viewed.   There are three likely motivations for adding another Calendar Suite:

1. You'd like to provide a smaller window for managing certain events.   This is usually done to restrict access to certain event tags (topical areas) to specific administrators.  As you'll see below, you can set up a Calendar Suite for this purpose by using the administrative client.
2. You'd like to provide a smaller window for managing and viewing certain events, and/or you'd like to create a second web site with an independent look and feel.  This is usually done to create an independent departmental instance of a fully-functioning Bedework calendar site.  As you'll see below, creating a fully-independent departmental site involves configuration work in the administrative client and making configuration changes to the Bedework system itself.  The Bedework system configuration changes involve defining a new web client to be built and deployed.

Add a New Calendar Suite

A Calendar Suite that is to have its own web context (e.g. http://localhost:8080/mydept ) must be built, and the resulting .war will be packaged up and deployed alongside the other suites.   If you wish to use calendar suites solely for limiting access to topical areas, you do not need to build it and may skip directly to Configure a Bedework Calendar Suite.

Build a Bedework Calendar Suite

1. Follow the instructions for setting up your build environment.
2. Add calendar suites to deploy.properties using the quickstart's example of SoEDept (the demo departmental public web client). See Update deploy configuration.
3. Copy a template directory for use with the new calendar suite from an existing one, and name it with the name given the calendar suite. E.g. copy bedework/deployment/webpublic/webapp/resources/demoskins/MainCampus as ....demoskins/MyDept
4. Build Bedework

Configure a Bedework Calendar Suite

You must now define the Calendar Suite in the admin client and associate it with an administrative group.

1. Create an admin group from which to hang the Calendar Suite:
   1. Log into the Bedework Admin Client as a superuser.
   2. Select the Users tab.
   3. Select Manage admin groups
   4. Click the button Add a new group
   5. Set the group's properties:
      1. Name: calsuite-MyDept (note: it is recommended practice to name Calendar Suite groups in this way, prepending them with "calsuite-" or a similar signifier so that they are easy to distinguish from other groups.  Furthermore, you should only add users to this topmost group who should be granted Calendar Suite Owner access.  Such users can manipulate the calendar suite itself.)
      2. Description: provide a reasonable description for the group, e.g. "calendar suite for MyDept"
      3. Group owner: a userid, probably of the main contact point for the group; this field is only informational
      4. Events owner: agrp_CalSuite-MyDept (note: it is recommended practice to make the events owner the same as the Name prepended with "agrp" or a similar signifier to associate the owner with the group. The "events owner" is a system user: the "agrp_" prefix distinguishes this user from a real user - one associated with an actual person. The calendar suite's preferences will be attached to this user.)
2. Add the new group to “campusAdminGroups” so that proper access rights are inherited down the group hierarchy.
   1. Select the Users tab.
   2. Select Manage admin groups
   3. Select membership for campusAdminGroups and add the new group to it.
3.  Add the calendar suite:
   1. Select the System tab.
   2. Select Manage Calendar Suites
   3. Click the button Add Calendar Suite
4. Set the Calendar Suite's properties:
   1. Name: this is the calendar suite name you defined in myconfig.properties, e.g. if you defined org.bedework.app.MyDept.cal.suite=MyDept, use "MyDept".
   2. Group: this is the name of the group you defined in step 1, e.g. "CalSuite-MyDept"
   3. Root calendar: this will almost always be "/public", the root of the public calendar tree