Closed GoogleCodeExporter closed 9 years ago
I support this proposal.
I'm involved in a project which will involve a number of volunteers capturing
data and it will be imporant during quality control of the data to identify
whether some people ar consistently making certain types of error.
Kirby
Original comment by kirby.ja...@gmail.com
on 21 Feb 2011 at 2:02
much of this will be covered in the openrosa metadata schema.
https://bitbucket.org/javarosa/javarosa/wiki/OpenRosaMetaDataSchema
Original comment by yanokwa
on 28 Feb 2011 at 3:07
adding Collect label. Not sure if there is a preload function to write for
Collect to accomplish populating data for OpenRosa's metadata fields?
Original comment by mitchellsundt@gmail.com
on 1 Jul 2011 at 8:28
There is a "deviceid" property (and any capitalizations work) defined that will
return:
(1) the IMEI if available, or
(2) the WiFi MAC address if available, or
(3) the Android ID
<bind id="hidden1" nodeset="/imci/Meta/DeviceID" type="xsd:string"
jr:preload="property" jr:preloadParams="DeviceID" />
Original comment by mitchellsundt@gmail.com
on 28 Jun 2012 at 11:21
To better conform with OpenRosa, I've added:
jr:deviceID -- prefixes imei:, android_id: or mac:
jr:subscriberID -- prefixes imsi:
jr:simserial -- prefixes simserial:
jr:phonenumber -- prefixes tel: (note, if you don't have a sim card, this may
still have a value).
jr:username -- prefixes username: to the username as configured in ODK Collect
settings
jr:email -- prefixes mailto: to the Google Account (email) as configured in ODK
Collect settings
Original comment by mitchellsundt@gmail.com
on 30 Jun 2012 at 1:42
Update: I've changed jr: to uri: to be more generic. "uri:" means it will
prefix the parameter value with the uri of that value, per above.
Creating separate documentation issue to track documentation.
Original comment by mitchellsundt@gmail.com
on 12 Jul 2012 at 6:57
Original issue reported on code.google.com by
l...@applab.org
on 21 Jan 2011 at 10:08