OU Campus explained

Omni CMS (formerly OU Campus) is a web content management system (CMS) for colleges, universities, and other higher education institutions.[1]

Omni CMS (then known as OU Campus) was launched in 1999 using the cloud computing, software as a service (SaaS) product delivery model.[2] It was developed by OmniUpdate, a privately owned company headquartered in Camarillo, CA. OmniUpdate was started by software developers Tom Nalevanko, Lance Merker, and Yves Lempereur (developer of BinHex 4.0). OmniUpdate and Destiny Solutions merged to form ModernCampus in March 2021.

Technology

The product uses a push technology. Omni CMS can be accessed via the cloud – also known as software as a service (SaaS). The underlying platform of Omni CMS is developed in Java, and uses XSLT 3.0 for template transformation.[3] Omni CMS uses open standards, including XML, HTML, and CSS and is extensible through APIs. As a decoupled system, Omni CMS works with any server-side technology (e.g., PHP, ASP, .NET, ColdFusion) and for templates uses XHTML/HTML5 and CSS, as well as XML/XSLT.[4] [5] The templates are customizable so that developers can create sites using popular web development techniques including Responsive web design to adapt to all screen sizes and devices. Omni CMS does not store page content in a database; rather, each page is stored as an XML file on the CMS server. It is compatible with Internet Explorer, Firefox, Google Chrome, and Safari. Omni CMS' push technology architecture requires a separate database for some applications that use interactive content such as forms and surveys. These applications can be handled through the Live Delivery Platform (LDP), which provides a server-side module for plug-in application architecture. LDP is accessed and managed through Omni CMS.[6]

Features

References

  1. Web site: Fienen. Michael. Results: Higher Ed CMA Usage Survey, 2011. 7 November 2012.
  2. News: Merker. Lance. Considering Enterprise Software as a Service?. 7 November 2012. University Business. November 2009.
  3. Web site: Merker. Lance. OmniUpdate Releases Version 9 .
  4. Web site: Merker. Lance. Learning to Leverage XML for Higher Ed Web CMS .
  5. Web site: Schaffhauser. Dian. 9 Best Practices for Implementing a CMS .
  6. Web site: Spick. Geoff. Digital Asset Management Takes Front Seat for Higher Education Web CMS. CMS Wire. 7 November 2012.
  7. Web site: Berthiaume. Dan. OmniUpdate Enhances Content Reuse in OUCampus Update.
  8. Web site: Spick. Geoff. Digital Asset Management Takes Front Seat for Higher Education Web CMS.
  9. Web site: Guseva. Irina. OmniUpdate Adds Social Features to Web CMS.