On 6 Nov 2007, at 15:13, Luke Melia wrote: > > On Nov 6, 2007, at 9:31 AM, Nicholas Van Weerdenburg wrote: > >> Are import and versioning dependent or just lumped together under C >> since both need to be done. > > My thoughts are that we need to think about versioning if we offer an > import option, because otherwise we have a big problem the first time > we want to introduce a feature that needs a schema change.
>> I'd vote for B). Export and Import are often migration processes, so >> there is great value in having either. I'd vote for B too. I did start thinking about Importing, but the more I thought about it, the more complex it got (as do many things!). It's not hard to import a CSV file, YAML file or db dump, but as Luke points out, what happens if the schema has changed in between export and import. More importantly, how do we assign users to the imported records (what are the implications for security?), and how do we deal with possible conflicts or duplicate data? None of these are insurmountable, but they're not something that can be implemented quickly. At least having an export option allows people to a) try Tracks and get their data out easily if it doesn't work out for them, or b) use the data from tracks for reporting or archival purposes. cheers, bsag -- but she's a girl - the weblog of a female geek http://www.rousette.org.uk [EMAIL PROTECTED] _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
