One CMS to rule them all?

1

• One CMS to rule them all?
• Sue Steele
• Manager ITS Web Centre

2
Utilising a Content Management System

• Choosing an appropriate model for your business
• Exploring ways to simplify content migration
• Realising how your CMS can impact on user
  experience
• Getting your CMS to be fully accessible
• Brief case study

3
Utilising a Content Management System

• Choosing an appropriate model for your business
• Exploring ways to simplify content migration
• Realising how your CMS can impact on user
  experience
• Getting your CMS to be fully accessible
• Brief case study

4
Lets pick a CMS

• A CMS should produce web sites that align with
  organisational goals
• This should be easy
• Develop your web sites goals
• Based on site goals, decide the functionality you
  require from a CMS
• Evaluate available CMS and choose the best fit

5
Lets pick a CMS

• CMS come in all shapes and sizes
• Some are open source, some cost a great deal of
  
• Some publish stand-alone sites, some are tightly
  integrated with the published web site
• Some we dont even think of as CMS at first

6
(No Transcript)
7
(No Transcript)
8
(No Transcript)
9
(No Transcript)
10
(No Transcript)
11
But

• Not all web sites have the same goals and needs
• Intranets may have very different goals compared
  to public sites
• The CMS that delivers on one may struggle to
  deliver on the other if the goals are vastly
  different

12
Utilising a Content Management System

• Choosing an appropriate model for your business
• Exploring ways to simplify content migration
• Realising how your CMS can impact on user
  experience
• Getting your CMS to be fully accessible
• Brief case study

13
Content migration

• The simplest way of all is to start from the
  beginning
• Clean slate
• Opportunity to review site goals and architecture
• Every piece of content is reviewed before
  migration
• We always recommend this, it is sometimes done

14
(No Transcript)
15
(No Transcript)
16
Can automate a migration

• Needs considerable preparation
• Must be tailored for each site migrated
• Can be done for inconsistent quality content
• Ideally still requires a human to view and
  approve migrated content
• New site and old site have same structure

17
Automated conversion

• Clean up content
• non-compliant file names
• non-standard HTML code
• orphaned files
• empty directories
• charset
• XHTML 1.0
• abbreviations and acronyms
• Convert to CMS templates
• Import converted content into CMS
• Review content and publish

18
pstagg ./html2cms-cleaner /web/test/ Back-up the
directory (Y/N)? y Backing-up '/web/test' --gt '/w
eb/test-cleaner-bak'. File/folder expunging
started... File/folder expunging
completed! File/folder name cleaning
started... File/folder name cleaning
completed! File laundering started................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
..................................................
.................. File laundering
completed! Expunging orphaned files
started... Expunging orphaned files
completed! Expunging empty directories
started... Expunging empty directories
completed! Finding local broken links
started... Finding local broken links
completed! File/folder flagging
started... File/folder flagging
completed! Finalising reports started... Finalisin
g reports completed! Done Dusted!!! pstaggs
Total Files Before 13491 Total Folders Before
734 Total Html Files Before 5166 Total Files
After 3865 Total Folders After 416 Total Html
Files After 1583 Orphaned Files
9242 Orphaned Exceptions 24 Renamed Files
7839 Flagged Files 1091 Expunged Files
9404 Expunged Folders 318 Updated Links
4814 External Links 2570 Broken Links 617
19
Best of both worlds?

• Design new intranet
• Build site architecture in CMS
• Convert old content that will be migrated
• Import relevant content into the new architecture
  (may require manual import)

20
Utilising a Content Management System

• Choosing an appropriate model for your business
• Exploring ways to simplify content migration
• Realising how your CMS can impact on user
  experience
• Getting your CMS to be fully accessible
• Brief case study

21
Intranet CMS user experience

• Desired outcome/experience may be the very
  different to that required for a public site
• Want to encourage collaboration and
  participation, may allow any user to publish
• Want seamless experience of web content and other
  applications/processes

22
Intranet CMS user experience

• Ease of creating/updating content
• Familiar interfaces
• Training implications
• Integration with existing systems and processes
• One more thing to remember?

23
(No Transcript)
24
(No Transcript)
25
(No Transcript)
26
Utilising a Content Management System

• Choosing an appropriate model for your business
• Exploring ways to simplify content migration
• Realising how your CMS can impact on user
  experience
• Getting your CMS to be fully accessible
• Brief case study

27
Accessible CMS inputs and outputs

• Policies and standards
• Management support?
• Contributor education
• Templates
• Controlled environment eg corporate browser and
  SOE standards
• Vendor education
• System safeguards?

28
Utilising a Content Management System

• Choosing an appropriate model for your business
• Exploring ways to simplify content migration
• Realising how your CMS can impact on user
  experience
• Getting your CMS to be fully accessible
• Brief case study

29
Snapshot of Monash

• Over 50,000 students from more than 100 countries
• 8 campuses Australia (6), Malaysia and South
  Africa
• Centres in Italy and United Kingdom
• Several study modes
• Pathway programs
• Thriving community
• 10 faculties

30
Internationally-recognised research

• International reputation in leading-edge fields
• 27 million for NHMRC research programs and
  projects (2005)
• Australian Synchrotron (2007)and National Stem
  Cell Centre
• 75 specialist research institutes/centres
• 17 cooperative research centres
• More than 2,400 academic staff publish some 5,000
  articles annually
• Global collaborations with more than 110
  institutions

National Health and Medical Research Council
31
CMS project

• Commenced in 2002 now mature. All faculties and
  almost all admin areas are CMS users.
• Goals might be different now if we were starting
  out
• Initial focus was on managing public sites

32
Selected

• TeamSite
• MetaTagger

33
Monash web strategy . . .

• Separate public content from internally focused
  content

34
Monash web strategy . . .

• Target content to user needs, roles and tasks

35
Monash web strategy . . .

• We had basic strategy and building blocks (CMS
  and portal)
• We proposed a project to develop a university
  intranet based around these technologies
• It was rejected. We have proposed it from several
  perspectives to no avail.
• So we have started very small

36
Monash intranet project

1. Find 2 or 3 early-adopters
2. Integrate CMS and portal
3. Implement a trusted authentication process
4. Usability evaluation and re-design of
   early-adopters intranets
5. Migrate early-adopters to new environment
6. Develop desktop module for portal

37
(No Transcript)
38
(No Transcript)
39
(No Transcript)
40
(No Transcript)
41
(No Transcript)
42
(No Transcript)
43
(No Transcript)
44
(No Transcript)
45
Next steps

• Orderly queue of intranet and CAS clients
• In-line editing of intranet content for
  authorised users
• Student intranet project
• Sue.Steele_at_its.monash.edu.au