valueflows docs
git clone
Log | Files | Refs | README

commit a451217bbb143d30e5099587cf9b2a80a31f9ee9
parent 5715db7c6955236ff7b54f802389279e5e790aef
Author: Lynn Foster <>
Date:   Tue, 22 Jan 2019 14:45:32 -0600

Improve tt (#408)

track using trackingIdentifer, per @bhaugen

Mdocs/appendix/ | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/appendix/ b/docs/appendix/ @@ -30,6 +30,6 @@ Here is the logic for tracking and tracing. * a Process or Transfer from which is is an output, or * if it is an input to a Process or Transfer, the EconomicResource which it affects. -When there is more than one economic resource going from input to output of a process without transformation of that resource (except for location), the tracking identifier is used. And example of this would be partial load shipments, where many separate shipments are included in the same shipment process. +When more than one resource of the same classification goes from input to output of the same process, use the tracking identifier if you need to track or trace the same resource. And example of this would be less-than-truckload shipments, where many separate resources with different destinations are included in the same shipment process. When the same economic resource is both input and output of a process, sometimes a series of processes, such as for repair or quality testing or a workflow where a resource is refined through stages like writing/editing/etc, the stage must be identified, based on the kind of process the resource was last output of.