Dependency types
A dependency is absolute when the dependency always applies or occasional when the dependency sometimes applies. However, if an occasional dependency applies to an item, it must, as a rule, be transferred (or be present on the destination Content Manager).
For example, a Component must have a Schema to define its structure so it is an absolute dependency, but a Folder may have a linked Schema associated with it (in which case the linked Schema will be transferred) so the dependency is occasional (but its transfer is not optional).
- Absolute dependencies
-
The following diagram shows the absolute dependencies between types of Content Manager items. Each item depends on the items pointing to it. For example, a Root Structure Group depends on its Publication.
- Occasional dependencies
-
The following table shows the occasional dependencies between item types. Note that while the dependency may or may not be present, if it is present, the dependent item must be transferred, or already present on the destination Content Manager.
For example, not every Folder has a Metadata Schema, but a Folder that has a Metadata Schema depends on that Metadata Schema and must either be included in the transfer or found on the destination Content Manager, just like an absolute dependency.
An item of type... ...may need an item of type Publication Metadata Schema Publication Component (linked) Publication Process Definition Publication Parent Publication Publication Template Bundle Process Definition Publication Task Process Definition Target Group Target Group (used) Target Group Keyword (used) Folder Schema (linked) Folder Metadata Schema Structure Group Metadata Schema Structure Group Component (linked, if the Metadata Schema uses Component Links) Structure Group Page Bundle Process Definition Schema Schema (embedded) Schema Category (referenced) Schema Schema (referenced) Schema Component (linked, as a default field value) Schema Keyword (as a default field value) Schema Bundle Process Definition Component Component (linked, either in data or in metadata) Component Category (if the Metadata Schema uses Categories Links). Component Keyword (used for pick values in a list) Multimedia Component Component (linked, in metadata) Multimedia Component Multimedia Type Template Building Block Template Building Block (included) Template Building Block Parameter Schema Template Building Block Metadata Schema Component Template Schema (related) Component Template Category (tracked) Component Template Template Building Block (included) Page Template Parameter Schema Page Template Metadata Schema Page Template Template Building Block (included) Page Template Region Schema (here also called Page Schema) Region Schema Region Schema (for its nested Regions) Page Page Template Page Metadata Schema Page Component (linked) Page Component (in Component Presentation) Page Component Template (in Component Presentation) Page Target Group (in Component Presentation) Category Category (its parent Category) Category Metadata Schema Keyword Keyword (its parent Keyword) Keyword Keyword (its related Keyword) Keyword Metadata Schema (as of SDL Tridion 2009) Virtual Folder Metadata Schema Virtual Folder Virtual Folder configuration (any item) Process Definition User Group Process Definition Approval Status Process Definition Template Building Block (as of SDL Content Porter 2013) Group Group Membership Group Publication (allowed) Business Process Type Bundle Schema Business Process Type Metadata Schema In addition to this, there are certain connections between items that could be considered occasional dependencies, but that will not cause the dependent item to be transferred or searched for on the destination Content Manager. Such connections are:
- A Group may have a scope that limits its use to three Publications (and so is, strictly speaking, dependent on those Publications), but only two of those Publications are present on the destination Content Manager. In this situation, the scope of the Group will be updated during import.
- An item may have application data associated with it that links to other items (and so, indirectly, the item may said to be dependent on those items). If the import is configured to not import such application data (because the application to which the application data belongs is not set up on the destination Content Manager), then this indirect dependency is also ignored.