Project

General

Profile

Bug #3789

create "export to VegBank" function

Added by Michael Lee over 11 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
ViewerDB
Target version:
Start date:
01/29/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
3789

Description

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.


Related issues

Blocked by InfoVeg - Bug #3800: 1/28/2009 CONTAINER bugNew01/29/2009

History

#1 Updated by Michael Lee over 10 years ago

The Viewer can now do this!

User defined fields are not exported at this time, and I'd suggest we skip that except for vitally important fields. I highly doubt that user-defined fields will be used very much in VegBank.

#2 Updated by Redmine Admin over 7 years ago

Original Bugzilla ID was 3789

Also available in: Atom PDF