Primordial records

Primordial records are created automatically and should not be modified by the user.

When an Endeca Server data domain is created, a group of system records, called primordial records, is created automatically within the Dgraph. These primordial records are used internally by the Dgraph and their configuration should not be changed by the user. Changing their configuration may cause parts of the system to fail to work or to work incorrectly.

The purpose of these primordial records is to define system properties that will, in turn, be used to define user-created system records, such as PDRs and CDRs. For example, the mdex-property_Type record defines the configuration for the mdex-property_Type schema attribute, which is one of the various properties that define a PDR for a standard attribute.

The primordial records in the system are:
Primordial record Purpose
CDR (defines the schema for collection):

mdex-collection_Key

mdex-collection_PropertyKey

mdex-collection_UniquePropertyKey

system-collection_Description

system-collection_DisplayName

Define properties of a Collection Description record (CDR). A CDR, in turn, defines the characteristics of collections, such as their spec.
GCR (defines global configuration):

mdex-config_Key

mdex-config_MergePolicy

mdex-config_SearchChars

mdex-config_SpellingDValMaxWordLength

mdex-config_SpellingDValMinWordLength

mdex-config_SpellingDValMinWordOccur

mdex-config_SpellingRecordMaxWordLength

mdex-config_SpellingRecordMinWordLength

mdex-config_SpellingRecordMinWordOccur

mdex-config_SystemRecordVersion

Define properties of a Global Configuration Record (GCR). A GCR, in turn, defines global configuration parameters, such as spelling configuration.
DDR (together with a PDR, defines a managed attribute):

mdex-dimension_Key

mdex-dimension-value_Spec

mdex-dimension-value_Parent

mdex-dimension_EnableRefinements

mdex-dimension_IsDimensionSearchHierarchical

mdex-dimension_IsRecordSearchHierarchical

system-dimension_DefaultValue

Define a Dimension Description Record (DDR). A DDR, together with a PDR, in turn, defines properties for managed attributes. For example, a DDR defines a primary key for the managed attribute, its spec and its parent, and whether it should enable refinements to be displayed.
MAVDR (defines a managed attribute value):

mdex-dimension-value_Dimension

mdex-dimension-value_Name

mdex-dimension-value_Rank

mdex-dimension-value_Synonyms

Define properties of a Managed Attribute Value Description Record (MAVDR). A MAVDR, in turn, defines characteristics of managed attribute values, such as their display name, as well as rank and synonyms (if they are present).
PRDR (defines a precedence rule):

mdex-precedenceRule_Key

mdex-precedenceRule_IsLeafTrigger

mdex-precedenceRule_TargetAttributeKey

mdex-precedenceRule_TriggerAttributeKey

mdex-precedenceRule_TriggerAttributeValue

Define properties of a description record that defines precedence rules. This record, in turn, defines characteristics of precedence rules, such as the spec for the precedence rule, its trigger's spec and value, its target spec and value.
mdex-property_ForeignKey Not used (reserved for future use).
PDR (defines a standard attribute and a managed attribute):

mdex-property_Key

mdex-property_DisplayName

mdex-property_IsPropertyValueSearchable

mdex-property_IsSingleAssign

mdex-property_IsTextSearchable

mdex-property_IsUnique

mdex-property_Language

mdex-property_TextSearchAllowsWildcards

mdex-property_Type

system-navigation_Select

system-navigation_ShowRecordCounts

system-navigation_Sorting

system-property_DefaultValue

Define properties of a Property Description Record (PDR). A PDR represents characteristics for standard attributes. Note that:
  • PDRs, in addition to defining standard attributes, also define managed attributes (together with DDRs).
  • mdex-property_Key is also used to add standard attributes to attribute groups.
EDR (defines an entity):

mdex-semanticEntity_Key

mdex-semanticEntity_Attributes

mdex-semanticEntity_Definition

mdex-semanticEntity_Description

mdex-semanticEntity_DisplayName

mdex-semanticEntity_Groups

mdex-semanticEntity_IsActive

mdex-semanticEntity_Metrics

system-group_DynamicContent

system-group_DynamicOrder

Define properties of an entity description record, which, in turn, defines characteristics for entity records.
FRDR (defines a filter rule):

system-filterRule_Key

system-filterRule_DisplayName

system-filterRule_IsActive

system-filterRule_SourceCollectionKey

system-filterRule_SourcePropertyKey

system-filterRule_TargetCollectionKey

system-filterRule_TargetPropertyKey

Define properties of a Filter Rule Description Record (FRDR), which in turn defines filter rules.
GDR (defines an attribute group configuration):

system-group_Key

system-group_DisplayName

Define properties of a Group Description Record (GDR), which, in turn defines attribute group configuration.
GMDR (defines attribute group membership):

system-group-membership_Key

system-group-membership_GroupKey

system-group-membership_Position

system-group-membership_PropertyKey

Define properties of a Group Membership Description Record (GMDR), which in turn defines attribute group members.
system-navigation_RecordSource Used in the definition of various types of primordial records.
system-parentPipeline*

system-pipeline*

Define the various schema records for the Data Enrichment module. The Data Enrichment module is packaged with the Endeca Server and is used with Studio.

Listing primordial records

You can list the primordial records with: