Page Comparison

Icon

Behavior

VIDEO: How Relationship Behaves

You select Content Items based on the Query Filter of the Field. On assignment, you must provide information about the relationship between the assigned and the original content. The underlying relationship schema defines which relationship information you must provide.  

Pre-Requirement

Before creating a Relationship Field, you must create the schema used for providing information about the relationship. This schema shows up when assigning a Content Item in this field. 

Parent-Child Setup

You can create a schema "Relationship" following a parent-child setup. When you connect your Relationship schema to the Relationship field, the parent-child hierarchy is ignored. If you connect the Relationship field to a parent, you will only see fields on the parent. If you connect the Relationship field to a child, you will only see fields on the child, no propagated fields from the parent.

Batch Actions:

• Download all related Content Items

• Add all related Content Items to basket

Related content items can be downloaded all together or placed all together in the basket for further processing, e.g., editing or sharing. Additionally, each individual item can be downloaded directly or added to the basket.

Limitation

Relationship Fields are not available in Batch Editor! You can not edit a single or multi relationship in the Batch Editor batch edit mode (only in single edit), nor Excel Roundtripping App. You can easily edit them via API. 

Furthermore, Content Items or List Items cannot be sorted based on Relationship fields.  
You cannot add Relationship Fields to filters in the Content Browser or List Browser.  

Important to note is that you can set the search settings (search, index) on the relationship field. However, the Content Browser search only delivers results for the Content Item, whose metadata matches the search. The Content Browser does not deliver related Content Items. 

Display pattern

Picturepark does not use the Display Pattern on the Relationship Schema. 

All relationship information in the view mode of a Content Item is hard-coded and does not consider Display Patterns.

Single Relationship

One item can be related. Examples are:

• one employee image for a person

• one hero shot for a campaign

• one logo for a company

Multi Relationship

Multiple items can be related. Examples are:

• different angles of a product (e.g., front view, top view, side view)

• featured images in press kits

• screenshots for FAQ

• related or featured products

Display & Handling

The relationship field items are displayed as a list or thumbnails small or medium. The elements can be re-arranged if you have edit permissions on the Content Item and view permissions on the related Content Items.

Permissions

Inside a relationship field, the Content Item permissions apply. For example, if you have a user who cannot view a Content Item in a relationship field, they will get this view:

However, double-clicking on that field will allow them to view the relationship details - when the layer is visible thanks to the "view for all" permission on the relationship schema.

Examples

On a Content item for a product, you might have a Relationship field for product photos. In your relationship schema for this field, you might have a single field for "View" that is, in turn, assigned to a List that provides the values Front, Top, and Side.

When a user relates a photo to the product Content Item, the field for "View" would appear, enabling the user to define the context of the related image. When the Content Item was published, this contextual information would be available.

Another valid approach is to use the Relationship field to relate creative files. Whether you are linking the zip package or individual files is up to you. 

In addition, your relationship schema could include fields for Caption or any other context information about the related content.