Database Schema Changes

Upgrading to uPortal 3.2 requires re-initializing the uPortal database structure. uPortal adopters may migrate their data to uPortal 3.2 through the use of the import/export tools. The remainder of this section describes places where changes to the portal's schema or default data sets may warrant hand-tuning of migrated data.

Default Categories

The uPortal 3.2 release included a reorganization of the default uPortal categories. New categories may need to be added to an existing installation to ensure all new content is properly imported. Several previously-existing categories were removed, so upgraders may also need to choose betweeen restoring those categories or assigning existing content to new categories.

The list of categories as of uPortal 3.2 is a flat (un-nested) list as follows:

Academics
Administration
Demonstration
Development
Entertainment
Information
Instructors
News
Testing
uPortal

Portlet Permissions

Publishing Workflow Permissions

uPortal 3.2 introduced new portlet publishing workflow features that allow a portlet to be moved through a series of lifecycle stages. Portlet management permissions for each lifecycle step may be delegated to a particular user or group upon any given portlet category. Upgrading institutions may wish to assign these permissions to administrative groups or users.

Publishing permissions in uPortal 3.2 are as follows:

Workflow step	uPortal Permission
Created	MANAGE_CREATED
Approved	MANAGE_APPROVED
Published	MANAGE
Expired	MANAGE_EXPIRED

New subscription permissions were similarly created to allow administrators and developers to subscribe to un-published content.

Workflow step	uPortal Permission
Created	SUBSCRIBE_CREATED
Approved	SUBSCRIBE_APPROVED
Published	SUBSCRIBE
Expired	SUBSCRIBE_EXPIRED

Targeting categories and portlets

As of uPortal 3.2, the *.* regex-based syntax for targeting all portlets was dropped in favor of the static string "ALL_CHANNELS".

The uPortal permissions implementation was also modified to allow inheritence of permissions by targets. For example, setting a permission on the target "Everyone" group will now cause that permission to cascade down to all members of the "Everyone" group. Prior to uPortal 3.2, permissions inheritence was calculated for principals, but not for targets.

Profiles, Themes, and Structures

uPortal 3.2 introduces the concept of an functional name ("fname") on user profiles. This new field allows the portal to properly associate multiple profiles with a single user without relying on hard-coded profile IDs. Profile IDs should now be globally unique rather than unique per user. uPortal's import/export scripts are designed to assign a default fname to profiles exported from uPortal versions prior to 3.2.

uPortal 3.2 also introduces new themes, structures, and default profiles to enable mobile functionality. Upgrading institutions should ensure that these new resources are created while data is migrated from prior versions.