Hi,
when trying access the aggregate instance on app engine I get the following
errors, either invalid token (when trying to export forms to aggregate from
ODK build) or an invalid url when the app tries to redirect.
I was using the aggregate 1.0.9 because when using the latest version I
could not log into the aggregate using my google account details
I'd appreciate any help, best regards
Note that if your appspot instance is https://opendatakit.appspot.com, in
the Build dialog, you would enter just "opendatakit" in the field -- it
will prepend the https:// and the ".appspot.com" portion of the URL.
Also, you must sign up and log into Build before you can Publish a form to
aggregate, otherwise, you will get an
{"error":"unauthenticated"}
page (Build needs to know your e-mail address in order to publish to
Aggregate, and it does this through your sign-in to Build).
You should confirm that the e-mail you specified in Build is appropriate
for your appspot instance. You can do this by clicking on the username in
the upper right corner of build. If you need to change that e-mail, you
can, but you will also need to re-enter your password, as clicking "Update"
apparently changes the password whether or not you enter your old
password. And the e-mail address change does not show immediately. You
have to log out, then log back into Build before the change to the e-mail
is applied. This is most likely the cause of your woes.
I've tried this with ODK Aggregate 1.2, and it works fine for me, so this
does not appear to be a problem with Build or Google AppEngine.
Mitch
Hi,
when trying access the aggregate instance on app engine I get the
following errors, either invalid token (when trying to export forms to
aggregate from ODK build) or an invalid url when the app tries to redirect.I was using the aggregate 1.0.9 because when using the latest version I
could not log into the aggregate using my google account detailsI'd appreciate any help, best regards
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
And w.r.t. your attempt to use ODK Aggregate 1.2, when you specify your
e-mail address during the installer, you need to specify it exactly as
reported by Gmail. This generally means all-lowercase letters. To see the
capitalization that Gmail uses, click on your name in the upper right
corner of Gmail. Use the e-mail address reported under your name in the
pop-up as the Superuser e-mail address during the install.
Mitch
Note that if your appspot instance is https://opendatakit.appspot.com, in
the Build dialog, you would enter just "opendatakit" in the field -- it
will prepend the https:// and the ".appspot.com" portion of the URL.Also, you must sign up and log into Build before you can Publish a form to
aggregate, otherwise, you will get an{"error":"unauthenticated"}
page (Build needs to know your e-mail address in order to publish to
Aggregate, and it does this through your sign-in to Build).You should confirm that the e-mail you specified in Build is appropriate
for your appspot instance. You can do this by clicking on the username in
the upper right corner of build. If you need to change that e-mail, you
can, but you will also need to re-enter your password, as clicking "Update"
apparently changes the password whether or not you enter your old
password. And the e-mail address change does not show immediately. You
have to log out, then log back into Build before the change to the e-mail
is applied. This is most likely the cause of your woes.I've tried this with ODK Aggregate 1.2, and it works fine for me, so this
does not appear to be a problem with Build or Google AppEngine.Mitch
On Wed, Aug 8, 2012 at 8:33 AM, scrirmmager prbrundell@gmail.com wrote:
Hi,
when trying access the aggregate instance on app engine I get the
following errors, either invalid token (when trying to export forms to
aggregate from ODK build) or an invalid url when the app tries to redirect.I was using the aggregate 1.0.9 because when using the latest version I
could not log into the aggregate using my google account detailsI'd appreciate any help, best regards
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
Thanks for your quick reply. I can now access the aggregate on google apps
(the email was indeed not identical in terms of uppercase/lowercase)
. However, when I access the aggregate site admin tab user options are
greyed out, I have no data collector for myself and cannot change anything.
I am unable to access the aggregate from my phone and was suspecting it was
to do with permissions. Although forms appear uploaded to the aggregate,
they are not visible when logged in.
apologies for all the questions...many thanks
Yes, on the Site Admin/Permissions tab, it will initially show just your
gmail account, and all the settings for that are greyed out. This is
because this is the SuperUser for the system, and has widespread
permissions which cannot be reduced. It does, however, lack Data Collector
permissions.
Data Collector permissions cannot be granted to Gmail accounts (hence why
it is not granted to your SuperUser account).
You must add a user (an ODK Aggregate user), grant that user Data Collector
permissions, and assign it a password. To do so:
(1) Enter a username in the text area in the "Add Users" section, below the
permissions table,
(2) click "Add". The user will now appear in the permissions table above,
and, if the username does not look like an e-mail address, it will
automatically have the "ODK" account type.
(3) Ensure that this user has the "ODK" account type,
(4) check the "Data Collector" permission for that username, and
(5) click "Save Changes".
(6) Then click "Change Password" and set the password for this user
account.
You can then open ODK Collect, click on the menu button, choose Change
Settings, and enter this username and password into ODK Collect. You should
then be able to access the server.
Mitch
Thanks for your quick reply. I can now access the aggregate on google apps
(the email was indeed not identical in terms of uppercase/lowercase)
. However, when I access the aggregate site admin tab user options are
greyed out, I have no data collector for myself and cannot change anything.
I am unable to access the aggregate from my phone and was suspecting it was
to do with permissions. Although forms appear uploaded to the aggregate,
they are not visible when logged in.apologies for all the questions...many thanks
On Wednesday, 8 August 2012 18:09:20 UTC+1, Mitch wrote:
And w.r.t. your attempt to use ODK Aggregate 1.2, when you specify your
e-mail address during the installer, you need to specify it exactly as
reported by Gmail. This generally means all-lowercase letters. To see the
capitalization that Gmail uses, click on your name in the upper right
corner of Gmail. Use the e-mail address reported under your name in the
pop-up as the Superuser e-mail address during the install.Mitch
On Wed, Aug 8, 2012 at 10:06 AM, Mitch S mitche...@gmail.com wrote:
Note that if your appspot instance is https://opendatakit.appspot.**comhttps://opendatakit.appspot.com,
in the Build dialog, you would enter just "opendatakit" in the field -- it
will prepend the https:// and the ".appspot.com" portion of the URL.Also, you must sign up and log into Build before you can Publish a form
to aggregate, otherwise, you will get an{"error":"unauthenticated"}
page (Build needs to know your e-mail address in order to publish to
Aggregate, and it does this through your sign-in to Build).You should confirm that the e-mail you specified in Build is appropriate
for your appspot instance. You can do this by clicking on the username in
the upper right corner of build. If you need to change that e-mail, you
can, but you will also need to re-enter your password, as clicking "Update"
apparently changes the password whether or not you enter your old
password. And the e-mail address change does not show immediately. You
have to log out, then log back into Build before the change to the e-mail
is applied. This is most likely the cause of your woes.I've tried this with ODK Aggregate 1.2, and it works fine for me, so
this does not appear to be a problem with Build or Google AppEngine.Mitch
On Wed, Aug 8, 2012 at 8:33 AM, scrirmmager prbru...@gmail.com wrote:
Hi,
when trying access the aggregate instance on app engine I get the
following errors, either invalid token (when trying to export forms to
aggregate from ODK build) or an invalid url when the app tries to redirect.I was using the aggregate 1.0.9 because when using the latest version I
could not log into the aggregate using my google account detailsI'd appreciate any help, best regards
--
Mitch Sundt
Software Engineer
University of Washington
mitche...@gmail.com--
Mitch Sundt
Software Engineer
University of Washington
mitche...@gmail.com
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com
It is likely that your form definition has omissions or is partially
defined in some way, causing errors when it is uploaded to ODK Aggregate.
Download your form XML from Build to your desktop.
Download the ODK Validate tool from here:
http://code.google.com/p/opendatakit/downloads/list
Double-click the ODK Validate tool to launch it, choose the form XML, and
resolve any errors the tool reports.
Until ODK Aggregate has the form definition, you will be unable to send any
of those completed forms up to aggregate -- because it simply won't know
what to do with them. So you will get 404 errors (form definition not
found). That is expected.
Note that different users have different permissions on ODK Aggregate. Your
SuperUser can upload form definitions, delete them, view completed forms,
etc. If you created an ODK Aggregate user with just Data Collector
permissions, it will only be able to submit completed forms, not upload
form definitions. Because of the way the ODK Aggregate user is recognized
by the server and browser, if you need to log in under a different username
or under a gmail account, you must close all your browser tabs and windows
after you "log off" from and ODK user within ODK Aggregate, in order for
the logging out to actually take place. This can be confusing. The Google
acconts give you a more natural, more expected, web experience.
Mitch
I realise now i cannot set myself as a collector.oops. I have set up a new
user and can log in, but on the phone app obviously google account is set,
so even if I change the username and password to the new one set in the
aggregate, is that not a problem?I am unable to upload any forms to the aggregate, either completed from
the phone (not found 404 error) or from the build export. It allows the
upload but when I go to the aggregate there is nothing there. trying to
load a local xml form doesnt work either (I get an app engine app error)I can connect to the aggregate now from the phone to view a form list, but
obviously there are no forms. however the connection must be working.I really want to get this working, but should it be this much work?!
best regards
On Friday, August 10, 2012 2:53:49 PM UTC+1, scrirmmager wrote:
Thanks for your quick reply. I can now access the aggregate on google
apps (the email was indeed not identical in terms of uppercase/lowercase)
. However, when I access the aggregate site admin tab user options are
greyed out, I have no data collector for myself and cannot change anything.
I am unable to access the aggregate from my phone and was suspecting it was
to do with permissions. Although forms appear uploaded to the aggregate,
they are not visible when logged in.apologies for all the questions...many thanks
On Wednesday, 8 August 2012 18:09:20 UTC+1, Mitch wrote:And w.r.t. your
attempt to use ODK Aggregate 1.2, when you specify your e-mail address
during the installer, you need to specify it exactly as reported by Gmail.
This generally means all-lowercase letters. To see the capitalization that
Gmail uses, click on your name in the upper right corner of Gmail. Use the
e-mail address reported under your name in the pop-up as the Superuser
e-mail address during the install.Mitch
On Wed, Aug 8, 2012 at 10:06 AM, Mitch S mitche...@gmail.com wrote:
Note that if your appspot instance is https://opendatakit.appspot.com,
in the Build dialog, you would enter just "opendatakit" in the field -- it
will prepend the https:// and the ".appspot.com" portion of the URL.Also, you must sign up and log into Build before you can Publish a form
to aggregate, otherwise, you will get an {"error":"unauthenticated"}page
(Build needs to know your e-mail address in order to publish to Aggregate,
and it does this through your sign-in to Build).You should confirm that the e-mail you specified in Build is appropriate
for your appspot instance. You can do this by clicking on the username in
the upper right corner of build. If you need to change that e-mail, you
can, but you will also need to re-enter your password, as clicking "Update"
apparently changes the password whether or not you enter your old
password. And the e-mail address change does not show immediately. You
have to log out, then log back into Build before the change to the e-mail
is applied. This is most likely the cause of your woes.I've tried this with ODK Aggregate 1.2, and it works fine for me, so
this does not appear to be a problem with Build or Google AppEngine.Mitch
On Wed, Aug 8, 2012 at 8:33 AM, scrirmmager prbru...@gmail.com wrote:
Hi,
when trying access the aggregate instance on app engine I get the
following errors, either invalid token (when trying to export forms to
aggregate from ODK build) or an invalid url when the app tries to redirect.I was using the aggregate 1.0.9 because when using the latest version I
could not log into the aggregate using my google account detailsI'd appreciate any help, best regards
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com