Images and files

InRiver Resource Entity

Images (and files) in InRiver are represented with a entity called "Resource" and this entity need to have special field names and types.

Following is a extract from InRiver documentation
"...
Field Types for Entity Type Resource with datatype in parenthesis. The Resource Entity Type have some special requirements on which Field Types to create, because it is tied to special logic making it possible to upload image files into the database that will be associated with the Resource entities.

• ResourceFileId (File). This Field Type must be present on the Resource Entity Type. It represents an Id to associate this entity to a file in the database, the value will be set automatically during the upload process. Boolean properties set to true: ReadOnly. Category: ResourceGeneral
• ResourceFilename (String). This Field Type must be present on the Resource Entity Type. It represents the filename of the uploaded file and will be set automatically during the upload process. Boolean properties set to true: ReadOnly. Category: ResourceGeneral
• ResourceMimeType (String), This Field Type represent a technical property extracted from the image file during the upload process. Boolean properties set to true: ReadOnly. Category: ResourceGeneral
• ResourceName (LocaleString). Boolean properties set to true: Display Name. Category: ResourceGeneral
  ..."

Image/file field mappings

Litium Studio InRiver Connector uses the InRiver linkType as the image(or file) field in the product group and article templates according to following scheme.

1. ItemResource InRiver LinkType will result in image (or file) fields created in article template, with variant group field attribute set to false.
2. ProductResource InRiver LinkType will result in image (or file) fields created in article template, with variant group field attribute set to true.
3. ChannelNodeResource LinkType will result in image (or file) fields created in product group template, with variant group field attribute set to false.

For each image mapped, the field name used is the inRiver LinkTypeId prefixed with a number starting from one(to denote the number of images). The sort order of images will be the same as in inRiver. (in inRiver connector versions before 3.0 the prefixed number starts at 0).

Following is a example showing image fields generated for a custom link type called CategoryDisplayImage

Number of Images/Files

By default the number of images transfered is limited to 1, and only one Litium Studio property field is created.

This means that only the first image linked to an InRiver entity will be transfered by default.

To have multiple images do one of the following:

1. Add a InRiver field setting with name = LsMaxNoOfImages to any field of the Resource entity, and set its value to desired number of images. This increases the number of images for all linkTypes.
   
    
2. Set the number of images in the Connector Setting "No. of images by Resource LinkType". You can specify the no of images for multiple resource link types as a comma seperated list.
   e.g. ProductResource:2, ItemResource:3, ChannelNodeResource:1
   
   
    
3. If both 1. and 2. above are specified for a given link type, the value specified in 2.connector settings takes precedence and will be used instead of value specified in 1.

Media archive

All images are placed into the media archive folder named "InRiverResources". The file name is the inRiver entity id followed by the extension. The inRiver fields of the resource entity are transfered as meta data to a particular image.