do we have to install aggregate server for every new project/application we create?
I don't understand the context.
···
-------------- ODK Aggregate does not implement per-form access management. So if you want different people to only have access to certain forms or data from certain forms, then yes, you MAY need to have different servers, one for each.BUT, for the most part, if you have this need, it is better to think of ODK
Aggregate as a central collection point, accessible by one or two people.
Then, to use publishers or ODK Briefcase to distribute the data to
different groups by managing access to the resulting artifacts. I.e.,
manage access to the Google Spreadsheet or Fusion Table you publish data
to. Or after generating a CSV file from ODK Briefcase, place it on a
network file share and manage access via the access controls of that file
share.
The downside is that all the forms for all the projects would be visible
and downloadable to the device from this one common server even though a
data collector might use only one of the forms for their project. This may
be another justification for maintaining separate servers, but that would
also mean maintaining different sets of Android devices since ODK Collect
can only talk to one server.
And you can also specify the submitted-to server in your form definition.
That can enable the forms to be downloaded from server A, but, when
submitted, they would be sent to server B. This, however, necessitates the
use of the same username and password on both systems.
For ODK 2.0, an 'application' or 'project' is a collection of forms and web
pages that provide functionality for a complex set of workflows. Each ODK
Aggregate manages only a single such collection. And, in this case, you
MUST use a different ODK Aggregate for each.
On Fri, Nov 20, 2015 at 9:23 AM, ssonamtshering@gmail.com wrote:
do we have to install aggregate server for every new project/application
we create?--
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
And, for ODK 2.0, each Android device can interact and support multiple
'applications' or 'projects' co-existing on the same device without
interacting or corrupting each other.
···
On Fri, Nov 20, 2015 at 9:43 AM, Mitch Sundt wrote:I don't understand the context.
ODK Aggregate does not implement per-form access management. So if you
want different people to only have access to certain forms or data from
certain forms, then yes, you MAY need to have different servers, one for
each.BUT, for the most part, if you have this need, it is better to think of
ODK Aggregate as a central collection point, accessible by one or two
people.Then, to use publishers or ODK Briefcase to distribute the data to
different groups by managing access to the resulting artifacts. I.e.,
manage access to the Google Spreadsheet or Fusion Table you publish data
to. Or after generating a CSV file from ODK Briefcase, place it on a
network file share and manage access via the access controls of that file
share.
The downside is that all the forms for all the projects would be visible
and downloadable to the device from this one common server even though a
data collector might use only one of the forms for their project. This may
be another justification for maintaining separate servers, but that would
also mean maintaining different sets of Android devices since ODK Collect
can only talk to one server.
And you can also specify the submitted-to server in your form definition.
That can enable the forms to be downloaded from server A, but, when
submitted, they would be sent to server B. This, however, necessitates the
use of the same username and password on both systems.
For ODK 2.0, an 'application' or 'project' is a collection of forms and
web pages that provide functionality for a complex set of workflows. Each
ODK Aggregate manages only a single such collection. And, in this case, you
MUST use a different ODK Aggregate for each.On Fri, Nov 20, 2015 at 9:23 AM, ssonamtshering@gmail.com wrote:
do we have to install aggregate server for every new project/application
we create?--
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
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com