Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Note: The ints 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 what was done on ONE field.

20150519: This page uses "ID" after nearly everything; the other documents do not.WorkRecord Inherits multiple attributes from Document.

LoggedData is a subclass of WorkRecord

IdCompoundIdentifier

A human-readable description of the work record.

 Moved to Parking Lot - 20150519, Tarak Reddy (Deactivated), we use "Name" in Plan, Rec, Work Order; can we standardize to one of the two? Personally I prefer "Description".

A reference to the Season in which the work was done. Note how in this case we are handling the timescope by reference. This is to accommodate the possibility of, for example, efficiently searching for all the records in a given crop season. This is done differently for start / stop times.

 Moved to Parking Lot - A list of references to ContextItem objects
AttributeTypeMultiplicityDescription
MachineIdInteger0..1

32-bit integer ID, corresponding to the ReferenceID element in CompoundIdentifier.

Name

string1

A reference to the Machine used for the work

 R. Andres Ferreyra (Unlicensed):

StartEndTimeTimeScope1The date/time when the work was started / completed
EndDateTime (question)TimeScope0..1
  •  Moved to Parking Lot - 20150519, R. Andres Ferreyra (Unlicensed): Could we add this? It simplifies expressing the duration of tasks, and accommodates summary data more easily.
GrowerIdInteger0..1A reference to the Client/Grower used for the work
FarmIdInteger0..1A reference to the Farm used for the work
FieldIdInteger0..1A reference to the Field used for the work
CropZoneIdInteger0..1A list of CropZone references
PersonRoleIdsInteger0..*A list of IDs of PeopleRole objects that describe "who" is involved and what their role is in the collection of data.
MachineIdInteger0..1A reference to the Machine used for the work
CropSeason(question)Integer0..1

This should go under LoggedData, so WorkRecord can also work for Non-mechanical harvest and other things.

GuidanceAllocationIdsInteger0..*ContextItemIdInteger0..*

A list of GuidanceAllocation objects to be used for the work.

   R. Andres Ferreyra (Unlicensed)

, discuss with Tarak Reddy (Deactivated) / team that we use "CropSeason" elsewhere. Can we standardize?

 

WorkItemIdInteger0..1A reference to the Work Item that this work was generated from
GuidanceIdInteger0..*A list of guidance objects to be used for the work
NoteIdsInteger0..*Reference to a Note object

: This should go under LoggedData, so WorkRecord can also work for Non-mechanical harvest and other things.