Return to: U of M Home
The Office of Information Technology (OIT) is continuing to test the pre-release of the editor and updating training materials. Oracle has informed us that they may be adding additional localizations to the Content Server patch, which might delay that component further. However, the component is progressing through QA and they have not found any major bugs. In an effort to get the editor available to units to start testing, OIT will be starting to install the updated editor and related patches on our DEV environment on Monday, March 3rd. The version currently available to us has been successfully installed on our virtual images and is fully supported by Oracle. Depending on internal testing and communications with Oracle, OIT will then determine when to install the editor on the TEST environment. This would occur later this week (Thursday at the earliest) and may be pushed into the week of the 10th.
From initial testing of the editor, there are a couple of things that we have found that should be noted. First, a new version of Site Studio Designer will be released with the upgrade. The updated Site Studio Designer will only be able to connect to upgraded UMContent environments. Therefore, the update is installed next to any existing versions of Site Studio Designer so that users can still use their older version of Site Studio Designer to connect to environments that have not been updated. We will post this update on the UMContent website as soon as we receive a final release from Oracle.
The second thing to note is that Site Developers will have to modify their layouts to take advantage of some of the new features of the editor. By default, the source code view and accessibility checker are not enabled. Site Developers who would like to use these features will need to modify their layouts and go into each element to enable them. The other feature that is not enabled by default is the ability to show metadata within the contributor. This option can be found in the region properties and is the option labeled "Modify Metadata". Site Developers can also set which metadata fields are available for contributors to edit.
The last thing to note is that with this update, UMContent will now be able to index the Contributor Data Files (XML) that are created by Content Contributors. This will allow UMContent users to perform full-text searching of these files.
OIT will try to update the UMContent Support site (http://1help.umn.edu/umcontent) with documentation of the changes mentioned above.