Really enjoying the new Aggregate (1.0 beta 3) and Collect (1.1.7 rc1)
modules - great work! Am trying to get a better feel for everything
the system can do and have the following questions that I can't find
the answers to at the minute:
Is it possible to delete submissions from within Aggregate? I know
you can purge published data, but what if you aren't publishing the
data and want to delete a incorrect submission?
Fusion table names default to 'data'. Changing the name seems to
break the link. Furthermore having multiple fusion tables each linked
to a form breaks all but the first publishing link. Presumably there
is a conflict due the other tables also being named 'data'? When
publishing to Google Spreadsheet one can define the tablename, but not
with Fusion. Is there a way of defining it in the form?
Am trying to find out if it is possible for each submission to have
stored as part of the data, the username of the person who submitted
the form?
Sorry just saw another thread that issue 1 is being worked on....
···
On Aug 12, 11:01 am, dj_bridges wrote:
> Hi there,
>
> Really enjoying the new Aggregate (1.0 beta 3) and Collect (1.1.7 rc1)
> modules - great work! Am trying to get a better feel for everything
> the system can do and have the following questions that I can't find
> the answers to at the minute:
>
> 1) Is it possible to delete submissions from within Aggregate? I know
> you can purge published data, but what if you aren't publishing the
> data and want to delete a incorrect submission?
>
> 2) Fusion table names default to 'data'. Changing the name seems to
> break the link. Furthermore having multiple fusion tables each linked
> to a form breaks all but the first publishing link. Presumably there
> is a conflict due the other tables also being named 'data'? When
> publishing to Google Spreadsheet one can define the tablename, but not
> with Fusion. Is there a way of defining it in the form?
>
> 3) Am trying to find out if it is possible for each submission to have
> stored as part of the data, the username of the person who submitted
> the form?
>
> Hope these are easy to answer!!!
Created an issue for #2 http://code.google.com/p/opendatakit/issues/detail?id=301 Not sure whether
the hard-coded naming is a limitation of the interface to Fusion Tables or
if it is a limitation in our code, or if Fusion Tables has better APIs now.
w.r.t. #3, the authenticated user that submits the form data is tracked in
the datastore as the _CREATOR_URI_USER, and if an update occurs, as the
_LAST_UPDATE_URI_USER. We just haven't exposed that as metadata in the user
interface. We're reworking the way submission records are displayed by
default, and we may allow these additional fields to be exposed once we get
something that shows your data without, by default, spewing 9 extra columns
of metadata that users ordinarily don't care to see.
Mitch
···
On Fri, Aug 12, 2011 at 2:04 AM, dj_bridges wrote:
Sorry just saw another thread that issue 1 is being worked on....
Really enjoying the new Aggregate (1.0 beta 3) and Collect (1.1.7 rc1)
modules - great work! Am trying to get a better feel for everything
the system can do and have the following questions that I can't find
the answers to at the minute:
Is it possible to delete submissions from within Aggregate? I know
you can purge published data, but what if you aren't publishing the
data and want to delete a incorrect submission?
Fusion table names default to 'data'. Changing the name seems to
break the link. Furthermore having multiple fusion tables each linked
to a form breaks all but the first publishing link. Presumably there
is a conflict due the other tables also being named 'data'? When
publishing to Google Spreadsheet one can define the tablename, but not
with Fusion. Is there a way of defining it in the form?
Am trying to find out if it is possible for each submission to have
stored as part of the data, the username of the person who submitted
the form?
Fusion table names default to 'data'. Changing the name seems to
break the link. Furthermore having multiple fusion tables each linked
to a form breaks all but the first publishing link. Presumably there
is a conflict due the other tables also being named 'data'? When
publishing to Google Spreadsheet one can define the tablename, but not
with Fusion. Is there a way of defining it in the form?
The column names and repeat table names in fusion tables names are
based on your xform instance names. Whatever the xml tag name in your
xform definition is what Aggregate uses to create the names. We will
look into the issue of not allowing tables with the same name soon.
Something might have changed in FusionTable api, in the past the
tables are just referred to by tableids generated by FusionTables and
you could have many tables of the same name. However, we have
experienced many changes in FusionTables that require changes in
Aggregate code, so if something change in FusionTables we will fix it
to match.
Waylon
···
On Fri, Aug 12, 2011 at 8:51 AM, Mitch Sundt wrote:
> Created an issue for #2
> http://code.google.com/p/opendatakit/issues/detail?id=301 Not sure whether
> the hard-coded naming is a limitation of the interface to Fusion Tables or
> if it is a limitation in our code, or if Fusion Tables has better APIs now.
>
> w.r.t. #3, the authenticated user that submits the form data is tracked in
> the datastore as the _CREATOR_URI_USER, and if an update occurs, as the
> _LAST_UPDATE_URI_USER. We just haven't exposed that as metadata in the user
> interface. We're reworking the way submission records are displayed by
> default, and we may allow these additional fields to be exposed once we get
> something that shows your data without, by default, spewing 9 extra columns
> of metadata that users ordinarily don't care to see.
>
> Mitch
>
> On Fri, Aug 12, 2011 at 2:04 AM, dj_bridges wrote:
>>
>> Sorry just saw another thread that issue 1 is being worked on....
>>
>> On Aug 12, 11:01 am, dj_bridges wrote:
>> > Hi there,
>> >
>> > Really enjoying the new Aggregate (1.0 beta 3) and Collect (1.1.7 rc1)
>> > modules - great work! Am trying to get a better feel for everything
>> > the system can do and have the following questions that I can't find
>> > the answers to at the minute:
>> >
>> > 1) Is it possible to delete submissions from within Aggregate? I know
>> > you can purge published data, but what if you aren't publishing the
>> > data and want to delete a incorrect submission?
>> >
>> > 2) Fusion table names default to 'data'. Changing the name seems to
>> > break the link. Furthermore having multiple fusion tables each linked
>> > to a form breaks all but the first publishing link. Presumably there
>> > is a conflict due the other tables also being named 'data'? When
>> > publishing to Google Spreadsheet one can define the tablename, but not
>> > with Fusion. Is there a way of defining it in the form?
>> >
>> > 3) Am trying to find out if it is possible for each submission to have
>> > stored as part of the data, the username of the person who submitted
>> > the form?
>> >
>> > Hope these are easy to answer!!!
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>
>
>
> --
> Mitch Sundt
> Software Engineer
> http://www.OpenDataKit.org
> University of Washington
> mitchellsundt@gmail.com
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>