Conversion from 2.3
For the small number of 2.3 sites, these are notes dealing with the process of conversion to bedework. Following track what I did to dump the data from the production 2.3 database at RPI. These have since been modified to the state we are at about version 3.3.1. Having a copy of the 2.3.2 data from Navarre I fixed up the restore process to work.
The steps are as follows:
Dump the database as xml
The first step is to use the uwcal 2.3.2 dump process to get an xml dump of the 2.3.2 data
Edit the data
The data is divided into a number of sections. Find the <filters> section adn move it to just before the <events> section. This allows the restore process to create calendars from the 2.3.2 filter definitions.
Copy in timezones
When you unpack the restore (you can run it from bedework/dist/temp/shellscr/restoreFrom2p3px) you need to copy bedework/doc/bwtimezones.xml into the resources directory
Configure your system
You should be able to alter the names of some of the entities created during the restore by suitable changes mostky to the options.xml file.
In particular, if your native language is not English you will want to change the default names for calendars, views and probably the user and public root calendars.
The build the system and unpack the dump/restore from 2.3.2
Restore the data
cd into the dump-restore directory chmod +x bwrun ./bwrun scheam-export ./bwrun restore your-data-file --indexroot part-to-your-index
To get a working 3.3.1 system with your data the remaining steps involve you fixing up groups a bit, creating a calendar suite, views and subscriptions. This is going to be a manual process, partly because you will have your own naming. Do this in the admin client - all the following are done as a superuser.
The restore created a super group which includes all the others as members. We call this campusAdminGroups in the quickstart. if you really want anothre name you're going to have to change access rights as well. Membership of this group is what gives all the other groups access.
You can check the groups by going to "Manage admin groups"\\
The restore process subscribes you to the top level calendars. Maybe you want more subscriptiosn or to alter them.
One view per subscription and an All view are created.
In the "Manage calendars" page you can click on the calendar "public" (or whatever name you gave it and see the access rights. It should be permitted "write-content and read" to the group "campusAdminGroups". This access is inherited by all sub-calendars and folders.
Add main calendar suite
Go to "Manage Calendar Suites" and click on the add button to create a calendar suite associated with the main campus admin group.
Fill in the fields with
Name: MainCampus Group: campusAdminGroups Root calendar: /public
Add it then log out and back in.
Inthe bar near the top you should see something like:
Calendar Suite: MainCampus Logged in as: public-user Group: campusAdminGroups
If you don't something is not correct, for example, the current user is not the member of an admin group.