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.
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.
17.
18. Timeline Software Install (development) April 2003 Metadata & 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 & 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.
20.
21.
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)
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?