The predefined Renditions type is based on the Peer-to-Peer Class.It is typically used to indicate peer relationships between items.For example, a monthly report for April (A) will be superseded by a report in May (B) that 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. The date superseded is set on the previously active record, which in this scenario is item C.This type of relationship can be created by anyone in the Records Group security group to link an item source file to any other renditions.
The supersede date is set on the item that was superseded, not on the superseding item.
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 Section 12.4.2, "Renditions Link Example." The predefined Supersedes relationship is based on the Chained List Class.
A single image might be used in multiple parent documents, for instance, and a single document might contain multiple images.
For example, a Word document (A) may have embedded content such as a spreadsheet (X) and a graphic (XX).