Since we're completing a survey with a sample size close to 3000, I thought
I'd share something that Aggregate needs or should accommodate: Choosing
file names for csv exports AND the ability to DELETE csv files when they
are not needed!!!
Here's why! I have the Research Analyst in another city while I'm out in
the field and I DON'T want him to use the wrong csv export that I create
--- but they're ALWAYS given the same name. Also, if I have duplicate
submissions, then I clean the data from the web interface and then generate
a NEW csv. But no one would know which is the cleaned csv version -- very
confusing in a shared environment where many users have user id/passwords
to SEE the data. 
In addition, if I create filters for a subset of the data, the exports for
these ARE the same names too.
Ditto for deletions! It would be nice to be able to DELETE OLD csv files
since they're taking up server space AND confusing users.
Is this feature possible in future releases??
~DataMax
Max,
Feel free to file an issue on the website and it will be prioritized
based on lots of factors. There are many UI improvements that are on
the list but we are a small team trying to do a lot.
Additionally, the ODK project accepts code patches so if you want to
tackle that would be great.
Cheers,
Waylon
···
On Wed, Jun 13, 2012 at 9:34 PM, DataMax wrote:
> Since we're completing a survey with a sample size close to 3000, I thought
> I'd share something that Aggregate needs or should accommodate: Choosing
> file names for csv exports AND the ability to DELETE csv files when they are
> not needed!!!
>
> Here's why! I have the Research Analyst in another city while I'm out in the
> field and I DON'T want him to use the wrong csv export that I create --- but
> they're ALWAYS given the same name. Also, if I have duplicate submissions,
> then I clean the data from the web interface and then generate a NEW csv.
> But no one would know which is the cleaned csv version -- very confusing in
> a shared environment where many users have user id/passwords to SEE the
> data. :-)
> In addition, if I create filters for a subset of the data, the exports for
> these ARE the same names too.
> Ditto for deletions! It would be nice to be able to DELETE OLD csv files
> since they're taking up server space AND confusing users.
>
> Is this feature possible in future releases?? :-)
>
> ~DataMax
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
Ok Waylon, will do once I'm finished with this project.
Thanks.
···
On Thursday, June 14, 2012 8:13:16 AM UTC+3, waylon wrote:
>
> Max,
>
> Feel free to file an issue on the website and it will be prioritized
> based on lots of factors. There are many UI improvements that are on
> the list but we are a small team trying to do a lot.
>
> Additionally, the ODK project accepts code patches so if you want to
> tackle that would be great.
>
> Cheers,
> Waylon
>
> On Wed, Jun 13, 2012 at 9:34 PM, DataMax <max.......@gmail.com> wrote:
> > Since we're completing a survey with a sample size close to 3000, I
> thought
> > I'd share something that Aggregate needs or should accommodate: Choosing
> > file names for csv exports AND the ability to DELETE csv files when they
> are
> > not needed!!!
> >
> > Here's why! I have the Research Analyst in another city while I'm out in
> the
> > field and I DON'T want him to use the wrong csv export that I create ---
> but
> > they're ALWAYS given the same name. Also, if I have duplicate
> submissions,
> > then I clean the data from the web interface and then generate a NEW
> csv.
> > But no one would know which is the cleaned csv version -- very confusing
> in
> > a shared environment where many users have user id/passwords to SEE the
> > data. :-)
> > In addition, if I create filters for a subset of the data, the exports
> for
> > these ARE the same names too.
> > Ditto for deletions! It would be nice to be able to DELETE OLD csv files
> > since they're taking up server space AND confusing users.
> >
> > Is this feature possible in future releases?? :-)
> >
> > ~DataMax
> >
> > --
> > Post: opendatakit@googlegroups.com
> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> > Options: http://groups.google.com/group/opendatakit?hl=en
>