...
Icon | |||||
Behavior | Its a view only field. The administrator who creates the field defines the search criteria e.g. product id = 123. The field will then show all Content Items that match this search criteria. Content that is not permitted to view will be greyed out. You cannot edit the field in single or batch edit mode. | ||||
Batch Actions:
| Related content items can be downloaded all together or placed all together into the basket, for further processing e.g. for editing or sharing. Additionally, each individual item can be downloaded directly or added to the basket. | ||||
Limitation | Dynamic View Fields are not editable - neither in Single nor in Batch Editor! The field is therefore also not available in filters or search. The content shown in the field depends on the field filter configuration. | ||||
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 not considering Display Patterns. | ||||
Multi Relationship | Multiple items can be related. Examples are:
| ||||
Display & Handling | The relationship field items are displayed as a list, or thumbnails small or mediumdynamic view shows item in a light version of the Content Browser, with list and thumbnail view. 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 that cannot view a Content Item in a relationship field he will get this view: However, double-clicking on that field will allow him to view the relationship details - when the layer is visible and 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. Wether 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. |
Relationship Value Handling
...
Picturepark Setup Example
...
Fieldpath
...
corporateInformation.corporateLogo
...
Advanced search for field
...
_exists_:corporateInformation.corporateLogo
Finds all Content Items with a Logo assigned in the Relationship Field "Corporate Logo."
...
Use in Display Pattern
...
Filter by label (Content by label) | ||||||
---|---|---|---|---|---|---|
|
...
Returned field value options
Single:
...
targetId (related item)
...
targetDocType (type of related item e.g. content)
...
relationType (Id of the relation selected)
...
sourceDocType (original item)
...
Field Id from relationship schema
...
targetId (related item)
...
targetDocType (type of related item e.g. content)
...
relationType (Id of the relation selected)
...
sourceDocType (original item)
...
Field Id from relationship schema
...
Value in field
...
Returned field value
...
Dynamic View Value Handling
This is just a view, no values can be extracted from business rules or in display pattern.
Dynamic View Field Settings
Name |
| ||||||
ID |
| ||||||
Single item relationship | Allowing one or multiple data entries into the Relationship Field. You cannot change this setting once saved. | ||||||
Relationship name | The name of the relationship you create when assigning a Content Item. | Relation ID | Constructed from the name by removing spaces and special characters. Relationship type | The type of items you can assign in the Relationship Field. Currently limited to Content Items only. Relation | The underlying schema used to insert information about the relation e.g., a schema with two fields for legend title and description, which you must fill out when relating a hero shot. |||
Item filter | Limit the Content Items available for selection by using a filter e.g., only show logos. | ||||||
Minimum | Only whole numbers (integers) are supported. By adding a minimum value, you set the field required. | ||||||
Maximum | Setting the maximum value to one turns a multi-item relationship to a single item relationship; however, we recommend to choose a single item relationship instead. | ||||||
Required | This allows ensuring that at least one item is always related e.g. for press kits the hero shot or the logo. The minimum value fulfills the same purpose, but we recommend using the correct required flag for the desired required option. Filter template | You can add a filter here to find the related items.
| |||||
Sort | You can select the metadata value that should be used for sorting the Content Items in the Dynamic View. | ||||||
Display Settings | |||||||
Default view | Select the default view for related items:
Large thumbnails are not available as they would not fit into the small view. | ||||||
List view maximum rows | Select the maximum rows that should be displayed in the list view. The default is set to 4. | ||||||
Thumbnail view maximum rows | Select the maximum rows that should be displayed in the thumbnail view. The default is set to 2. | Include in filters | Picturepark uses indexing settings from the relation schema. |||||
Include in search | Keep in mind that Picturepark does not index metadata of the related content e.g., all the Product Information or an assigned Media Type. Only the relationship information given on the assignment of a Content Item is indexed. | ||||||
Boost value | Include Page | | TERMS:Boosting | TERMS:BoostingShow the related Content Items in the download window. |