November 24, 2005

1
November 24, 2005 JA-SIG UK, Edinburgh
CMS for websites portals - Luminis Documentum
Presented by David Simpson, The University of
Nottingham
2
Introduction

• Highlighting the key issues in implementing CMS
  across a university.
• A practical guide to the challenges of an
  enterprise wide implementation
• How Luminis CMS fits within the Documentum
  product family

3
Agenda

• Background
• Benefits of a CMS solution
• The challenges
• The key steps to success

4
Benefits of a CMS solution

• Ease of use for editors In context editing
• Concentrate on content not technology
• Ensure overall quality and consistency of layout
  and navigation
• Ensure consistent branding

5
Benefits of a CMS solution

• Ensure Accessibility
• Introduce formal editorial practices - Workflow
• Maximising database driven content
• Schools individuality - retained via custom
  designed look and feel for each site
• Standardised navigational structure for all
  websites
• Prefabricated websites - merely awaiting content
• Default pages templates predefined
• Optional pages available within the model website
  structure

6
Design Example 1
7
Design Example 2
8
Design Example 3
9
Design Example 4
10
Header - School and Corporate ID
11
Global Navigation and Function bar
12
Section Navigation
13
Relational Navigation
14
Content Area
15
In-Context Editing
16
Prefabricated websites
Merely awaiting content
17
(No Transcript)
18
Guidance for Schools

• Work with Web Team to Develop Visual ID
• Identify Site Manager and Key Contacts
• Identify Content requirements with reference to
  the model needs and resources
• Develop content and enter via Content Collection
  Tool
• Identify Content Editors and Content Managers
• Process anywhere between 3-6 months

19
Documentum Luminis CMS
Vendor
EMC Documentum Sungard SCT
Content Server (meta data file system)
20
Luminis CMS
Content Server
21
LCMS What you get

• A CMS product based on the leading ECM technology
• Fully functioning EMC Documentum Content Server
• Versioning
• Workflow
• Lifecycles
• SCT Site Studio
• Documentum Administrator
• Support from Sungard SCT
• More functionality with each version increment!

22
LCMS What you dont get

• Publishing more than 1 version of content at any
  one time
• Documentum licensed as an ECM solution
• Direct access to Documentum support
• Support is via Sungard SCT
• Documentum Webtop/Desktop client

23
LCMS Portal Integration

• Automated Luminis Channel Creation (ALCC)
• Publishing HTML content to a portal channel from
  within LCMS
• Assign roles etc. to LCMS channels in the usual
  uPortal manner - but from within LCMS.
• Inbox channel with SSO to LCMS
• Shows outstanding tasks- workflow etc.
• Currently, no support for Documentum portlets
• Maybe with Luminis 4 JSR168 compliance - next
  year?
• Many off the shelf Documentum portlet are
  available
• Currently, no integration with Documentum Portlet
  Builder
• Maybe with Luminis 4 JSR168 compliance - next
  year?

24
Portal Integration at Nottingham

• ALCC - Single items of content published as
  channels
• Better to bundle micro-sites as portal channels
• Awaiting more advanced functionality
• Integration with Documentum Portlet Builder?
• Inbox channel with SSO to LCMS
• Implementation soon

25
Intranet Policy

• Move external facing websites under CMS first
• Consider migrating intranets later
• Much intranet content is now within the Portal
• Module information
• SSO to VLEs
• Exam timetables
• Reading lists
• Etc.
• The Portal is the intranet for smaller schools

26
Questions Answers

?
27
Thank You!

• David Simpson
• david.simpson_at_nottingham.ac.uk