create "export to VegBank" function
Since the data structure are very similar in VegBank and CVS, it should be fairly easy* to copy code from VegBranch to the Viewer so that someone could create XML to ship to VegBank for inclusion there.
The scope for this would be about a project in size, perhaps broken into pieces if one file would be too large for VegBank.
We will have to consider how much data to send about each plot. Some of the questions:
1) send plots with nested subplots for each module, or just "parent" plots
2) how many of the extra fields created for use in CVS should be added as user-defined data
3) very careful QA will be needed to make sure that embargoed/confidential/sensitive data are not transmitted about plots, e.g. all plot location information about some plots.