InfoVeg

And that the fields in the database match each other correctly with Z_FieldDEsc

fixing the various cases in stem data also needs to take this into account. Also, make sure the unknownSp field is taken into account.

detecting and combining duplicates works, as does moving it over to the unfolded (treeDataBig/Sml).

Need to add this into the interface somehow, if we decide to regularly support this. Radio options between: all stems planted, all stems natural, and some stems planted (then selected which ones in the data lines).

This functionality may be better hidden from normal users and only messed with by dba.

also need to autopopulate isPlanted to T for individual stems.

Not needed anytime soon, if at all.

Sometimes users have planted stems that need to be switched to natural. Would be nice to have a button that did that, though probably the stem would stay in the planted form, which might be confusing. How to show the button is also unclear. Perhaps at the bottom of the form. "Change this stem to/from natural" If it was already natural, and the button was pressed, the stem would go back to planted. Some invisible (blank) text would be needed to flag the natural ones fairly clearly, always on.

(In reply to comment #8)

Sometimes users have planted stems that need to be switched to natural. Would
be nice to have a button that did that, though probably the stem would stay in
the planted form, which might be confusing. How to show the button is also
unclear. Perhaps at the bottom of the form. "Change this stem to/from natural"
If it was already natural, and the button was pressed, the stem would go back
to planted. Some invisible (blank) text would be needed to flag the natural
ones fairly clearly, always on.

This exact process has been done, version: (v224_p0585_mid3)

And these stems marked planted are excluded from future printing and sampling, as well as excluded from statistics that are spit out of the entry tool.

Original Bugzilla ID was 2787