To see this working, head to your live site.

Feature Request: Origin Tracking

I'd like to request the addition of a field in the Stands table named "Origin" [NVARCHAR(50)] that allows the user to define the stand origin (planted, natural, unknown). This could potentially be constrained to match planting actions in the Rules section of Assisi (and updated when a rule is implemented during growth?).

Thoughts?

5 comments

Comments (5)

Rich Howard

Sep 19, 2022

I've added Origin and an AllowedOrigin table.

Origin can be set in the Stands table to reflect the regeneration source of trees at the time of a cruise. Assisi will update the SummaryByStand.Origin field when a cruise is compiled, or when a planting action occurs. In other words, look to the SummaryByStand table for a stand's "current inventory origin".

Elijah Allensworth

Sep 13, 2022

I would think keeping it constrained to an Allowed table is best; I'm always a fan of more controls. And yeah, connecting it to the History table would be cool; if a stand was regenerated with a planting action, Assisi could update the Origin field automatically?

Rich Howard

Sep 13, 2022

Replying to

Yes, but the planting would update fields in the SummaryByStand table, not the Stands table. This is because Stands is really just the state of the stand at "establishment of record" rather than the current state it is in. Establishment is when the stand first became a defined polygon. It could be before the first cruise. So the fields in Stand should be looked at as what the stand looked like at that date of establishment. As history is simulated during growth, those fields can change for example acres or "Origin". So... Assisi puts the "latest" stand field values in the SummaryByStand table. It's ads a layer of redirection which I don't like, but we can add fields to SummarybyStand to summarize the latest processed state of a stand.

Elijah Allensworth

Sep 13, 2022

Replying to

Fair enough. Origin is, at the least, I think, appropriate for the Stands table based on that definition.

Rich Howard

Sep 13, 2022

Do you think Origin should have an "Allowed" values table too so that spellings and cascade updates occur? Or just a free floating field?

Related to this is building out the History tables more. History is meant to hold all the history of a stand from establishment to disposal. Stands can be recompiled from original cruise and regrown to arbitrary dates carrying out whatever is in the History tables: harvest, thins, planting, fertilization etc. Adding summaries of history to stand grids and reports might be best so that other historical actions can be show as well.