Add a Custom Field

Home > selected Project > menu or right-click > Settings > Custom Fields > New Custom Field
Project > Settings drop-down > Project Settings >Custom Fields> New Custom Field

Requires Project - Custom Fields - View, Add Permissions

Home > selected Organization > menu or right-click > Settings > Custom Fields > New Custom Field
Project > Settings drop-down > Organization Settings > Custom Fields > New Custom Field

Requires Organization - Custom Fields - Add/Edit Permissions

Users in a role with the appropriate permissions can add a Custom Field to the Project Custom Fields list or Custom Fields template.

You may want to use Custom Fields when working with Load Files, such as DAT Load Files.

When you add a Custom Field, the Custom Field is included in other views that display metadata fields (for example, under the Available Metadata for configuration of Metadata View Fields,or at the end of the Digital Reef list for Export Fields).

Once a Custom Field is added, it cannot be edited or deleted.

Note: When working with Export Fields, keep in mind that no Custom metadata field mapping is permitted at the Organization template level. Use a Project Export Fields template to define all of the Custom field mapping for Export.

Add Custom Field Options

• Name The unique name of an item. For many items, the name can have up to 100 characters. Some items, such as a Connector name, can have up to 255 characters. An Excluded Content Block name is limited to 32 characters. (required) - The unique name for the Custom Field. When you add a Custom Field with a given name, the software automatically adds the prefix drcustom-. Note the following restrictions concerning Custom Field names:

The Custom Field name is subject to validation upon creation or edit. The name can include alphanumeric characters and some supported characters (such as a hyphen, underscore, and apostrophe). You can use uppercase or lowercase letters in the name and the software will normalize the name to lowercase for the purposes of search. During validation, the software will also allow characters from foreign languages (for example, Korean characters).

However, spaces as well as the following characters are not supported for Custom Field names:

! " # $ % & * + . / : ; < = > ? @ [ \ ] ^ { | } ~ “ ”

Specifying a space and/or any of the unsupported characters will generate the following error message:

Entry contains a space or one of these invalid character(s): ! " # $ % & * + . / : ; < = > ? @ [ \ ] ^ { | } ~“ ”

The length of a Custom Field name is also subject to validation upon creation or edit. An error message appears if you try to add or edit a Custom Field whose name exceeds the maximum number of characters allowed.

Note: You must search for a Custom Field using single quotes and lowercase using the 'drcustom-<custom_field_name>' format. This format requires you to place the Custom Field name search within single quotes and specify the name in lowercase, since the software normalizes a Custom Field name to lowercase.

• Description Provides a helpful description of an item. A description can have up to 255 characters. (optional) - A useful description of the Custom Field, if one was specified.

Custom Field Attributes

The following defaults apply to a Custom Field:

• The field database type is set to string.

• The field database length is set to 2147483647.

• The field token type would be untyped.

• The tokenization type would be standard with wildcard support. This means that the field content is lowercase and tokenized (that is, broken into words/terms, where each word is searchable, and you can use wildcards such as * or ?).

• The field content is stored in the index.