Each field has a set of attributes that affect how the field behaves. You set the settings when adding the field to a Layer or Virtual Type, so different instances of the same Field Type can behave differently, depending on their specific settings. There are some parameters that are common to all the field types. 

Name (required)

The setting "name" is available for various things in Picturepark e.g. fields, schemas, business rules. This value defines what appears in the Picturepark interface. You can change the name at any time, and translate it into any configured metadata language. If you would like to add a translation for the name, just press Add.

  • ID's and Name need to be the same or at least the same meaning.

  • Sentence-style capitalization e.g. Media type and not Media Type.

  • Schema names in plural e.g. products, events, persons for lists.

  • No numbers at the beginning of the ID (mediaType2 is correct but not 2MediaType)

ID (required)

The field id is the ID of your field, which is used to link to this field. The field id is always lowercase. The id of the field is set on the creation of a new field, using camel casing. You need the field id for the configuration of filters or display pattern. 

The ID is automatically created from the name you insert: 

  • Example: You insert the field name "My NeW fielDs #1 Purpose?

  • Automatic Id: myNeWFielDs1Purpose

You can open the Display Pattern Editor to see the JSON of a Content Item. 


Field Type

The type of field where you insert metadata, where Picturepark supports different data types e.g. text, numbers, or tags. You cannot change a field type once saved. You can only remove the field, update the index "Content and List Items" and re-add the field using another type. Field values on Content Items are lost after the deletion of a field, prepare an Excel Export to update affected Content Items after field removal and readdition.   

Required

The field setting "required" determines whether an editor must provide a field value before being able to save the Content Item. If a field is required and the user has not provided a value or has deleted an existing value, Picturepark does not permit saving the item. This value can be changed at any time. You cannot set a field required on a Layer that has XMP mappings defined for any field. 

Sortable

The field setting "sortable" for a field defines if Picturepark uses the values of those fields for sorting of List Items (in Lists). Sorting of contents based on fields in a Layer is possible via the channel configuration, which only considers fields marked as sortable. All fields except for Geo Point and Relationship fields are sortable. This can be changed after field creation. 


Include in Filters

The field setting “Include in filters” allows the field to be added as a filter for content (see Channels Configuration) and the field values to be edited in the Batch Editor (indexed fields). Picturepark checks this setting against the allowed number of Search-indexed fields in your subscription plan. While it may be tempting to include all fields in filters and simple search also boosting them, you may revisit this idea based on your subscription plan limit, and by testing your common search scenarios - too much values will not automatically result in better search results.

Include in Search

The field setting "Include in Search" determines whether the field's values should be considered in content browser simple search operations. If this option is not enabled, the search does not consider the values of the field in search operations. This can be useful, for example, if the field is used for internal discussions or work directives that you don't want to affect the search results. Picturepark checks those settings against the allowed number of Search-indexed fields in your subscription plan. While it may be tempting to include all fields in filters and simple search also boosting them, you may revisit this idea based on your subscription plan limit.

Boost Factor

The field setting "Boost" will boost the values in the search and helps you define the relevance of the content for your users. The boost parameter increases the relative weight of a term (with higher boost values) or decreases the relative weight (with lower boost values), but the increase or decrease is not linear. In other words, a boost of 2 does not result in double the score. You can select between 1, 10, 25, 50, 100, or 500. 

  • Boosting in a list is for the search in fields while tagging.

  • Boosting in layers is for the content browser search.

Picturepark checks this setting against the allowed number of Search-indexed fields in your subscription plan. While it may be tempting to include all fields in filters and simple search also boosting them, you may revisit this idea based on your subscription plan limit.