We use ODK Aggregate with ODK Collect and Enketo to collect data. Below I'm
describing a recurrent obstacle we encounter quite often, and perhaps we
might not be alone in this regard.
Whenever we have two (or more) forms that *need different authentication
settings from each other (one private, the other public), *it's impossible
to have them run simultaneously within a single ODK instance since there is
only *one universal setting regarding public/private forms ( *the anonymousUser
privileges at Site Access Configuration page).
Because of the usage fee model for Google AppEngine, we recommend users
move the data off of ODK Aggregate to a secondary system for data analysis
and access (see https://opendatakit.org/use/aggregate/data-transfer/ ).
This generally limits the use of ODK Aggregate to accumulating data from
all data-collection devices into a central location.
In this usage model, groups generally have a very small number of user
accounts with access to the system. Those users are either:
data collectors, with no visibility into the collected data, or
form managers that supervise the individual data collection efforts,
maintain the publishers into external systems, or use ODK Briefcase to
generate CSV files and assemble those into reports for dissemination.
For this reason, we decided to omit per-form permissions from ODK Aggregate
and simplify the administration screens.
ยทยทยท
On Wed, Jan 13, 2016 at 3:04 AM, piqo wrote:
Hi ODK team,
We use ODK Aggregate with ODK Collect and Enketo to collect data. Below
I'm describing a recurrent obstacle we encounter quite often, and perhaps
we might not be alone in this regard.
Whenever we have two (or more) forms that *need different authentication
settings from each other (one private, the other public), *it's
impossible to have them run simultaneously within a single ODK instance
since there is only *one universal setting regarding public/private forms
( *the anonymousUser privileges at Site Access Configuration page).