Your Federal Quarterly Tax Payments are due April 15th Get Help Now >>

to download - CommonSpot _ Cornell - Cornell University by liuhongmei


									CommonSpot @ Cornell
May 18, 2005

I. Background and history of CommonSpot purchase (15 min)

II. CommonSpot @ Cornell (30 min)

III. Break (15 min)

IV. PaperThin presentation: Overview and Future of CommonSpot (45 min)

V. Ask the Experts (30 min)
I: Background and History of CMS Decision
   Collaborative Stakeholder Driven Selection Process
      • Engineering included CIT in their CMS RFP process (Late Fall ’03)

      • Thomas Richardson advocated that CIT spearhead CMS purchase (3/04)

      • Thought was “to do something quickly” (3/04)

      • RFP development and evaluation (5/6) included broad representation

           • AA&D, Engineering, Library, Vet School, Registrar, and Web
           Communications. Later ILR (and others?) joined us.

           • “More non-CIT people, than CIT people” in selection meetings

      •Selected three vendors for further consideration
I: Background and History of CMS Decision (cont.)
      • Very high end tool – Works best at enterprise scale

      • Great hooks into enterprise systems (People Soft, WSDL, existing web aps)

      •Their complete suit “did everything” but overlapped with existing IT
      infrastructure. Had to use their delivery mechanism.

      • Presentation was for a solution that was much more expensive than what they
      had bid

      • We could make the parts we wanted work with “a little bit of programming”

      • Most expensive option, both in purchase price, development, maintenance,
      and server requirements. We could only afford one server for the campus
I: Background and History of CMS Decision (cont.)
      • Mature Mid-market product

      • Focused on integrating data inputs and outputs
           • Inputs could be word docs, databases, WYSIWUG editor, etc.
           • Outputs are always static files or database record sets

      • Works with any web delivery technology (CF, php, JSP, .NET, XSLT, etc.)

      • Web editor’s user interface was weak and not well connected with web

      • Too expensive to site license, CIT would have to run the single installation
I: Background and History of CMS Decision (cont.)
      • Lower mid-market product (or upper low market product)

      • Fully integrated web content manager.
           • WYSIWYG editor, template management, and web delivery are all in
           one package.
           • Not as strong for delivering content to print or other formats (but it can
           be done).

      • Integrates easily into CU Kerberos and Cold Fusion infrastructure

      • Targeted at Department level web sites – Very close to our stakeholders needs

      • Least expensive option – Site license available
I: Background and History of CMS Decision (cont.)
   Stakeholders Selected CommonSpot (8/04, purchased 12/04)
      • Good fit with stakeholders business needs

      • Ability to be independent of CIT (or host with CIT if we choose)

      • Unanimous vote from stakeholders

      • Plan was for WPG to purchase single license and host centrally until there was
      enough interest to purchase site licenses

      • David DeMello drove effort to get site license

      • Site license purchased (late 12/04)
I: Background and History of CMS Decision (cont.)
   Collaborative Stakeholder Process
      • People outside of CIT identified a common need and worked with CIT to find
      an optimal solution for the campus

           • Stakeholder group provided the direction

           • CIT provided the implementation

           • Everybody ended up happy with the results

      • This SIG is an effort to institutionalize a stakeholder driven process for
      coordination and governance of the CommonSpot site license

      • IMHO: This process should be replicated with many of CIT’s projects
Engineering College Public Web Site
Re-developing Engineering Intranet
II: CommonSpot @ Cornell

   CommonSpot website
   A collection of resources for CommonSpot users, administrators, and
   developers at Cornell.

   • Best Practices (installation, configuration, site management, security, etc.)
   • Evaluation guidelines to help decide if CommonSpot is right for your next project.
   • FAQ
   • Updates and patches
   • Contributions from the SIG are encouraged.
II: CommonSpot @ Cornell

   CIT Training initiative
   • Informed by the recommendations of the SIG, Training and Documentation (from
   CIT’s Customer Service and Marketing Division) is developing a series of workshops
   focusing on audience-specific topics (for contributors, designers, developers, power
   users, and administrators)

   • First workshop (CommonSpot Overview) will be available in late June.

   • Others will follow soon after.
II: CommonSpot @ Cornell

   CIT Hosting service

   • When is it ready? Now

   • How much does it cost? Ask Al

   • IWS will develop default templates suitable for many project and topic-based sites.
   They can also offer additional design services to tailor those to a specific unit. Finally,
   they are available for full analysis, site architecture, and graphic design.
II: CommonSpot @ Cornell

   Campus groups with active CommonSpot projects under way
      • ATA
      • ITMC
      • CALS
      • Campus Life
      • Cornell University Libraries
      • Engineering
      • Facilities
      • Human Ecology
      • ILR
      • OWC
      • ORIE
      • Planning & Budgeting
II: CommonSpot @ Cornell

   Custom Security Initiative

   • An ad hoc task force of developers are developing a packaged, easily extensible
   authentication/authorization framework.
   • Built on top of CommonSpot’s built-in APIs with all site and subsite settings
   managed in a single XML file to support a consistent, reliable, and well-documented
   approach campus-wide.
   • Makes setting up alternative authentication and authorization methods a breeze.
   • Will ship with a module for using CUWebAuth to authenticate CommonSpot users.
   • Integrates with user and group information stored outside of CommonSpot, for
   example in support of personalization and permission features managed by external
II: CommonSpot @ Cornell

   Container Element

   • PaperThin has just completed development of a new layout element that will help
   support the move to standards-based website design using CSS layout without tables.
   • PaperThin worked patiently through the testing a revision phase to give us as much
   of what we asked for as they could.
   • Look for downloads and tutorials on the website.
II: CommonSpot @ Cornell

   Possible Future Directions

   • RSS/Atom feeds – technology is clear in that CommonSpot can easily produce and
   consume feeds. We need some creative thinking to identify and develop content worth
   syndicating. This is a great way to make certain kinds of content available to uPortal.
   • Campus-Wide Event Calendar that interacts with CommonSpot sites.
   • Notification system for Cornell News Services stories.
   • Packaged integration strategy for Verisign Payment services.
   • Gateway to digital library resources and services through metadata and OAI
   • Integration with Cornell Courses of Study and Faculty research.
   • ???

To top