Your SlideShare is downloading. ×
0
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Powerpoint presentation for Software AG Users Group
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Powerpoint presentation for Software AG Users Group

1,820

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,820
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • http://www.utexas.edu/index.html.SAVE
  • Efficiency example: news release time 10 minutes to create a Web page and another 15 minutes to get it linked all of the places it should be linked
  • Hundreds of Web Servers Thousands of Web publishers/developers Content owners/contributors Millions of Web consumers
  • Hundreds of Web Servers Thousands of Web publishers/developers Content owners/contributors Millions of Web consumers
  • Hundreds of Web Servers Thousands of Web publishers/developers Content owners/contributors Millions of Web consumers
  • Hundreds of Web Servers Thousands of Web publishers/developers Content owners/contributors Millions of Web consumers
  • On bullet 2 mention that publishers can choose to create part of a site with the CMS and another part in a traditional method On bullet 3, if the medical school for example deploys a CMS for their Web site and the Business School deploys one for their Web site, as is often the case does the Medical school benefit from the Business School, can they share commons assets across their different solutions?
  • 4 vendors: Stellent, Interwoven, Merant Collage, Rhythymx Percussion
  • Hundreds of Web Servers Thousands of Web publishers/developers Content owners/contributors Millions of Web consumers
  • Press Control Shift F5 to active contributor mode Rebeling Stellent
  • Transcript

    • 1. Web Content Management: The Texas Experience Glenda Sims
    • 2. Outline <ul><li>University Webs </li></ul><ul><li>CMS models </li></ul><ul><li>Selecting a solution </li></ul><ul><li>Implementation </li></ul><ul><li>Goals </li></ul>
    • 3. www.utexas.edu <ul><li>Hundreds of Web servers </li></ul><ul><li>Containing thousand of Web sites </li></ul><ul><li>Created and maintained (sometimes) by thousands of Web publishers </li></ul><ul><li>Who produce millions of pages </li></ul>
    • 4. Attributes of a High-Quality University Web Site <ul><li>Complete </li></ul><ul><li>Current </li></ul><ul><li>Coherent </li></ul><ul><li>Searchable </li></ul><ul><li>Accessible </li></ul><ul><li>Attractive </li></ul><ul><li>Robust </li></ul><ul><li>Secure </li></ul><ul><li>Cost Effective </li></ul><ul><li>Aligned with spirit and goals of institution </li></ul>
    • 5. Feb 2002 www.utexas.edu
    • 6. UT Self Assessment on These Attributes Early 2002
    • 7. Some Key Questions? <ul><li>Does everyone have to be an accessibility expert? </li></ul><ul><li>Does everyone have to know HTML or Dreamweaver? </li></ul><ul><li>Can we free up time for highly-trained Web professionals to create and innovate? </li></ul><ul><li>Can we do things more efficiently? </li></ul><ul><li>Where does your content go when it dies? Does it ever die? </li></ul>
    • 8. Progress <ul><li>UT Web redesign in 2002 improved in many of these areas </li></ul><ul><ul><li>More attractive </li></ul></ul><ul><ul><li>More consistent, better branding </li></ul></ul><ul><ul><li>Modular templates </li></ul></ul><ul><ul><li>More usable and accessible </li></ul></ul><ul><ul><li>Improved division of labor </li></ul></ul><ul><ul><ul><li>IT - infrastructure </li></ul></ul></ul><ul><ul><ul><li>Public Affairs – content </li></ul></ul></ul><ul><ul><li>More dynamic </li></ul></ul>
    • 9. University’s Home Today
    • 10. Progress Needed in Other Areas <ul><li>Current </li></ul><ul><li>Cost effective </li></ul><ul><li>Accessible </li></ul><ul><li>Workflow </li></ul><ul><li>Metadata </li></ul><ul><li>Can a Web content management solution help? </li></ul>
    • 11. Typical University Web Presence Web Publisher Web Consumer Content Contributor Web Publisher Web Publisher Web Publisher Web Publisher Content Contributor Content Contributor Content Contributor Content Contributor Content Contributor Web Consumer Web Consumer Web Consumer Web Consumer IIS Web Server Apache Web Server IIS Web Server IIS Web Server Apache Web Server Apache Web Server Apache Web Server IIS Web Server Apache Web Server IIS Web Server
    • 12. Typical Web Content Management Model Web Editor Web Consumer Content Contributor Web Publisher Web Publisher Content Contributor Content Contributor Content Contributor Web Consumer Web Consumer Web Consumer Web Content Management Server Web Editor Template Creation Content Approval
    • 13. A Point CMS Approach in Higher Ed Web Publisher Web Consumer Engineering Web Server (CMS Solution B) Law School Web server (CMS Solution A) Business School Web Server (CMS Solution C) Departmental Apache Server (CMS Solution D) Content Contributor Web Publisher Web Publisher Web Publisher Web Publisher Content Contributor Content Contributor Content Contributor Content Contributor Content Contributor Web Consumer Web Consumer Web Consumer Web Consumer
    • 14. Clear Differences <ul><li>Commercial content management </li></ul><ul><ul><li>More highly centralized </li></ul></ul><ul><ul><li>Greater control of content, branding, toolset </li></ul></ul><ul><li>University </li></ul><ul><ul><li>Decentralized </li></ul></ul><ul><ul><li>Less control </li></ul></ul>
    • 15. A Hybrid Model Web Editor Web Consumer Content Contributor Web Publisher Web Publisher Content Contributor Content Contributor Content Contributor Web Consumer Web Consumer Web Consumer Web Content Management Server Web Editor Template Creation Content Approval Pre-existing Apache Web Server Pre-existing IIS Web Server
    • 16. Advantages of Hybrid Model <ul><li>Leverages CMS solution yet is still sensitive to the distributed nature and political realities of a research University </li></ul><ul><li>Can use the CMS solution selectively; rely on carrot rather than stick </li></ul><ul><li>Better than typical University approach because CMS solution is shared across the enterprise </li></ul>
    • 17. In Pursuit of a Solution <ul><li>Formed cross-campus team IT </li></ul><ul><ul><li>Library </li></ul></ul><ul><ul><li>Public Affairs </li></ul></ul><ul><ul><li>Academic colleges </li></ul></ul><ul><ul><li>Business units </li></ul></ul><ul><ul><li>(http://www.utexas.edu/web/cms/steer.html) </li></ul></ul><ul><li>Developed functional specification for solution </li></ul><ul><li>Evaluated possibilities </li></ul><ul><ul><li>Open Source </li></ul></ul><ul><ul><li>Building Our Own </li></ul></ul><ul><ul><li>Commercial space </li></ul></ul>
    • 18. Timeline Software Install (development) April 2003 Metadata &amp; Security Models Jul-Aug UT Open House Implementation Planning May-Jun Sep-Dec Production Hardware Software Installation 2005 Nov-Jan Dec-May Early Adopters Develop Templates, Workflows &amp; Sites Solicit community input July Develop functional specs Jul-Aug Review solutions Jul-Aug Request for information August Review responses Select 4 possibilities September Product demos October Select 2 finalists October On site POCs Nov-Dec License negotiation Feb-Mar Product Training Round 1 April Product recommendation January 2004 Early wins May
    • 19. Major Functionalities <ul><li>Integration with campus infrastructure (databases, Web servers, authentication) </li></ul><ul><li>Content creation; knowledge of HTML or Dreamweaver not required </li></ul><ul><li>Templates for attractive, consistent presentation </li></ul><ul><li>Workflow </li></ul><ul><li>Metadata </li></ul><ul><li>Versioning </li></ul><ul><li>Deployment to other Web servers </li></ul><ul><li>Support for standards (accessibility, XML, Web services, WebDAV) </li></ul>
    • 20. Selection Process <ul><li>Selected 4 vendors for 1 day demo </li></ul><ul><ul><li>Stellent </li></ul></ul><ul><ul><li>Interwoven </li></ul></ul><ul><ul><li>Merant Collage </li></ul></ul><ul><ul><li>Rhythymx Percussion </li></ul></ul><ul><li>Narrowed list to 2 vendors </li></ul><ul><ul><li>Stellent </li></ul></ul><ul><ul><li>Merant Collage </li></ul></ul><ul><li>Each of 2 final candidates conducted 10 day proof of concept on site </li></ul><ul><li>Stellent Content server selected. </li></ul>
    • 21. Why Stellent? <ul><li>Excellent content conversion </li></ul><ul><li>Solid, flexible workflow </li></ul><ul><li>But no solution was a perfect fit </li></ul><ul><li>Success would depend upon both product and partnership with vendor </li></ul><ul><li>Commitment from Stellent to the University </li></ul>
    • 22. CMS Scorecard -- + Macintosh Support Support for Standards -- Deployment to other Web Servers Versioning Metadata + Workflow Templates + Content Creation Integration w/ Campus Infrastructure Stellent Merant Requirement/Vendor
    • 23. Stellent Architecture at UT Main Content Management Server (Solaris) Web Editor Content Contributor Web Publisher Content Contributor Content Contributor Web Consumer Existing Apache Web Server Existing IIS Web Server Active Directory Oracle Stellent Content Server Instance Windows PDF Converter Server Netapp Filer Authentication PDF Conversion Metadata Store Disk for Content Server Web Consumer (possibly)
    • 24. Implementation Stages <ul><li>Integration with existing campus Web servers and authentication </li></ul><ul><li>Development of common metadata/document models </li></ul><ul><li>Quick early wins to provide carrots for campus; </li></ul><ul><li>Must demonstrate value of learning new way of doing things for Webmasters and contributors </li></ul>
    • 25. Quick Win Examples Around Austin Handbook of Operating Procedures
    • 26. Around Austin <ul><li>Developed using Stellent SiteStudio </li></ul><ul><li>Enables very easy editing of existing site </li></ul><ul><li>Developer sets up site with editable regions </li></ul><ul><li>Contributor navigates to site, presses key sequence, and switches to edit mode to update site </li></ul><ul><li>Edits can enter workflow if desired, or go live immediately </li></ul><ul><li>Example ( http://wwwtest.utexas.edu/work/stellent/austin/ ) </li></ul><ul><li>Note: Windows-only solution (for developers/contributors) </li></ul>1) alt + space (open system menu) /2) R (to restore) 3) alt + space M (for move) 4) Arrows (to bring her over)
    • 27. Handbook of Operating Procedures <ul><li>President’s Office, VP Offices and HR currently create polices in MS Word and use email to edit </li></ul><ul><li>Easy to get the wrong version published </li></ul><ul><li>Create site with Stellent Site Studio </li></ul><ul><li>Users drop current MS Word documents in WebDAV folder </li></ul><ul><li>Automatically checked in to CMS </li></ul><ul><li>Metadata automatically applied </li></ul><ul><li>Presentation template automatically applied </li></ul><ul><li>HOP Table of Contents automatically updated with links </li></ul><ul><li>Example ( http ://wwwtest.utexas.edu/work/stellent/hop/ ) </li></ul>
    • 28. 2004 Accomplishments <ul><li>Purchased Product </li></ul><ul><li>Development environment </li></ul><ul><li>Training for early adopters - Web developers </li></ul><ul><li>Template creation </li></ul><ul><li>Production environment </li></ul><ul><li>Active Directory integration </li></ul><ul><li>Security model </li></ul><ul><li>Metadata model </li></ul><ul><li>Show the way by walking there first and let people choose the approach that works best for them </li></ul><ul><li>Campus product advisory board </li></ul>
    • 29. 2005 Goals <ul><li>Baseline measurement for web quality attributes: </li></ul><ul><ul><li>Complete, Current, Coherent, Searchable, Accessible, Attractive, Robust, Secure, Cost Effective, Aligned with spirit and goals of institution </li></ul></ul><ul><li>Second round of Stellent Training </li></ul><ul><ul><li>Site Studio </li></ul></ul><ul><ul><li>Customizing Stellent Content Server </li></ul></ul><ul><li>4 prod sites deployed using Stellent by June 2005 </li></ul><ul><li>Begin Training the Masses – Summer 2005 </li></ul><ul><li>10-15 prod sites deployed using Stellent by December 2005 </li></ul><ul><li>“ I wanna play!” “Wow, I’m glad I use Stellent!” </li></ul>
    • 30. How Will We Know if it Works? <ul><li>Campus research opportunities (i.e. School of Information) </li></ul><ul><li>Measurement of campus Web </li></ul><ul><ul><li>Frequency of content updates, less stale content </li></ul></ul><ul><ul><li>Number of contributors </li></ul></ul><ul><ul><li>Less time spent on routine maintenance </li></ul></ul><ul><ul><li>Fewer Web servers on campus </li></ul></ul><ul><ul><li>Improved consistency for usability and branding </li></ul></ul><ul><ul><li>More accessible </li></ul></ul><ul><ul><li>More secure </li></ul></ul><ul><ul><li>Improved content discovery via metadata </li></ul></ul><ul><li>How to measure? </li></ul><ul><ul><li>WatchFire </li></ul></ul><ul><ul><li>Urchin </li></ul></ul>
    • 31. Additional Info <ul><li>http://www.utexas.edu/web/cms/ </li></ul><ul><li>[email_address] </li></ul>

    ×