See the ADAPT - LoggedData / OperationData / Section / Meter Discussion: each instance of a Load is valid inside the context of a single OperationData instance.
How does this work in the context of non-mechanical harvest? In the context of Summary? (Relegating non-mechanical load discussions for version 2).
Attribute | Type | Multiplicity | Description |
---|---|---|---|
Id | CompoundIdentifier | 1 | Unique identifier |
Description | String | 0..1 | |
TimeScopeIds | Integer | 0..1 | When was the load created? This is useful for summary-only situations. Note how it can also include a geographical location. |
LoadNumber | String | 0..1 | Think about use cases: cotton modules |
LoadType | LoadTypeEnum | 1 | Will ultimately become an EnumeratedRepresentationValue |
LoadQuantity | NumericRepresentationValue | 0..1 | |
DestinationIds | Integer | 0..* | Destination(s) to which the load is shipped. |
NEED TO ADD WHAT IS CONTAINED IN THE LOAD! |
Attribute | Type | Multiplicity | Description |
---|---|---|---|
Id | CompoundIdentifier | 1 | Unique identifier |
Name | String | 1 | Note text |
DestinationType | EnumeratedRepresentation | 1 | Unspecified, Bin, Elevator, Terminal, etc. |
GLN | Uri | 0..1 | Global Location Number |
ContactInfo | Integer | 0..1 | Address, phones, etc. Defined in ADAPT - Grower / Farm / Field / Cropzone / ContactInfo / Location / Facility / FacilityTypeEnum Discussion |
Use cases to use for testing our ideas:
Attrib / type | Concept | Load | ContainerUse | ProdAll | Comment |
---|---|---|---|---|---|
Load.Id: CompoundIdentifier ProductAllocation: CompoundIdentifier | Identify standalone instances | ContainerUse does NOT have a unique Id because it is owned by the corresponding LoggedData? Do Loads, ProductAllocations, etc. need to stand alone? | |||
ProductAllocation.OriginContainerId | Origin of the movement | This is implicit in ContainerUse, and explicit in ProductAllocation. Do not have clear semantics in ContainerUse of how to link a succession of container movements: we have to sort through them with timestamps, etc. Need to tighten the causality for the purposes of traceability. An interesting assumption in ProductAllocation is that products always flow among containers. So does ContainerUse, for that matter. | |||
ProductAllocation.DestinationContainerId | Destination of the movement | This is implicit in ContainerUse, and explicit in ProductAllocation. Do not have clear semantics in ContainerUse of how to link a succession of container movements: we have to sort through them with timestamps, etc. Need to tighten the causality for the purposes of traceability. An interesting assumption in ProductAllocation is that products always flow among containers. So does ContainerUse, for that matter. | |||
Load.DestinationIds[0..*]: Integer | List of destinations | A destination is a separate class, an ad-hoc mashup of Location and Facility, with a unique Id and a description. Note that as of ContainerUse does not resolve where things go / where they come from. | |||
Load.LoadNumber[0..1]: String | Human-readable identifier of the load. | As of ContainerUse needs a description or LoadNumber or similar. | |||
ProductAllocation.LoadId | Id of the Load that the ProductAllocation is in the context of. | Used in conjuction with Load, ProductAllocation identifies the product and the amount involved, and Load allows giving that particular instance of an amount of a product an identity. | |||
Load.Description[0..1]: String | As of ContainerUse needs a description or LoadNumber or similar. | ||||
Load.TimeScopes[0..*]:Integer ContainerUse.TimeScopeIds[0..*]:Integer ProductAllocation.TimeScopeIds[0..*]:Integer | Meaningful timestamps & locations for when the movement took place. | No need to use TimeScopes by reference. | |||
LoadType: Enumeration | Enumeration: Unknown, Tank, Field, Truck, Bale, Module | A little unclear | |||
Load.LoadQuantity[0..1]: NumericRepresentationValue ContainerUse.AmountUsed: NumericRepresentationValue ProductAllocation.ProductAmount: NumericRepresentation | Amount of product/commodity | Note that it was optional in Load, but required in ContainerUse. Unclear why it would be optional. | |||
ContainerUse.ContainerId | What container was the subject | ||||
ContainerUse.ProductId ProductAllocation.ProductId | Identifying what product is being handled | Based on latest work on the matter, harvestedCommodity is a specialization of Product, so this ProductId would allow us to identify both products going to the field and commodities coming back from the field. | |||
ContainerUse.ContainerAction: ContainerActionEnum | Tells us what is being done with the container | ||||
ContextItems[0..*] | Container has ContextItems that could be used to reflect things like:
| ||||
DocumentIDs[0..*]: Integer | Identify the document(s) this "load" is associated with. Such documents could include Work Records, Weight Certificates / Scale Tickets, etc. |