Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Map Update - Ureport Project #1172

Open
evandrolohmann opened this issue Jan 3, 2024 · 2 comments
Open

Map Update - Ureport Project #1172

evandrolohmann opened this issue Jan 3, 2024 · 2 comments

Comments

@evandrolohmann
Copy link

Dear Team,

We would like to share a situation where your assistance is
highly appreciated. Weni is hosting one of the Ureport Projects for an Unicef Country office, where they have identified the need to update the current map/region within the Ureport Website. However, based on the logic of the platform, we understand that, once the maps are updated in the production environment,the metrics indicating the amount of answers from a previous region would not be available for polls lauched prior to this update.

Given this context we request your assistance to interpret this demand and guide us if there is a possibility to update the maps in the live workspace and after that reassess/resyncronize the results from the previous polls so that the metrics are not lost during this process.

In case you need any further details I remain available to discuss this situation during a meeting where we can assess the best course of action for this scenario.

Looking forward to your reply,

Weni Team.

@evandrolohmann
Copy link
Author

@ericnewcomer @norkans7 Any thoughts on this?

Kind regards

@norkans7
Copy link
Contributor

I do not think there will be any issue updating the locations maps, the locations data is maintained on RapidPro side and then U-Report will sync that.

The location objects on U-Report will be update using the OSM_ID matching to update the name.

And yes, you can always resync the stats for any poll using

def pull_refresh_task(self):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants