Content Definition Naming Restrictions

When creating content definitions in Nomad Media, there are specific naming restrictions that must be followed to avoid conflicts with system-reserved names and internal functionality.

Overview

Content definitions and their fields cannot use certain reserved words that are used internally by the Nomad Media system. Using these reserved names will result in validation errors when attempting to save the content definition.

Reserved Content Definition Names

The following names cannot be used as content definition names (case-insensitive, spaces removed):

Reserved Name	Description
ASSETMETADATA	Reserved for the Asset Metadata content definition
CONTENTTYPE	Reserved for internal content type management
FIELD	Reserved for field type definitions
HTTPHEADER	Reserved for HTTP header configuration
PAGE	Reserved for page content types
TEMPLATEPACK	Reserved for template pack management

Validation

When creating a new content definition, the system validates that the title (with spaces removed and converted to uppercase) does not match any of these reserved names. If a match is found, you will receive an error:

"{Title}" is a reserved Nomad internal table, please pick a new name

Reserved Field Names

The following field names cannot be used for content definition fields (case-insensitive):

Asset & Media Properties

ASSETSTATUS
ASSETTYPE
ASSETTYPEDISPLAY
ASSETID
SOURCEASSETID
THUMBNAILASSETID
PROXYAUDIOASSETID
PROXYIMAGEASSETID
PROXYVIDEOASSETID

Audio Properties

AUDIOBITDEPTH
AUDIOBITRATE
AUDIOBITRATEDISPLAY
AUDIOBITRATEMODE
AUDIOCHANNELS
AUDIODURATION
AUDIODURATIONDISPLAY
AUDIODURATIONSECONDS
AUDIOFORMAT
AUDIOFRAMECOUNT
AUDIOFRAMERATE
AUDIOSAMPLINGRATE
AUDIOTRACKCOUNT
AUDIOTRACKS
PREVIEWAUDIOURL

Video Properties

VIDEOBITRATE
VIDEOBITRATEDISPLAY
VIDEOBITRATEMODE
VIDEOCODECID
VIDEOCOLORSPACE
VIDEODURATION
VIDEODURATIONDISPLAY
VIDEODURATIONSECONDS
VIDEOFORMAT
VIDEOFRAMECOUNT
VIDEOFRAMERATE
VIDEOFRAMERATEMODE
VIDEOHEIGHT
VIDEOOVERALLBITRATE
VIDEOPREVIEWURL
VIDEOROTATION
VIDEOTIMECODE
VIDEOWIDTH
HASVIDEO
HLSVIDEOURL
PREVIEWVIDEOHEIGHT
PREVIEWVIDEOWIDTH
PREVIEWVIDEOURL

Image Properties

IMAGEHEIGHT
IMAGETIMECODE
IMAGEPREVIEWURL
IMAGEWIDTH
IMAGEURL
PREVIEWIMAGEHEIGHT
PREVIEWIMAGEURL
PREVIEWIMAGEWIDTH
PREVIEWTHUMBNAILHEIGHT
PREVIEWTHUMBNAILWIDTH
THUMBNAILIMAGEHEIGHT
THUMBNAILIMAGEURL
THUMBNAILIMAGEWIDTH

Storage & File Properties

BUCKETTYPE
BUCKETNAME
CONTENTLENGTH
CONTENTLENGTHDISPLAY
CONTENTTYPE
ETAG
FILEEXTENSION
FILENAME
INTERNALURL
LOCALPATH
OBJECTKEY
ORIGINALBUCKETNAME
ORIGINALOBJECTKEY
S3URL
SLUGGEDOBJECTKEY
STORAGECLASS
STORAGECLASSNAME
STORAGEEVENTNAME
STORAGESOURCEIPADDRESS

Metadata & Processing

METADATAARCHIVEBUCKETNAME
METADATAARCHIVEPREFIX
METADATACONTENTBUCKETNAME
METADATACONTENTPREFIX
METADATATYPE
METADATATYPEDISPLAY
MEDIATYPE
MEDIATYPEDISPLAY
HASMETADATA
INDEXEDDATE
MOBIUSLABSFEATURESVIDEOID
MOBIUSLABSPREDICTTASKID
TWELVELABSTASKID
TWELVELABSVIDEOID

AI & Analysis

HASFACES
HASLABELS
HASTEXTANDPHRASES
FACEITEMS
LABELS
TEXTITEMS
TEXTCAPTIONS
DETECTEDLANGUAGE
DETECTEDLANGUAGESCORE
LANGUAGE
PERSONS
ASSIGNEDPERSON

Display & Preview

DISPLAYASPECTRATIO
DISPLAYDATE
DISPLAYNAME
DISPLAYPATH
HIGHLIGHTANIMATEDGIFURL
HIGHLIGHTDURATION
HIGHLIGHTTIME
HIGHLIGHTURL
HIGHLIGHTS
SCREENSHOTMILLIS
SCREENSHOTSFOLDERID
SCREENSHOTTIMECODE

Relationships & Hierarchy

HASCHILDREN
HASRELATEDASSETS
HASSUBFOLDERS
PARENTS
PARENTID
RELATEDASSETS
RELATEDAUDIO
RELATEDIMAGES
RELATEDVIDEOS

System & Technical

ID
CONTENTID
SOURCE
SOURCEID
SCHEMA
VERSIONNUMBER
STATUS
STATUSNAME
CREATEDDATE
CREATEDBYID
ENCODEDDATE
LASTMODIFIEDDATE
LASTMODIFIEDUSERNAME
LASTMODIFIEDUSERID
LASTMESSAGE
EXTERNALID
EXTERNALURL
URL
NAME
NAMELOWER
PERCEPTUALHASH
SCANTYPE
SEGMENTCOUNT
SEGMENTS

Live Streaming

LIVECHANNELID
LIVEINPUTID
PREROLLASSETID
POSTROLLASSETID
ADBREAKS
CHAPTERS
AVAILABILITY

Subtitles & Captions

HASSUBTITLES

Destination & Transfer

DESTINATIONID
DESTINATIONFOLDERID
STARTTIMECODE
ENDTIMECODE

Special Case Exceptions

There are a few special cases where certain reserved field names are allowed for specific content definitions:

User Content Definition

Field Name: STATUS
Content Definition ID: b42cb50a-1664-4b68-a8f8-2272b9b13e7c
Reason: The User content definition is the owner of the Status field

Asset Metadata Content Definition

Field Name: EXTERNALID
Content Definition ID: 5e66de08-a5b8-4b4c-a5ff-ed7e605823e3
Reason: Required for Brightcove integration

Event Content Definition

Field Name: EXTERNALURL
Content Definition ID: 412a30e3-73ee-4eae-b739-e1fc87601c7d
Reason: Required for event management

Best Practices

When creating content definitions and fields:

Check Reserved Names: Always verify that your proposed field name is not in the reserved list above
Use Descriptive Names: Choose field names that clearly describe their purpose
Avoid System Prefixes: Don't use prefixes like has, is, display, preview, metadata unless necessary
Case Insensitive: Remember that validation is case-insensitive, so AssetStatus, assetstatus, and ASSETSTATUS are all blocked
No Spaces in Validation: For content definition names, spaces are removed before validation

Error Messages

Reserved Field Name Error

If you attempt to use a reserved field name, you will receive:

The field {fieldName} is a reserved system name. Please choose a new name.

Reserved Content Definition Name Error

If you attempt to use a reserved content definition name, you will receive:

{Title} is a reserved Nomad internal table, please pick a new name

Field Type Mismatch Error

For Asset Metadata content definitions, if you try to use a field name that already exists with a different type:

The field {fieldName} already exists with a different type. Please choose a new name or make sure the type matches.

Additional Validation Rules

Asset Metadata Content Definition

The Asset Metadata content definition has additional restrictions:

Supported Field Types Only: Only specific field types are allowed (Asset Selector, Short Text, Long Text, Date, Time, Lookup Dropdown, Lookup Multi-Select, Checkbox, Related Content Definition, Number, Image Selector)
No Type Mismatches: Field names must not conflict with existing fields of different types across other content definitions
No System Field Names: Cannot use field names that are already used as system fields in other content definitions

Summary

When creating content definitions in Nomad Media:

6 reserved content definition names to avoid
Over 170 reserved field names to avoid
3 special case exceptions for specific content definitions
Case-insensitive validation for all names
Additional restrictions for Asset Metadata content definitions

Always consult this list before creating new content definitions or fields to ensure compliance with Nomad Media's naming restrictions.