Action performed by:

I was wondering, is it possible for Aggregate to acknowledge which account has done this particular entry? We have accounts to allow access, does the system have the feature to detect the user for accountability?

Thank you!

Every data row has audit logging of

created-by user,
created-at-datetime,
last-update-by user,
last-update-date.

These are not exposed or exported, but are present for DBAs should they
need to reconstruct databases from logs and/or backups.

··· On Wed, Jul 1, 2015 at 5:12 PM, wrote:

I was wondering, is it possible for Aggregate to acknowledge which account
has done this particular entry? We have accounts to allow access, does the
system have the feature to detect the user for accountability?

Thank you!

--

Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en


You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

Every data row has audit logging of

created-by user,
created-at-datetime,
last-update-by user,
last-update-date.

These are not exposed or exported, but are present for DBAs should they need to reconstruct databases from logs and/or backups.

I was wondering, is it possible for Aggregate to acknowledge which account has done this particular entry? We have accounts to allow access, does the system have the feature to detect the user for accountability?

Thank you!

--

--

Post: opend...@googlegroups.com

Unsubscribe: opendatakit...@googlegroups.com

Options: http://groups.google.com/group/opendatakit?hl=en


You received this message because you are subscribed to the Google Groups "ODK Community" group.

To unsubscribe from this group and stop receiving emails from it, send an email to opendatakit...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Mitch Sundt
Software Engineer
University of Washington
mitche...@gmail.com

thank you for the reply! So is there any way to make it appear? I'm still new to this. I use the google app engine for the server.

··· On Thursday, 2 July 2015 08:48:25 UTC+8, Mitch Sundt wrote: > On Wed, Jul 1, 2015 at 5:12 PM, wrote:

If you want to record the username or e-mail of the user that collected the
data, you can add a pre-loaded property field into your form with that
information
https://opendatakit.org/help/form-design/examples/#Property_values This
would then appear as a field within your collected data. And you must
configure this information on ODK Collect's General Settings page. Note
that most devices do not allow retrieval of the phone number.

The Site Admin / Permissions page is used to manage user access rights
(e.g., Data Collector - the ability to submit filled-in forms). Form
Manager and Site Admin users implicitly have the Data Collector privilege.

You must revoke the Data Collector and Form Manager rights from 'anonymous'
in order for devices/users to be challenged for their username and
password. (be sure to Save Changes). If you don't, form submissions will be
recorded as coming from 'anonymous'.

We don't expose the audit fields because they are most useful for recovery
operations when you are a DBA managing a Tomcat install with MySQL or
PostgreSQL. They are present on AppEngine, but not exposed. Note that if
you were to pull data down with ODK Briefcase, then delete the form on the
server, then push the data up to the server, the username and created-at
timestamps would all change -- these are not treated as 'permanent data of
record' -- which is why we don't expose them.

··· On Wed, Jul 1, 2015 at 5:58 PM, wrote:

On Thursday, 2 July 2015 08:48:25 UTC+8, Mitch Sundt wrote:

Every data row has audit logging of

created-by user,
created-at-datetime,
last-update-by user,
last-update-date.

These are not exposed or exported, but are present for DBAs should they
need to reconstruct databases from logs and/or backups.

On Wed, Jul 1, 2015 at 5:12 PM, yogi...@gmail.com wrote:
I was wondering, is it possible for Aggregate to acknowledge which
account has done this particular entry? We have accounts to allow access,
does the system have the feature to detect the user for accountability?

Thank you!

--

--

Post: opend...@googlegroups.com

Unsubscribe: opendatakit...@googlegroups.com

Options: http://groups.google.com/group/opendatakit?hl=en


You received this message because you are subscribed to the Google
Groups "ODK Community" group.

To unsubscribe from this group and stop receiving emails from it, send
an email to opendatakit...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Mitch Sundt
Software Engineer
University of Washington
mitche...@gmail.com

thank you for the reply! So is there any way to make it appear? I'm still
new to this. I use the google app engine for the server.

--

Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en


You received this message because you are subscribed to the Google Groups
"ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com