Content store

From VYRE

(Redirected from Data store)
Jump to: navigation, search

Content stores are used in Unify to define data models, and store items. A store can either be a data store, containing XML content, or a file store, containing a binary file. All stores also have metadata stored as XML.

Contents

Common features

Data store

A data store contains items, which have attributes, and are stored as XML.

File store

A file store contains a binary file stored on the filesystem.

Other names

Content stores are sometimes referred to by different names in Unify. Other names include:

  • Store
  • Collection Schema
  • Schema

Configuration Page

file-store edit page in 4.8
data-store edit page in 4.8

The backend edit page is divided into 7 sections.

  • Edit a Data/File Store
  • Collection Languages
  • Remote Indexing
  • Recording Configuration
  • XML Mapping
  • Upload File Restrictions
  • Core Attributes

Edit a Data/File Store

The label might sound strange but this section essentially contains ungroup information and core data for an collection schema. The fields are:

  • Name: Name of the collection schema, the must be a unique name. This field is Mandatory.
  • Description: Description of the collection schema. This field is Mandatory.
  • Access control: Should the collection schema be accessed control. If enabled logged in users with the correct permission can view and edit the items in the store.
  • Update derived files every time an item is checked in: This option is only available in the file-store. If enbaled it regenerates all the file service when an item is updated. It is a legacy feature that existed before Unify introduced conditionals in file services. We strongly recommend against enabling this functionality for two reasons:
    • it consumes massive amounts of the storage
    • previews/thumbnails may disappear in the frontend while the new derived files are regrenarated
  • Preview template: removed in Unify 4.7

Collection Languages

This section is used to configure the supported Locales/Languages. The fields are:

  • Primary Language: The primary locale, if you have multiple locales then this will be considered as the master locale and an item must be first created in the master locale before you can create it in another locale. This field is Mandatory.
  • Secondary collection languages: List of all the other secondary locales the collection schema will support. This restricts frontend users from creating items for arbitrary/unspecified locales.

Remote Indexing

This section is used to configure solr related information. The fields are:

  • User remote index for this store: this enables data from the collection schema to be stored in solr.
  • Remote indexing template: Also known as RIT. RIT is used to convert a unify item into Solr Documents. Which is used by Solr to index the data.

[Note]

Note

Solr needs enabled and configured in the content configuration module before unify to send data to it.

Recording Configuration

This section is used to configure the recording of the collection schema. The fields are:

  • Enable view recording: Enabling this option tells the system that it should record the view data of items from this collection schema if the item is viewed on an item display page.
  • Record total view count for the collection: This option tells the system that it should save the total view count for this store. The result of this can be viewed in Content Viewing. We do not see much benefit in this functionality and recommend not to use it. If you require this functionality we recommend using our business intelligence module.
  • File Store specific options:
    • Enable download (order) recording: Enabling this option tells the system that it should record the download data of items from this collection schema.
    • Record total download count for the collection: This option tells the system that it should save the total download count for this store. The result of this can be viewed in Content orderings. We do not see much benefit in this functionality and recommend not to use it. If you require this functionality we recommend using our business intelligence module.

[Note]

Note

The system will not record download/view data until you create a business intelligence configuration and enable recording on the site (and/or page level). This configuration is only a single step in three step process. For more information go to [confluence]

Upload File Restrictions

This is only available for file stores. It lets system admin select a configured upload file Restrictions that can be used allow/ ban files with certain extension.

XML Mapping

XML Name

This is only available for data stores. It is a legacy feature that allows system admin change the root xml element of the content section for a data item. If this value is changed then the data in all the existing items cannot be accessed via the Java API, edited or searched on via lucene. In 4.8, this field is only modifiable on create. It is strongly recommended not to change the default value from item.

XML namespaces

This option has been removed in Unify 4.8

Core Attributes

Introduced in 4.8. This section will hold configuration data directly related to all items. These fields are:

  • Name
  • Description
  • Keywords

These fields are not connection to content or metadata but exists for all item. This section contains:

  • index boost value
  • EXIT/IPTC mapping

Also see

Reporting

Personal tools