improving support for Transportation (process)

[elf-pavlik]

based on http://valdev.webfactional.com/accounting/process/957/

Transportation could use pickup and dropoff events which use locations. This way stocks of matching type would get filtered by the location, also possible new stocks created during the dropoff would have their location pre-populated.

Pickup events might have only location data but not the 'from' stock, especially if we pick up from inventory managed by another peer who doesn't maintain or expose information about their stocks.

[bhaugen]

Pickup events might have only location data but not the 'from' stock, especially if we pick up from inventory managed by another peer who doesn't maintain or expose information about their stocks.

Depends on whether the pickup event decrements the from-resource, or if another event logged by the from-agent does that (like staging some resources for pickup).

[bhaugen]

But, really nice valdev example!

[bhaugen]

See also http://www.itu.dk/people/hessellund/work/Hessellund05a.pdf , which proposes an REA transportation model.

[elf-pavlik]

Pickup events might have only location data but not the 'from' stock, especially if we pick up from inventory managed by another peer who doesn't maintain or expose information about their stocks.

Depends on whether the pickup event decrements the from-resource, or if another event logged by the from-agent does that (like staging some resources for pickup).

Let's say 'from-agent' split lot controlled resource and this ways stages it for pick-up. The 'transport-providing-agent' and 'to-agent' don't need to know anything else than the data about resource already staged from them. I think this fits 'hard allocation' discussed in https://github.com/valueflows/resource/issues/22