Assignment
Description
:Assignment encapsulates the details of a client's representation agreement in a specific area of expertise and potentially within certain geographic regions. It acts as a nexus connecting clients, representation areas, geographic coverage, and assigned employees on the client team.
Temporal properties on relationships allow tracking of changes over time without cluttering the node with time-bound data.
Label
:Assignment
Properties
| Property | Description | Type |
|---|---|---|
| id | A unique identifier for this Representation node | string (uuid) |
| teamRole | the role of the team member in this representation | 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 |
Valid team roles include:
| Role | Description |
|---|---|
| Responsible Agent | The primary agent responsible for this client (some groups call this Point Agent) |
| Agent Team | A team of agents representing the client |
| Lead Agent | One of the agents on the client team |
| Supporting Agent | Assisting lead and responsible agents on the team |
| Coordinator | Coordinator working with the client team |
| IQ Exec | Usually used in pursuits, this is an IQ Executive that is attached to the pursuit |
| Business Affairs | Business Affairs agent, if applicable |
TODO
The list of roles is not yet complete. We need to work with the business to understand the roles that are important to them.
Key
id
Relationships
The HAS_ASSIGNMENT relationship connects employees to :Assignment nodes.
The HAS_GEO_AREA relationship connects :Assignment nodes to :GeoArea nodes. This is how the geographic scope of a particular team member's assignment is defined -- commonly as a territory. For example, "This agent represents the client as a Musician in the United States."
The ASSIGNED_TO relationship connects :Assignment nodes to :Representation nodes.