I have been using ODK Aggregate 1.2 and recently just successfully customised the source code to fit in with our development needs for a project in Pakistan using PostgreSQL and HTTPS. However, from the release notes for ODK Aggregate 1.3 I understand that Google is disabling its OAuth 1.0 system and moving to OAuth 2.0.
So I wondered - does this mean all applications running ODK Aggregate 1.2 over https will stop working or will they continue to work? Esp. since I'm not using Google App service for data storage.
Also should I expect periodic upgrades to ODK Aggregate that will be required for the software to work in the future or can I continue to modify the current version 1.2 until the end of the project in 5 year's time?
If you need to publish to Google Fusion Tables or Spreadsheets, then you
will need to incorporate the OAuth 2.0 changes. Otherwise, you can remain
with the 1.2 codebase. It is only needed for the publishers.
Since you are running on your own server, it is up to you whether you
incorporate the updates from the active development branch or not. Since
you control your own hardware and software, once it works adequately, you
can freeze development and use it as-is. As long as nothing forces you to
change that configuration, it should continue to work. That would mean
that you will not have all the bug fixes made to the development branch.
So there will be some limitations to what your server is able to do; you
might want to monitor and incorporate significant bug fixes into your code.
Over time, your version of the Javarosa library will become increasingly
out-of-date with respect to what XLSForm uses, and you may eventually need
to update that library in order to work with the features being added to
the javarosa libraries.
Mitch
···
On Tue, Aug 27, 2013 at 2:08 AM, wrote:
Hi there,
I have been using ODK Aggregate 1.2 and recently just successfully
customised the source code to fit in with our development needs for a
project in Pakistan using PostgreSQL and HTTPS. However, from the release
notes for ODK Aggregate 1.3 I understand that Google is disabling its OAuth
1.0 system and moving to OAuth 2.0.
So I wondered - does this mean all applications running ODK Aggregate 1.2
over https will stop working or will they continue to work? Esp. since I'm
not using Google App service for data storage.
Also should I expect periodic upgrades to ODK Aggregate that will be
required for the software to work in the future or can I continue to modify
the current version 1.2 until the end of the project in 5 year's time?
···
On Tuesday, August 27, 2013 9:14:40 PM UTC+5, Mitch Sundt wrote:
> If you need to publish to Google Fusion Tables or Spreadsheets, then you will need to incorporate the OAuth 2.0 changes. Otherwise, you can remain with the 1.2 codebase. It is only needed for the publishers.
>
>
> Since you are running on your own server, it is up to you whether you incorporate the updates from the active development branch or not. Since you control your own hardware and software, once it works adequately, you can freeze development and use it as-is. As long as nothing forces you to change that configuration, it should continue to work. That would mean that you will not have all the bug fixes made to the development branch. So there will be some limitations to what your server is able to do; you might want to monitor and incorporate significant bug fixes into your code.
>
>
>
> Over time, your version of the Javarosa library will become increasingly out-of-date with respect to what XLSForm uses, and you may eventually need to update that library in order to work with the features being added to the javarosa libraries.
>
>
> Mitch
>
>
>
>
>
>
>
>
>
>
>
> On Tue, Aug 27, 2013 at 2:08 AM, wrote:
>
> Hi there,
>
>
>
> I have been using ODK Aggregate 1.2 and recently just successfully customised the source code to fit in with our development needs for a project in Pakistan using PostgreSQL and HTTPS. However, from the release notes for ODK Aggregate 1.3 I understand that Google is disabling its OAuth 1.0 system and moving to OAuth 2.0.
>
>
>
>
> So I wondered - does this mean all applications running ODK Aggregate 1.2 over https will stop working or will they continue to work? Esp. since I'm not using Google App service for data storage.
>
>
>
> Also should I expect periodic upgrades to ODK Aggregate that will be required for the software to work in the future or can I continue to modify the current version 1.2 until the end of the project in 5 year's time?
>
>
>
>
> Best wishes,
>
>
>
> Lu
>
>
>
> --
>
> --
>
> 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/groups/opt_out.
>
>
>
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitche...@gmail.com
While am i getting this error message everytime i try to run ODK-Agregate
on my windows 7 computer "Error creating directory
C:/ProgramData/Microsoft/Windows/StartMenu/Programs/ODK Aggregate".
That is one of Windows' special directory locations -- you should not be
creating anything under there -- the operating system manages that location.
Try placing it under 'My Documents' (choose Downloads, then go up a level,
and you will find a 'My Documents' folder -- place it under that).
···
On Fri, Nov 15, 2013 at 5:43 AM, Chrispin Njuku wrote:
Hi Mitch.
While am i getting this error message everytime i try to run ODK-Agregate
on my windows 7 computer "Error creating directory
C:/ProgramData/Microsoft/Windows/StartMenu/Programs/ODK Aggregate".