you can't collect phone number programmatically. best you can do is
sim or subscriber serial.
···
On Fri, Nov 19, 2010 at 13:13, Andrew Marder wrote:
> From, looking at example surveys the four metadata fields I plan to
> collect are:
>
> deviceid (IMEI)
> phonenumber
> start timestamp
> end timestamp
>
> Are there any other fields you have found useful for surveys? (I plan
> to use the deviceid to identify the surveyor.)
>
> Andrew
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
···
On Fri, Nov 19, 2010 at 8:54 PM, Yaw Anokwa wrote:
> you can't collect phone number programmatically. best you can do is
> sim or subscriber serial.
>
> On Fri, Nov 19, 2010 at 13:13, Andrew Marder wrote:
>> From, looking at example surveys the four metadata fields I plan to
>> collect are:
>>
>> deviceid (IMEI)
>> phonenumber
>> start timestamp
>> end timestamp
>>
>> Are there any other fields you have found useful for surveys? (I plan
>> to use the deviceid to identify the surveyor.)
>>
>> Andrew
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
hmm. doesn't work on my phone (nexus one on tmobile), so it must be
network dependent...
···
On Sat, Nov 20, 2010 at 10:16, Andrew Marder wrote:
> Try out the attached form. It's collecting my phone number!
>
> On Fri, Nov 19, 2010 at 8:54 PM, Yaw Anokwa wrote:
>> you can't collect phone number programmatically. best you can do is
>> sim or subscriber serial.
>>
>> On Fri, Nov 19, 2010 at 13:13, Andrew Marder wrote:
>>> From, looking at example surveys the four metadata fields I plan to
>>> collect are:
>>>
>>> deviceid (IMEI)
>>> phonenumber
>>> start timestamp
>>> end timestamp
>>>
>>> Are there any other fields you have found useful for surveys? (I plan
>>> to use the deviceid to identify the surveyor.)
>>>
>>> Andrew
>>>
>>> --
>>> Post: opendatakit@googlegroups.com
>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>> Options: http://groups.google.com/group/opendatakit?hl=en
>>>
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
I wonder whether xForms allow you to specify 'dummy' entries.
Instead of the user answering a question an answer would be filled in
automatically.
This might be used to create 'columns' in the output csv file which
could be filled in during the analysis stage - or for sub version
numbers for the form etc.
···
On Sat, Apr 16, 2011 at 02:04, KirbyJames wrote:
> I wonder whether xForms allow you to specify 'dummy' entries.
> Instead of the user answering a question an answer would be filled in
> automatically.
>
> This might be used to create 'columns' in the output csv file which
> could be filled in during the analysis stage - or for sub version
> numbers for the form etc.
>
> Kirby
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
Can you explain further what you mean by "read-only" binds?
I'd like to attach additional metadata to forms. One way I was
thinking of doing that was to programatically set the answers to
questions that the user never sees.
I appreciate any ideas you may have.
Thanks!
···
On Apr 16, 2:32 pm, Yaw Anokwa wrote:
> you can specific default values in theform.
>
> in the widgetsform, we specify default values for a lot of the nodes.http://code.google.com/p/opendatakit/source/browse/Widgets.xml?repo=f...
>
> you can use this in combination with read-only binds.http://code.google.com/p/opendatakit/source/browse/Widgets.xml?repo=f...http://code.google.com/p/opendatakit/source/browse/Widgets.xml?repo=f...
>
>
>
>
>
>
>
> On Sat, Apr 16, 2011 at 02:04, KirbyJames wrote:
> > I wonder whether xForms allow you to specify 'dummy' entries.
> > Instead of the user answering a question an answer would be filled in
> > automatically.
>
> > This might be used to create 'columns' in the output csv file which
> > could be filled in during the analysis stage - or for sub version
> > numbers for theformetc.
>
> > Kirby
>
> > --
> > Post: opendatakit@googlegroups.com
> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> > Options:http://groups.google.com/group/opendatakit?hl=en
read only binds make the data immutable. so in the example below,
you'll get a prompt with question text "stuff question" and an answer
of "my stuff". you will not be able to change the "my stuff" value.
my stuff
stuff question
only prompts which are defined in the body are shown. you can store
whatever you want in the instance. can detail exactly what you had in
mind?
yaw
···
On Tue, Apr 26, 2011 at 12:07, GregM wrote:
> Hi,
>
> Can you explain further what you mean by "read-only" binds?
>
> I'd like to attach additional metadata to forms. One way I was
> thinking of doing that was to programatically set the answers to
> questions that the user never sees.
>
> I appreciate any ideas you may have.
>
> Thanks!
>
>
>
> On Apr 16, 2:32 pm, Yaw Anokwa wrote:
>> you can specific default values in theform.
>>
>> in the widgetsform, we specify default values for a lot of the nodes.http://code.google.com/p/opendatakit/source/browse/Widgets.xml?repo=f...
>>
>> you can use this in combination with read-only binds.http://code.google.com/p/opendatakit/source/browse/Widgets.xml?repo=f...http://code.google.com/p/opendatakit/source/browse/Widgets.xml?repo=f...
>>
>>
>>
>>
>>
>>
>>
>> On Sat, Apr 16, 2011 at 02:04, KirbyJames wrote:
>> > I wonder whether xForms allow you to specify 'dummy' entries.
>> > Instead of the user answering a question an answer would be filled in
>> > automatically.
>>
>> > This might be used to create 'columns' in the output csv file which
>> > could be filled in during the analysis stage - or for sub version
>> > numbers for theformetc.
>>
>> > Kirby
>>
>> > --
>> > Post: opendatakit@googlegroups.com
>> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> > Options:http://groups.google.com/group/opendatakit?hl=en
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>