Nominations DB Architecture

Open

DB Architecture ERD diagram (ignore relations line symbols)

Design

This architecture was designed with Crop nominations in mind.

It was also thought that maybe this could be the basis for a platform wide change to pattern most actions done in Litefarm under a workflow > tasks > logs style architecture (to be proposed @Duncan Brain ).

Tables

nomination_type

DESCRIPTION: List of types. A nomination type will have only one workflow group.

nomination_type - Primary Key - String - notes: N/A

Example:

nomination

DESCRIPTION: List of nominations. A nomination needs a farm_id and a type but does not need an assignee.

nomination_id - Primary Key - Increments - Integer - notes: Linear-ish therefore integer

farm_id - Foreign Key - Not Null - UUID - notes: Consider removing. Necessary for hasFarmAccess(check).

nomination_type - Foreign Key - Not Null - String - notes: Consider using workflow_group instead.

Example:

nomination_workflow

DESCRIPTION: List of workflow groups and status names. Workflows groups many have different steps but same status.

workflow_id - Primary Key - Increments - Integer - notes: No particular order just an id

status - Unique(name, group) - Not Null - String - notes: N/A

type_group - Foreign Key -Unique(name, group) - Not Null - String - notes: N/A

Example:

nomination_status

DESCRIPTION: List of status changes. A status needs a timestamp

status_id - Primary Key - UUID - Integer - notes: Exponential-ish therefore uuid

nomination_id - Foreign Key - Not Null - Integer - notes: N/A

workflow_id - Foreign Key - Not Null - String - notes: N/A

notes - Nullable - Text - notes: N/A

BASE_OBJECT_ATTRIBUTES - notes: Consider removing updated_at and updated_by.

Example:

Not yet Implemented

Immutable Nominations

Consider the following table to hold the object: