Managing multiple versions of forms in a single database

I have been experimenting with ODK Collect and Aggregate to enable
data collection on our team's android phones. We have standard forms
and checklists that are re-used for various projects over multiple
years. One shortcoming I see is that whenever a form is updated, all
of the data is submitted into a new database. So far the only solution
I can see would be to download the old database as CSV, and maintain a
merged version outside of Aggregate. Would appreciate any advise or
tips you can offer.

we are working on some versioning abilities in the forms, but i think
exporting is currently your best option.

ยทยทยท On Tue, Feb 1, 2011 at 12:57, jaden wrote: > I have been experimenting with ODK Collect and Aggregate to enable > data collection on our team's android phones. We have standard forms > and checklists that are re-used for various projects over multiple > years. One shortcoming I see is that whenever a form is updated, all > of the data is submitted into a new database. So far the only solution > I can see would be to download the old database as CSV, and maintain a > merged version outside of Aggregate. Would appreciate any advise or > tips you can offer.