GNM_RCS_Rights_Defaults_TS

• 1. .Introduction

     1. Purpose

The document GNM_RCS_Rights_Management_FS.docx is the functional specification that describes what business functions RCS supports in relation to rights management.

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 definition of rights and rights properties in RCS, and the creation of rights profiles for commission, contracts and disregard reasons. Separate documents deal with all other aspects of rights management in RCS including rights approval, rights on content, and the publishing of rights data.

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. .Rights screen

Rights and rights properties define permissions that GNM acquires or seeks to acquire that determine what GNM may do with content, and for how long. The Rights and their properties are defined in the Rights screen.

The Oracle Form is called rcs_rght_010_pc.fmb and is accessed from this menu option:

Rights → Rights

The screen has three tabs: the first for Rights; the second for Properties; and the third for Groups.

• 1. Rights

A list of rights is maintained that GNM is interested in, and alongside it the associated properties of those rights, and the order in which they should be displayed. The properties must be chosen from the list of all known properties which are defined in the Properties tab.

Against each right and each property associated with a right the user can check either or both the Tag checkboxes (API and MM) which will lead to the property being included in the XML rights tags that are published (for the API and Multimedia respectively). These XML feeds of rights information are described in more detail in a separate document in this documentation set.

As the model is generic the user can define what the hint text and field prompts should be for each right when it is displayed elsewhere in the RCS application.

• 1. Properties

The full list of properties that a right may have is maintained in this tab:

The attributes of each right are maintained as shown above, and for each right a list of valid values and a list of valid units can also be defined.

The Display format field allows the user to define how the right should be presented in form of a sentence.

The user can also define whether the property should be included in summaries of data held against the right by checking or unchecking the Include in summary? checkbox?

• 1. Groups

Rights are displayed in groups elsewhere in the system: the list of available groups is maintained in this tab, including the order in which each group should be displayed:

• 1. .Defaults screen

Right profiles define standard sets of default rights and their properties that are applied to new commissions, contracts and siregard reasons. The Defaults screen is used to maintain rights profiles that apply to commission and contracts.

The Oracle Form is called rcs_rper_010_pc.fmb and is accessed from this menu option:

Rights → Defaults

For each combination of data on the left hand side of the screen a rights profile can be defined to the right.

The rights applicable are listed, along with whether each right is acquired or not. The order in which the right should be displayed elsewhere in the system is also defined. For each right included in the profile all of its properties are available on the right hand side and any default values and units can be defined.

Once a profile is marked as Live?, and has been used at least once, it cannot be changed.

By default the screen queries just the current profiles and any future ones that are being prepared. The user can opt to see a full history of profiles by changing the radio group option at the top of the screen from Current to All.

The user can view the description of each right and its default property values (in a sentence based format) by clicking on the Summary tab. This tab shows sentences that are constructed for the rights and their properties based on rules defined in the Rights screen, as described earlier in this document. For example:

The “Group copy” button at the top of the screen enables the user to copy the properties of the highlighted right to all the other rights in this profile that are in the same rights group. This is simply a time saving device used when setting up new rights profiles.

• 1. .Disregards screen

The Disregards screen is used to maintain rights profiles that apply to the reasons used to disregard content.

The Oracle Form is called rcs_rper_020_pc.fmb and is accessed from this menu option:

Rights → Disregards

The operation of the Disregards screen is the same as that of the Defaults screen, except that the Criteria on the left hand side that define each profile are different. For disregards the criteria is a combination of the Disregard reason and the Format of content.

End of Document