---
title: "Naming Conventions"
canonical: "https://docs.vaultspeed.com/space/VPD/3010101313/Naming%20Conventions"
format: markdown
---
**Table of Contents**

> Macro (toc)

On the **Naming Conventions** screen, you can change the names of **HUB** and **LINK** objects as needed. The names of **Satellites on HUB** and **Satellites on LINK** objects will be adjusted automatically based on their parent object.

The **Short Name** is used for creating **Link** table names, while the **Abbreviated Name** is used for **Satellite, HUB, and Hash Key Attribute** names.

### Naming Convention Example

When naming objects, follow these conventions:

- **Short Name:** `ADDR`
- **Abbreviated Name:** `ADDRESS`

This results in the following object names:

- **HUB:** `HUB_ADDRESS` (based on the Abbreviated Name)
- **SAT:** `SAT_<src>_ADDRESS` (based on the Abbreviated Name)
- **LNK:** `LNK_xxx_ADDR` (based on the Short Name)
- **LKS:** `LKS_<src>_xxx_ADDR` (based on the Short Name)

### HUB

1. Click on a **Data Vault Release** and go to the **Naming Conventions** tab.
2. In the **HUB** submenu, select **Edit** from the **Actions** menu.
3. Modify the **Object Short Name** and/or **Object Abbreviated Name**.

![image](media://02edae6e-77e6-41c2-a734-7f8a29cee869)

4. Click **Save All** once ready.

> 📝 **Note:** 
> 📝 
> 📝 Changing the **Short Name** of a HUB will also update the names of related **Relation-Based Links**.

### Object Based Links

Object-Based Links define relationships between multiple HUBs based on shared attributes. These links automatically group source entities and generate names based on predefined conventions.

The second submenu is **Object-Based Links**, which includes:

- **Many-to-Many Links**
- **Hierarchical Links**
- **Same-as Links**

The table below shows how VaultSpeed applies naming conventions to object-based links. Each row represents a different link, with columns for the object name, short name, abbreviated name, and its source entities.

![image](media://357e96ef-7561-45e8-b9f8-4113247ed164)

Editing these names follows the same process as for **HUBs**.

When multiple source entities exist, VaultSpeed automatically groups them into a single object-based link. The default name of this link is determined by the first source entity encountered when the link is created. However, hub grouping can unexpectedly trigger this automatic link grouping. If an object-based link appears missing or incorrectly named, check whether hub grouping has caused automatic grouping.

In such cases, the names of the satellites are derived from the source entities’ names. For example, if two many-to-many entities are defined as object-based links and both represent a relationship between *party* and *contact*, but one entity is named *customer* and the other *prospect*, the generated data vault model will include:

- `lds_party_contacts_customer`
- `lds_party_contacts_prospect`

> ℹ️ #### Considerations During Development
> ℹ️ 
> ℹ️ Before a production release, the name of a ***Satellite on Link*** (Sat on Link) may change if additional groups are added. Be aware of this potential change, as it can impact naming consistency in the data vault model.

### Relation Based Links

Modify the **Attribute Short Name** for Link names in these cases:

- **Multiple relationships** between two **HUB** objects → The **foreign key field’s Short Name** is added to ensure uniqueness.
- **Self-referencing HUB** → An indicator is added to specify the relationship field.

![image](media://a78341aa-48aa-427f-97de-56ec0e91d8d3)

### Non-Historical Links

The **Non-Historical Links** submenu displays all non-historical links. 

To rename a **Non-Historical Link**:

1. Click **Edit** in the menu.
2. Click **Save** when done.