search

akvo / akvo-product-design

Products Design Documents
GNU Affero General Public License v3.0
12 stars 9 forks source link

Geolocations for Project Updates #40

Closed adriancollier closed 9 years ago

adriancollier commented 10 years ago

Issue to start collecting and displaying the Gelocations for new project updates.

Started to cover some of the requirements here: https://github.com/akvo/akvo-rsr-up/issues/22 https://github.com/akvo/akvo-rsr/issues/646

Functional spec on its way.

adriancollier commented 10 years ago

@stellanl @zzgvh @KasperBrandt One question to be answered:

Number 3 here: https://github.com/akvo/akvo-product-design/blob/master/RSR/Features/40-Update-Locations/FunctionalDesign/40-Update-Locations.md#questions Should the options be on the app level or account level when adding updates?

I was wondering what your thoughts are?

If we add it at the account level then we could utilise this for the Web and Up forms. But I think this should be "settable" from either - so is it possible to have a user setting that can be modified either from http://rsr.akvo.org/myakvo/ or from the RSR Up settings and have them synchronised?

Ideas on the simple solution welcome!

stellanl commented 10 years ago

On 2014-07-02 10:14, Adrian Collier wrote:

@stellanl https://github.com/stellanl @zzgvh https://github.com/zzgvh @KasperBrandt https://github.com/KasperBrandt One question to be answered:

Number 3 here: https://github.com/akvo/akvo-product-design/blob/master/RSR/Features/40-Update-Locations/FunctionalDesign/40-Update-Locations.md#questions Should the options be on the app level or account level when adding updates?

I was wondering what your thoughts are?

If we add it at the account level then we could utilise this for the Web and Up forms. But I think this should be "settable" from either - so is it possible to have a user setting that can be modified either from http://rsr.akvo.org/myakvo/ or from the RSR Up settings and have them synchronised?

Ideas on the simple solution welcome!

— Reply to this email directly or view it on GitHub https://github.com/akvo/akvo-product-design/issues/40#issuecomment-47748259.

Synchronising anything between app and server has the same complications as updates. There is always a chance that the first of two operations will happen and the second not. Since this is not so critical, I suppose one way to have few troublesome states is to include the settings first in every update upload. If the upload succeeds, then the settings did, too. But if 2 apps on the same account keep changing the settings, things could easily get very confused.

adriancollier commented 9 years ago

This has been implemented.