GNM_RCS_Rights_Approval_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 approval of rights in RCS. Separate documents deal with all other aspects of rights management in RCS including rights defaults, 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 approval screen

The Rights agreed on every commission require approval by the Rights department. This approval is unrelated to the fee approval process that occurs within Editorial and is described in the documents relating to Commissions.

All commissions are queued for review in the Rights approval screen, and the Rights department users also see a count of items that are in the queue on their Welcome screen.

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

Rights → Rights approval

• 1. Restricting by format, source, or book extract

To facilitate quicker processing the commissions requiring rights approval they are separated into 7 distinct lists:

• • Text

  • Pictures

  • Illustrations

  • Audio

  • Video

  • Staff

  • Book extracts

Each of these groups has separate issues that the approver may need to deal with, so it is easier to process all commissions of one type together.

The user can also reorder the lists by contributor name which enabled them to process all commission for the same contributor together, again saving time.

• 1. Matched, fulfilled, or unmatched

The user can further restrict the lists by choosing one of Matched, Fulfilled or Unmatched at the top of the screen. The default is Matched when the screen opens as these are ready for payment and are therefore a priority.

• 1. Rights palette

All the data and features that would normally appear in the Rights palette are available in this screen – just not in a separate window. This layout makes it easier to process.

The approval of commission rights is achieved by pressing the “Approve” button.

• 1. Unapprove

The approver can see a list of all commissions they recently approved, and then unapproved any of them, by choosing the Unapprove radio group item instead of one of the 7 list choices for approval. The “Approve” button will be re-labelled “Unapprove” and pressing it will unapproved the rights.

• 1. Matching history

The “M Hist” button opens the Matching history screen.

• 1. Rights histories

The “R Hist” button shows the Rights history for the current contributor.

• 1. .Contracts under rights review screen

All contracts must be rights reviewed by the Rights department. Those contracts that have not been marked as reviewed are queued in the “Contracts under rights review” screen. The Oracle Form is called rcs_agmt_050_pc.fmb running in a mode that only shows these contracts. (The mode is passed to it from the menu item.) It is accessed from this menu option:

Contracts → Contracts under rights review

The approval process is slightly different to that for commissions. The user simply checks the “Rights reviewed?” checkbox to confirm the rights have been reviewed and are correct. For contracts rights are not approved in the rights palette as they are for commissions.

All other features of the screen are as described in the documents relating to Contracts and so they are not repeated here.

End of Document