GNM_RCS_Content_Processing_Rules_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 rules RCS applies to content in order to try to process it without any user intervention. 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. .Content processing rules

RCS attempts to process as much content as possible automatically, from both web and print sources, to reduce the amount of content processing that has to be done manually by users.

This automated processing is based on rules defined in database triggers that fire when the data is stored, and also more flexible rules that are user-defined in housekeeping screens.

• 1. Triggers rules

The following rules are examples of those that are executed by the trigger mtrl_br_iu when each item of content is stored in the MATERIAL table. (This list is not exhaustive as that would just replicate the trigger.)

• • “'%&%” is replace with “&” in the section name;

  • Department & section transactions are applied where applicable;

  • Simple rules are applied to convert weather pictures to graphics;

  • Simple rules are applied to convert crosswords to graphics;

  • The filename and PicDar URN are checked to see if they contain a valid CRN or ARN;

  • The headline/caption, contributor, and IPTC fields are tidied removing unwanted characters;

  • If Steve Bell content is identifiable it is converted to a graphic when recorded as a picture;

  • Where content is clearly marked as Guardian copyright the content is staffed; and

  • TV page images are disregarded as PR.

The user-maintained rules in the following section of this document are also applied.

.

• 1. Image rules

The Image rules screen lists all of the user-defined rules that are applied to images. This screen is accessed from the menu option Housekeeping → Content processing → Image rules

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

This screen is only accessible to RCS Administrators.

The longest rules are tested first, with the shortest last – this ensures a longer rule is not ignored because a shorter rule matched the data first.

• 1. Copyright

If the IPTC copyright and editorial department code data for an image are “like” any of the data on this tab then the appropriate action will be taken, if an automated action has been defined.

When making a change to a rule the user can ensure the same change is made on the corresponding rule for all other publications by ticking the checkbox at the bottom of the screen.

.

• 1. Location

If the Location data for an image is “like” any of the data on this tab then the appropriate action will be taken, if an automated action has been defined.

• 1. Source

If the Source & editorial department code data for an image are “like” any of the data on this tab then the appropriate action will be taken, if an automated action has been defined.

• 1. Item

If the Name and Item name data for an image are “like” any of the data on this tab then the appropriate action will be taken, if an automated action has been defined.

• 1. Provider

If the IPTC provider data for an image is “like” any of the data on this tab then the appropriate action will be taken, if an automated action has been defined.

• 1. Caption

If the Caption and editorial department code data for an image are “like” any of the data on this tab then the appropriate action will be taken, if an automated action has been defined.

• 1. URL

If the URL and editorial department code of an image matches any of the data on this tab then the appropriate action will be taken, if an automated action has been defined.

• 1. Cartoon description

If the Cartoon description and editorial department code for an image are “like” any of the data on this tab then the appropriate action will be taken, if an automated action has been defined.

.

• 1. Story rules

The Story rules screen lists all of the user-defined rules that are applied to stories i.e. text. This screen is accessed from the menu option Housekeeping → Content processing → Story rules

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

This screen is only accessible to RCS Administrators.

The longest rules are tested first, with the shortest last – this ensures a longer rule is not ignored because a shorter rule matched the data first.

• 1. By-line URL

If a URL is in the by-line of a story then the following rules are applied:

When making a change to a rule the user can ensure the same change is made on the corresponding rule for all other publications by ticking the checkbox at the bottom of the screen.

.

• 1. Headline

If the Headline is “like” any of the data on this tab then the appropriate action will be taken, if an automated action has been defined.

• 1. Story start

If the Story start i.e. first sentence(s) is “like” any of the data on this tab then the appropriate action will be taken, if an automated action has been defined.

.

• 1. Description

If the Description (web content only) is “like” any of the data on this tab then the appropriate action will be taken, if an automated action has been defined.

End of Document