Note: The integer IDs below correspond to the ReferenceID element in CompoundIdentifiers
Note: This list supersedes, as of 20150128, the Work Record material in a previously circulated Excel.
Note: The WorkRecord describes a single pass over a single field
Attribute | Type | Multiplicity | Description |
---|---|---|---|
Id | CompoundIdentifier | 1 | Unique identifier (reference integer & associated other unique IDs) |
PlanIds | Integer | 0..* | A list of Document references indicating which documents resulted in the creation of this work item |
RecommendationIds | Integer | 0..* | A list of Document references indicating which documents resulted in the creation of this work item |
WorkOrderIds | Integer | 0..* | A list of Document references indicating which documents resulted in the creation of this work item |
NoteIds | Integer | 0..* | Unbounded note field objects |
TimeScopeIds | Integer | 0..* | Note how this will include:
|
Priority | Enumeration | 0..1 | Immediately / SoonAsPossible (no due date) / High / Medium / Low? Some kind of scale? |
Season | TimeScope | 1 | The season the work item should be performed in |
PeopleRoleIds | Integer | 0..* | A list of IDs of PeopleRole objects that describe "who" is involved and what their role is in the collection of data. |
GrowerId | Integer | 0..1 | A reference to the Client/Grower to use for the work (This is meant to reflect the "business entity") |
FarmId | Integer | 0..1 | A reference to the Farm to use for the work |
FieldId | Integer | 0..1 | A reference to the Field to use for the work |
CropZoneId | Integer | 0..1 | A list of CropZone references. 20150205: The multiplicity of 0..n is counter-intuitive. This was probably derived from the user story about multi-variety planting operations. In this case, the link between the multiple cropzones and the corresponding operations does not happen directly through this list, but through the presciption object. 20151020: Changing 0..n to 0..1 to avoid cans of worms like having to change the relationship between Prescriptions and Cropzones. This also maximizes compatibility with ISOXML, where tasks have a scope of 1 part field. |
MachineId | Integer | 0..1 | A reference to the Machine to use for the work |
SpatialLayerIds | Integer | 0..* | A list of spatial layers needed to do the work (e.g. VarietyLocator layer) |
FieldBoundaryId | Integer | 0..1 | A reference to the field boundary to use for the work |
WorkItemOperationIds | Integer | 0..* | A list of WorkItemOperation references that define various objects to use with a given operation |
GuidanceIds | Integer | 0..* | A list of guidance objects to be used for the work |
StatusUpdates | StatusUpdate | 0..* | Defines the current status of the work item via StatusUpdate objects |
StatusUpdate
asdasdd