Email
Description
An email address associated with a party. Parties can have multiple email addresses of different types, and they have current and former email addresses.
Label
:Email
Properties
| Property | Description | Type |
|---|---|---|
| id | Unique identifier, a uuid | string |
| type | see below | string |
| the email address | string | |
| primary | boolean | |
| createdBy | the person or process that created the node | string |
| createdDate | dateTime | |
| modifiedBy | the person or process who last modified the node | string |
| modifiedDate | dateTime |
Below are the email address types that are valid in the type property, e.g., { type: "Home"}.
| Type | Notes |
|---|---|
Home | Personal email address at a Party's residence / @deprecated |
Work | Work email address |
CorpHQ | |
Main | |
Personal |
Parties can have multiple email addresses of various types, any number of which can be active at one time and of course no limit to the number of inactive email addresses. Parties can only have one primary email address (primary set to true) per each type.
Relationships
The HAS_EMAIL relationship connects parties to email addresses, and uses the standard relationship properties.
Examples
cypher
MATCH (party:Party { id: $id })
MERGE (party)-[rel:HAS_EMAIL {
active: true,
private: false,
fromDate: date()
}]->(email:Email {
type: "Work",
email: "john@gmail.com",
primary: false
})
RETURN party.id,
party.name,
email{.*}