Upgrade (2.7)

SAK-13584 - Getting issue details... STATUS , SAK-16554 - Getting issue details... STATUS : Sakai 2.6 improvements to the Message API require that implementers upgrading from a pre-2.6 version of Sakai run both the 2.6.0 conversion scripts and a second mailarchive-runconversion.sh script that can be found in the mailarchive module in order to update your existing mail archive data to take advantage of the 2.6 Email Archive performance improvements.

-- SAK-13584 Further Improve the Performance of the Email Archive and Message API. Note you have to run a bash conversion script on your old mail archive data for it to
-- appear in the new mail archive. The script is in the source as mailarchive-runconversion.sh. Please see the SAK for more information on this script or SAK-16554 for
-- updates to this script.
	  	 
	  	 CREATE INDEX IE_MAILARC_SUBJECT ON MAILARCHIVE_MESSAGE
 	  	 (
 	  	        SUBJECT                   ASC
 	  	 );
	  	 ALTER TABLE MAILARCHIVE_MESSAGE ADD COLUMN (
 	  	        SUBJECT           VARCHAR (255) NULL,
	  	        BODY              LONGTEXT NULL
 	  	 );

This conversion was a part of the post-2.4 assignments branch so those migrating from a version already running this can disregard this step.

SAK-11821 - Getting issue details... STATUS : The assignment service previously permitted the creation of duplicate submission objects (i.e. two or more submissions for the same student and assignment). While the UI should prevent this from happening, at various stages in the evolution of the Assignments code, bugs, race conditions or other failures have led to duplicate objects being created. This conversion seeks to reconcile those duplicates and add database constraints to prevent this is the future.

In summary, the conversion script is necessary to

1. Remove existing duplicate submission records, if any
2. Prevent future submission duplicates by applying unique constraint on the ASSIGNMENT_SUBMISSION table
3. Improve performance of the Assignment tool

The conversion script does the following to the existing ASSIGNMENT_SUBMISSION table in Sakai database:

1. read in all tuples as AssignmentSubmission object, parse out data such as submitter_id, submit_time, submitted, and graded, and stores those attributes as separate columns in the ASSIGNMENT_SUBMISSION table;
2. Runs though the table, combine and remove submission duplicates (tuples with same "context" and "submitter_id" combination);
3. apply the unique constraint of "context" + "submitter_id" to ASSIGNMENT_SUBMISSION table.

There is a README file with detailed instructions on this process at https://source.sakaiproject.org/svn/assignment/tags/sakai_2-7-0.

SAK-6545 - Getting issue details... STATUS : This property controls page order and visibility in the Preferences tool. The property takes comma-separated list of values identifying the pages (and toolbar actions) to display. Available pages are Notifications, Customize Tabs, Time Zone and Language. Below is an example of prefences.pages setting:

preference.pages=prefs_tab_title, prefs_noti_title, prefs_timezone_title, prefs_lang_title

The order of values in the comma-separated list determines page order and also the order of actions in the toolbar. If a value is missing, that page's action will not appear in the toolbar and the page will not be reachable via the UI. If the preference.pages property is not set, page order will be the (current) default.

If you remove

enable.privacy.status = true

you can achieve a similar effect by defining preferences.pages as follows:

preference.pages=prefs_tab_title, prefs_noti_title, prefs_timezone_title, prefs_lang_title, prefs_privacy_title

SAK-13403 - Getting issue details... STATUS : The properties associated with the WebDAV authentication cache have changed. In Sakai 2.5.0 and earlier the following properties were used:

maximumSize@org.sakaiproject.user.impl.AuthenticationCache
timeoutMs@org.sakaiproject.user.impl.AuthenticationCache
failureThrottleTimeoutMs@org.sakaiproject.user.impl.AuthenticationCache

These settings have been replaced as of Sakai 2.5.2 with:

maxElementsInMemory@org.sakaiproject.user.api.AuthenticationManager.cache
timeToLive@org.sakaiproject.user.api.AuthenticationManager.cache

SAK-10762 - Getting issue details... STATUS : in Worksite Setup/Site Info the names of properties associated with the ability to add participants via email address have changed:

OSP was turned off by default in Sakai 10 and removed entirely in Sakai 11.

SAK-13205 - Getting issue details... STATUS : if you are upgrading from a pre-2.5.0 version of Sakai, then you need to force conversion of the OSP permissions by setting osp.upgrade25=true in your sakai.properties file. (See also discussion.)

Commencing with Sakai 2.5, Sakai packaged distributions, tags or maintenance branches no longer include the Discussion tool. It has been retired and removed from the release, since there was no longer an active project team supporting the tool nor actively used by production institutions. feedback The Forums tool provides a viable alternative.

If you are upgrading and previously used the Discussion tool, you have two options:

1. Continue using Discussion. A 2.5-compatible version of the Discussion tool is available in Contrib. You can build it and add it to your Sakai instance. No one has committed to supporting this version of the tool though, and you should not rely on it remaining available for future Sakai releases.
2. Migrate Discussion content to Forums. A utility for converting Discussion tool content to Forums tool content is available in Contrib. See the README.TXT file for more information.