Renditions Supersedes Predefined Relationship Types

12-2 Oracle Fusion Middleware Users Guide for Universal Records Management

12.1 About Related Content

Related content establishes a type of relationship, or link, between individual items. The relationships are based on one of four available Relationship Classes . Several Predefined Relationship Types are also provided but custom relationship types can be added to suit the need of the site environment. See Adding or Editing a Custom Relation Type Administrative Function on page 12-7 for details. There are two basic methods of creating relationships between items: ■ Creating a relationship from one existing item to another existing item : If a relationship is created from an item in the system to another, existing item in the system, the search page can used during the process to access the existing item and link to it. For details see Linking to an Existing Item on page 12-9. ■ Creating a relationship from an existing item to a new item : If a relationship from an item is added to a new item, use the content check-in page during the process to create the new item. For details see Linking to a New Item on page 12-9.

12.2 Predefined Relationship Types

The following predefined relationship types are available: ■ Renditions , based on the Peer-to-Peer Class ■ Supersedes , based on the Chained List Class ■ Supporting Content , based on the Supporting Content Class ■ Cross-Reference , based on the Cross-Reference Class You can also define your own relationship types.

12.2.1 Renditions

The predefined Renditions type is based on the Peer-to-Peer Class . It is typically used to indicate peer relationships between items. Rendition in this sense means a link to a copy or some other version of an item. For example, an editable text item could be linked to a non-editable display content item, or a physical printed rendition. This type of relationship can be created by anyone in the RecordsGroup security group to link an item source file to any other renditions. Permissions: You can create relationships between items only to which you have access. You cannot create relationships to items for which you do not have adequate access privileges such as assigned rights, classification, supplemental markings, and so on. Important: When items are deleted, all corresponding relationships are deleted, except in the case when a superseded content item is in the midst of disposition processing. A dangling relationship exists until the superseded content item completes its disposition processing. Then the relationships are deleted. Configuring Related Content Links 12-3 Figure 12–1 Renditions Links For example, all versions of a file may be a different graphic type: .psd, .jpg, and .tif. This figure shows A .psd is linked to B .jpg, and B is linked to C .tif. Item C is linked indirectly by association to A, but it is not actually linked directly to A. If the link between A and B is removed unlinked, then C is no longer linked by association to A. To step through an example of creating this type of link, see Renditions Link Example on page 12-11.

12.2.2 Supersedes

The predefined Supersedes relationship is based on the Chained List Class . It enablesa user to create a hierarchical chain of content items where each item in the list is superseded by another item. One example is a subject-to-review content item, which must be maintained with current information. The supersede type causes the previous content item to become obsolete. A supersedes relationship creates a hierarchy chain between items. The supersedes relationship is special because it enables a user to harness the disposition processing to handle superseded items. This type of relationship is created by anyone in the RecordsGroup security group to link an item superseding another. Figure 12–2 Supersedes Links The Supersedes relationship can be set on any item in the chained list, but is typically set on the most recent. The supersede date is set on the item that was superseded, not on the superseding item. Only the most recent version is shown in the Links area on the Content Information page; not all revisions are shown. The most recent item that superseded another item is at the top of the chained list. 12-4 Oracle Fusion Middleware Users Guide for Universal Records Management For example, a monthly report for April A will be superseded by a report in May B which is later superseded by a report in June C, and so on. This figure shows A was superseded by B, which was superseded in turn by C, which was superseded by D. Item D is the most recent record. The date superseded is set on the previously active record, which in this scenario is item C. To step through an example of creating this type of relationship, see Superseded Link Example on page 12-13.

12.2.3 Supporting Content