WORLD CUP MANAGEMENT 2014

World Cup Management 2014

[Name of the Author]

World Cup Management 2014

The CPS has been designed and developed in-house, and so its workflow and process model has evolved to its current form for the purpose of World cup 2014. The CPS client is built using Microsoft .Net 3.5 and takes full advantage of Windows Presentation Foundation (WPF). The following screen shots of the CPS user interface illustrate some of its features.

Fig 1a: Screen shot of the CPS story-editing window

Fig 1b: CPS, showing the index editor

Figure 1 depicts a screen shot of its story-editing window. The CPS has a number of tools supporting its story editing functions such as managing site navigation, associating stories to indices and others such as search.

As you can see there is a component-based structure to the story content - figure 1a shows a video, an introduction and a quote.

These components are pre-defined allowing a journalist to drag and drop as desired. It is clear that the UI is not a WYSIWIG editor. The current incarnation of the CPS focuses on content structure rather than presentation or content metadata.

Although the editor is not WYSIWIG, CPS content is available for preview and indeed publication to a number of audience facing outputs and associated devices. On publication, CPS assets are statically rendered for audience-facing output - flavours include RSS, Atom, High-Web XHTML, JSON, Low-Web XHTML and mobile outputs (Heikki, 1992: 1-11).

Fig 2: News CPS static publishing

The static CPS delivery architecture (depicted in Fig 2 above) provides a highly scalable and high performance static content object-publishing framework.

The CPS UI utilises a Windows Communication Foundation data layer API abstraction which proxies the underlying persistence mechanism (an Oracle relational database). The abstracted relational data model captures and persists stories and media assets as well as site structure and associated page layout.

The CPS UI allows the journalist to author stories, media and site structure for preview, eventual publication and re-publication. A daemon process, the CPS publisher, subscribes to publication events for processing and delivery. The CPS publisher contextualises content objects in order that they are appropriate for required audience/platform output (McLaughlin, 2006: 89-94). Filtered, contextualised assets are rendered by the CPS publisher as a static file per output type. The CPS publisher uses a Model-View-Controller (MVC) architectural pattern to separate the presentation logic from thedomain logic.

Each output representation is made persistent onto a Storage Area Network (SAN).

Although the CPS relational content model and static publishing mechanism scales and performs well it has a number of functional limitations. CPS authored content has a fixed association to manually administered indices and outputs are fixed in time without any consideration to asset semantics, state changes or semantic metadata. Re-using and re-purposing CPS authored content to react to different scenarios is very difficult due to the static nature of its output representations (Bernhard, 2000: 12-18). Re-purposing content within a semantic context driven by metadata is impossible without manual Journalist management and re-publishing. Manual complex data management inevitably leads to time, expense and data administration headaches.

The CPS relational data model currently has a very simple metadata model capturing ...