Discussions in progress. Next steps:
...
Phase 1: Get a hierarchy defined in the CGR into Reveal. Cover these this Jira storiesstory:
https://smartregister.atlassian.net/browse/RVL-
...
Phase 1 Option (all would need to support client-based sync changes) | Pros | Cons | Est. LOE |
---|---|---|---|
Akros would run one instance of CGR to minimize server costs. Requires a one way sync to Reveal from CGR. | One server, one set of costs Production environment for managing location data UI for file prep UI for management Relatively easy “upload”/”download” Open doors to other use of CGR Less GIS experience needed | Additional platform to support, train on, maintain, host (server implications). CGR current limitations - can only visualize one layer at a time, file types for imports are not unrestricted. Manual fixes to hierarchy may take longer in CGR than if someone with GIS experience is doing in QGIS or ArcGIS. | ~2 weeks of exploration, scoping, spec writing (Akros). ~1 week Tf time to customize export format for CGR to fit Reveal. ~1 week Ona time to support and do lite dev as needed Server-set up and monthly support cost (one server - could be shared across implementations) |
As clients have requirements to host own CGR instance, could set up own server and solution. Can do both 1a and 1b depending on client need. | Above, plus full country ownership of hierarchy. | Added cost to own servers. | Same as above but server-set up and monthly support cost, per implementation (could be offset if country self manages) |
2. CGR as a master list. Cloud service | Above, plus benefits of cloud hosting (less downtime, security, streamlined support) | Policy restrictions on this option. | Same as 1.a. |
3. Reveal as master list. UI to load, view, edit, manage locations | Streamlined platform for users. | Rebuilding towards what is already in CGR. May be more than what is really needed. | Significant development effort. We will not pursue this option. |
4. Reveal as master list. Import/Export tool in OpenSRP | Streamlined platform for users. Scripts for start of this already exist. Bulk fix of errors is easier. | No UI for management. Requires skillset to do upfront GIS work to get into correct format for Reveal. | ~3 weeks Ona time |
...