GNM_RCS_Domains_Sections_Departments_TS

• 1. .Introduction

     1. Purpose

The document GNM_RCS_System_Configuration_FS.docx is the functional specification that describes what features RCS has in relation to the configuration of the system.

This document is one of a set of technical specifications that provide details of how those functions are implemented in RCS.

• 1. Scope

This document focusses on the configuration of domains, sections and departments. Separate documents deal with all other aspects of the system’s configuration.

This document is intended as a high-level technical document outlining how the relevant business functions are implemented in terms of software modules.

Importantly, this document does not aim to provide the level of detail that would be required in a programming specification in areas such as program structure, detailed business rules, data integrity, validation, locking considerations, data security, and calls to/from other software modules, performance considerations, and so forth.

For details of program logic and coding, the reader should refer to the program files themselves.

• 1. .Domains

A list of website domains is managed in RCS, allowing domains to be linked to Publications. In some cases multiple domains are linked to the same publication.

The domain data is extracted from the content feed from the website. (See separate documentation describing the Website content feeds.) Whenever a new domain is identified in the feed it is added to the WEBSITE_DOMAINS table and it becomes visible in the Website domains screen.

This screen is accessible from the menu option: Housekeeping → Department setup → Website domains

This opens the Oracle Form named rcs_wdom_010_pc.fmb as shown below.

This screen is only accessible to RCS Administrators.

• 1. .Sections

RCS was originally developed for the print edition and not the website. This led to a department centred model. When the website started using RCS it did not have the concept of a published department: instead there were sections. The Website section mapping screen makes it possible to marry the two i.e. to link website sections to publication departments.

These links form part of the security model that determines who processes what in RCS: users are granted permissions on Cost centres; Cost centres are linked to Publication departments; and Publication departments are linked to Sections.

The Website section mapping screen is accessible from the menu option: Housekeeping → Department setup → Website section mapping

This opens the Oracle Form named rcs_wsec_010_pc.fmb as shown below.

This screen is only accessible to RCS Administrators.

The radio group at the top of the screen allows the user to focus on those sections waiting to be mapped; or to see those already mapped; or to see them all.

• 1. .Departments

     1. Editorial departments

As stated in the previous section, the structure of the newspaper is based on departments. Each page belongs to a department such as Foreign or Sport.

A list of these departments is maintained for each publication managed in RCS. The department code for each published page is stored within the page itself and is available in the Text archive. This is where RCS gets information about printed copy from.

The website does have the concept of departments in its pages, but has sections instead. To ensure two separate models were not required dummy departments have been created for the website and the sections are mapped to them.

The Editorial departments screen is accessible from the menu option: Housekeeping → Department setup → Editorial departments

This opens the Oracle Form named rcs_edep_010_pc.fmb as shown below.

This screen is only accessible to RCS Administrators.

.

• 1. Department translations

Over time department codes have changed and editorial desks have been allocated new department codes to use. RCS simplifies all this by making it possible to combine codes i.e. translate one code into another. For example, the Society desk now has 4 codes “so1”, “so2”, “so3”, and “so4”, but to simplify things translations have been defined to ensure all content appears under “so1”. NB This only applies to print content.

Section translations can also be defined in a similar way.

The Department translations screen is accessible from the menu option: Housekeeping → Department setup → Departments translations

This opens the Oracle Form named rcs_edep_050_pc.fmb as shown below.

This screen is only accessible to RCS Administrators.

.

• 1. Department visibility

Not all publications that RCS is aware of need to be managed within RCS. As such they can be configured to be not visible. For example Guardian International and Observer International were once managed in RCS but aren’t any longer. Consequently they are defined as not visible.

Additionally, some departments within publications may not be relevant. For example if an Observer department code appears on a Guardian page then it would be treated a “misplaced”.

It is also helpful to identify codes that relate to Specials. This ensures that those pages/supplements can be diverted to a screen in which the RCS Administrator allocates them to another editorial department.

Various other flags can be set to determine how the content under each department is managed.

The Department visibility screen is accessible from the menu option: Housekeeping → Department setup → Departments visibility

This opens the Oracle Form named rcs_edep_020_pc.fmb as shown below.

This screen is only accessible to RCS Administrators.

.

• 1. COA mappings

Editorial departments need to be mapped to Cost centres within RCS. This is required so that the structure of the paper (and the website, via sections) can be mapped to the budgetary and financial structure of the organisation, thus enabling costs of the published content to be allocated to the relevant Cost centres.

In addition to this there is a facility to identify the default Chart of accounts Product code and Project code for each of the primary publishing formats within each department i.e. Text, Picture, Artwork, Audio and Video.

The Department cost centre mappings screen is accessible from the menu option: Housekeeping → Department setup → COA mapping

This opens the Oracle Form named rcs_cdep_010_pc.fmb as shown below.

This screen is only accessible to RCS Administrators.

End of Document