Role

Description

A role defines how the party acts within the context of the UTA business environment. A party can perform many roles with UTA, and they can become active and inactive over time.

Label

:Role

Properties

Property	Description	Type
id		string
name	the name of the role; see table below	string
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

The valid role names are:

Role	Description
Buyer	The person or organization paying for client services, or paying UTA directly, such as in a consulting services relationship.
Client	Designated by UTA leadership as a client. Usually appears on various official client lists. Can be a person or an organization (both formal, such as a corporation, or informal, such as a writing team). Clients are paid for services, usually by buyers, and UTA works on their behalf.
Talent	A person or organization UTA does not currently represent but they may either pursue or track in some manner
Employee	A UTA employee
Agency	A non-UTA talent agency.
Contact	A person UTA knows about that does not have a specific role.
External	A person or organization that has registered with us for a UTA ID, in order to use our applications and services
Sport Organization	A sports organization such as a league, conference, or association.
Sport Team	A sport team

Key

Roles are uniquely identified by a name property the name property; e.g., (:Role { name: "Client" }).

Relationships

Parties are attached to roles via a relationship called :HAS_ROLE.

A trivial example is a list of all of UTA's band clients and their members:

Get a list of all of UTA's band clients and their members

Examples

Get a list of available roles

MATCH    (role:Role)
RETURN   role.name
ORDER BY role.name

Get a list of active clients

MATCH       (p:Party)
        -   [:HAS_ROLE { active: true }]
        ->  (:Role { name: "Client"})
RETURN      p{.*}