Custom Field Data Types

Custom Field Data Types

Question

We're looking to create some custom fields and would like to know the differences between the various Data types.



Answer

There are multiple data types that enable administrators to create metadata schemas that can range from simple to very complex.

For more information about Custom Fields refer to this article: https://support.digitalhive.com/portal/en/kb/articles/adding-custom-metadata-fields

String - The most frequently used data type for Custom Fields. Typically used for when a single value Custom Field is required. For example, creating a Data Classification field to inform users about the type of data that they're working with. 



Array of Strings - This data type can be used when there are multiple values required for a Custom Field, or when a specific number of values are required. For example, assigning business stakeholders to content, where multiple business units must approve content before it can be published or marked as certified. Arrays can not be used as part of the metadata rules.(https://support.digitalhive.com/portal/en/kb/articles/adding-custom-metadata-fields#Creating_Rules_Based_Custom_Fields)

In this Custom Field definition, a Min items value of 2 was defined which means that at least two of the five available values must be set.



When a user edits the metadata on content, the schema will look like this:







Because the option for Categorization was enabled, when users search for content, and this piece of content is part of the search results, the facet will allow for each value to be used as a filter, not the union of the three.



Number - Similar to the Text data type, but used for numerical values, including decimals. One use case would be the ability to score content based on certain criteria. The number data type also allows users to leverage a slider control, which requires a minimum and maximum value to be set. 


Otherwise, values can be hardcoded, or users can be allowed to enter any value that require. In the UI, when setting the metadata value for a slider enabled number data type, the UI looks like this:


Once the value is set, it appears like this for users. 

Array of Numbers - Similar to the array of strings data type multiple values can be selected as part of the metadata values. In this example, a minimum of two values are required, with no more than 3 values possible. Also, there is a range specified which means that the provided values must fall within the range. Arrays can not be used as part of the metadata rules.(https://support.digitalhive.com/portal/en/kb/articles/adding-custom-metadata-fields#Creating_Rules_Based_Custom_Fields)



 In the UI, when setting the metadata value for an array of numbers data type, with a range specified, the UI looks like this:

Example of when there aren't enough values set to meet the Custom Field requirements.


When a number does not match the specified range (13 and -7 would be both be outside the desired range).






Integer - Identical to the Number data type, except that the Integer data type only supports whole numbers and thus does not provide a precision setting.

Array of Integers - Identical to the Array of Numbers data type, except that the Array of Integers data type only supports whole numbers and thus does not provide a precision setting.

Boolean - Another popular data type used when a Custom Field meets a certain requirement. When a Boolean data type is selected for a Custom Field, then the user will have a tri-state checkbox available to them.

The default state, which means that the field is not set:
 
The selected state, which means that the value is yes:

The unselected state, which means that the value is no:

A very common use for this data type is for indicating whether content has been certified or not. Here is a Custom Field definition for this type of usage.


When setting the metadata value for this Custom Field, this what the user would see:

Value hasn't been set yet.


Value has been set to Yes.


Value has been set.


Date - The Date data type is ideal for specifying a single date. This could be used to indicate when the content was first made available, when it becomes 'de-classified' or public, or when there is an expiry date on the lifespan of the object.

Like most data types, ranges are supported. Here is an example of a date Custom Field that only allows users to set expiry dates from January 1, 2024 through December 31, 2025. The format of the date value can also be configured.



 In the UI, when setting the metadata value for a date data type, with a range specified, the UI looks like this:

Custom Field value not set:


Clicking on the control and browsing to a date that is lower than the minimum date specified in the Custom Field definition (notice the values are greyed out):


A date value being selected:


Custom Field with a date value specified:


Array of Dates - Similar to an array of strings, but used for date values. The ability to specify a minimum and maximum of dates that can be used, as well as defining a date range is possible.  Arrays can not be used as part of the metadata rules.(https://support.digitalhive.com/portal/en/kb/articles/adding-custom-metadata-fields#Creating_Rules_Based_Custom_Fields)


    • Related Articles

    • Adding Custom Metadata Fields to Enhance Digital Hive Content

      Question Looking at the properties for a report, there is metadata visible from the content systems like Tableau, PowerBI, and IBM Cognos Analytics, but is it possible to create custom metadata values on a report or dashboard. The objective is to ...

    • Connecting PowerBI to Digital Hive Audit Data

      Question The Digital Hive Control Center doesn't seem to provide any reports or views around usage of the platform. Is there a way to create reports to show metrics like the amount of reports executed by platform, the number of searches being made, ...

    • Creating a Custom Color Scheme

      Question Within Digital Hive, we can manually change color values, or use predefined color schemes, but is it possible to create a color scheme that can be saved and reused in the future? Answer Custom color screens can be created by Digital Hive ...

    • Custom Sort Order for Digital Hive Folders

      Overview As of the 2024.3 Digital Hive release, it is now possible to create a custom sort order for contents within a Digital Hive folder. There are certain scenarios where alphabetical or time based sorting is not sufficient and a custom sort order ...

    • Set a Custom Thumbnail for Content

      Question Not all of my content has an automatically generated thumbnail but I would like to have a thumbnail appear for a specific report. Is it possible to configure a thumbnail for a specific piece of content? Answer Yes, as of the Digital Hive 2.1 ...