Differences

This shows you the differences between two versions of the page.

--- reference:system-architecture:address-editing-application [2025/09/01 18:56] – runarbe
+++ reference:system-architecture:address-editing-application [2025/09/01 22:45] (current) – [Data editing process] runarbe
@@ Line 54: / Line 54: @@
       * Creates, updates, deletes streets, address units
       * Creates, updates, deletes issues
+      * Largely, the functionality in the app covers most needs - however, from experience using it, there may be things that could be tweaked or adjusted to make it easier to use
   * When the user has identified a number of issues that require field verification, she can export data for field verification (optional)
       * The data can be all data within the area being edited
@@ Line 59: / Line 60: @@
       * The data should be exported to a format suitable for import and use in the mobile field verification application
       * Alternatively, the data can be posted to a web service provided by the mobile field-verification app and it will autoamatically be allocated to a user as per processes there
-      * Question: It is necessary to establish a format for data exchange between the field-verification application and the address editor application
+      * Question: **It is necessary to establish a format for data exchange between the field-verification application and the address editor application**
-      * Question: It is necessary to establish a clear boundary between what the **mobile**  field-verification application does and what the **desktop **address editing application does
+      * Question: It is necessary to establish a clear boundary between what the **mobile**  field-verification application does and what the **desktop **address editing application does. These two applications must be used in symbiosi <font inherit/inherit;;inherit;;inherit></font>
   * When field verification is done data should be handed back to the editing application
       * Any observations made in the field should be edited and dealt with
@@ Line 74: / Line 75: @@
       * The QC user can reject all or street by street
       * If rejected, the concerned parts go back to the editing step
-  * At the outset, someone is at MoHUP, in future, once "flown for 140 hours" others can be given qa role
+      * If all or a selection of streets are approved - those data are checked in, unlocked and removed from the checked out set
-  * Edits are presented street by street
+      * Question: **Who does the QC, is it anyone - just peer review - or is it someone on Governorate level? A thorough review requires detailed local knowledge**
-  * Approvals can be given street by street
+  * Data are checked back into the addressing database
-  * Rejected streets should have a note
-  * Note should be returned to user
-  * Someone (?) approves data
-  * Data are checked back in
 ===== Status =====