This article explains how you create a new content store and adjust its settings in the Content Store back end. 

Note! Only users with an assigned administrator role can access the Content Store back end in the Web Portal.

To set up a new inriver Content Store

1. Go to the Web Portal > Content Store to set up, delete, and manage your Content Store sites.
2. Click the +Create Content Store button to create a new content store.
3. Once the new content store is created, proceed to set up details such as Channel, Data Transfer Configuration, and Settings. See below for detailed information. 

Inriver Content Store configuration

Below is a list of the details you need to set up in the back end when creating a new content store.

Channel

Under Channel, select a channel from the dropdown menu. Note that the channel has to be published and that it has to contain channel nodes with entities for anything to be visible in the content store where your users log in.

Note! We currently only support one channel per content store. 

Data transfer configuration

Under Data transfer configuration you set up what data you want to make available on your content store site.

Excluded entity types

Excluded entity types allows you to exclude entity types from being displayed on your content store site. You may, for example, want to show products and items, but not tasks. Check the checkbox for the entity types you don't want to display.

Note! You must always include the Channel and Channel Node entity types. They are mandatory for the content store to work properly.

For entity type

For entity type allows you to select an entity type that is available for viewing in the content store. For example, select Product to define and set up the Product entity type for viewing.

Excluded field types

Excluded field types is where you select the fields you do NOT wish to display on the content store site. Fields that may be relevant to you but not to your retailer can be excluded here.

Searchable field types

Searchable field types displays the fields that were not excluded in the Excluded field types field. You can use the Searchable field types to select which fields a user should be able to perform a search on. Note that the fewer fields you choose, the faster the search will be.

MultiSearch field

MultiSearch field allows you to select a field that you can use to make multiple searches at the same time. For example, if you have selected Product Number as your multi search field, you can search for several specific product numbers at the same time, as long as they are separated using the CSV separator defined in the Settings for this content store.

Search string example: 12345;56789;90123;34567 This search will show four entities in your search result view.

Filter field types

Filter field types allows you to select which fields are displayed in the top menu in the Content Store front end. The fields can be used to filter the content, making it easier for Content Store users to select a part of the assortment in a content store.

Read about how to configure filtering field types in this article.

Excluded link types

In the Excluded link types field, you cannot exclude Channel and Channel Node links, as this will disrupt the display of entities.

Languages

Languages is where you select which data languages that should be visible on the content store site.

Resource format

Resource format is where you select which Image Configuration to use for catalogs and downloads on the content store site.

Rename fields

Rename Fields is where you can create a mapping for the display name on a particular field of a selected entity type. For example, if you have a field called "Market" on your Product entity type, but you want to display "Country" on the content store site instead, follow the below instructions:

1. In the Web Portal > Content Store > Data transfer configuration, click the Edit icon next to Rename fields.
2. In the Edit pop-up, click +Create new mapping.
3. Select entity type and select which field you want to give a different name. Enter the field name you want to change to and click Create. 
4. Click Save in the upper right corner of the pop-up to save your changes.

File output naming

File output naming allows you to modify the name of the output folder and file. The name is concatenated, using entity type fields, and delimited using one of the predefined characters.

It is possible to have a maximum of five field types in the concatenated name. For example, if you want to change the name of the output files, follow the below instructions:

1. In the Web Portal > Content Store > File output naming, click the Edit icon next to Configure file output naming.
2. In the Edit pop-up, select an entity type from the drop-down list.
3. Click Add field type for either File name or Folder name. 
   • It's possible to create the file and folder output names at the same time.
4. Select one field from the drop down list.
5. Click Save to save your changes.

Name

Name is where you can edit the name of the content store, for example, in case the name is misspelled or unclear.

Defaule entity types

Default entity types is where you check the entity types you want to display per default on your content store site. Default entity types appear automatically when you search and you have to deselect it if you don't want the system to search for that particular entity type. Typically, only one entity type is selected in this field, for example, Product.

HTML templates

HTML templates is where you select which HTML templates to use for a particular content store site. The HTML templates generate the PDF files you can download from the content store site, for example, they make it possible for your retailers to create customized catalogs.

Note! You have to create the content store site first, then go to Control Center > HTML Templates to enable the HTML templates you want to use for that content store. Read more about Content Store HTML Templates in this article.

CSV separator

CSV separator is where you define the character you want to use as a separator between field values in a CSV file. You can choose between Semicolon, Comma, Pipe, Tab, and Space.

Note! If you plan on opening the CSV file in Excel, the you should always use Semicolon (;) for content stores in EMEA and Comma (,) for USA.

Background color

Background color is where you define, in HEX format, the background color of the header areas and structure areas. Example: #336699 or #44ffcc

Text color

Text color is where you define the color of the text that lies on the Background Color. Example: #ffffff or #2b2b2b

Logo image

Logo image is where you can upload an image, often your company's logotype or similar. The image will be displayed as an icon in the upper left corner of the content store site. Note that the file size of the image can be maximum 1024kb. It is preferable that you use a .png image with a transparent background.

Advanced

Advanced is where you configure the system to export structured SKU data from an entity into fields in the CSV export file. Content Store supports structured SKU data in the same formats as Syndicate does, read more in this article.

Add the name of the FieldTypeId in your marketing model that holds the SKU data in the SKU field type and the tag names you want to export in the SKU output fields. If there are multiple fields, separate the fields you add with a semicolon.

The SKU fields will only be visible when exporting data to a ZIP file. Example: SKU Field type: "ItemSKU", SKU output fields: "ItemEAN;ItemSize". It is also possible to change each SKU field output name by setting the SKU output fields to: "ItemEAN=EAN;ItemSize=Size", no spaces in the new names though. 

Note that the fully structured SKU field cannot be excluded from the fields to Content Store, and will be visible when opening the product or item in the UI.

You can also click Edit custom code to personalize each content store with custom scripts. Read more in this article.

Further reading

Inriver Content Store

Sorting the cart in inriver Content Store

Accessing inriver Content Store

Personalizing an inriver Content Store with custom scripts

Publications in inriver Content Store

Setting up inriver Syndicate to work with structured SKU data