Changes between Version 8 and Version 9 of UserGuidelines/Importer

Timestamp:

08/18/10 15:30:33 (14 years ago)

Author:

Shikhar Kohli

Comment:

--

UserGuidelines/Importer

@@ -9 +9 @@
   * Referenced resources, like pr_person in org_staff, can be imported as well.
   * Records, which could not be validated, are not inserted into the database. These records are displayed to the users in a spreadsheet interface. Records have at least one field in red. 
-   This is the field with in incorrect value. The format in which errors are displayed is :  ''' <field-name>: <error> . You entered <value entered by user> '''. Records can then be corrected and re-imported.
+   This is the field with an incorrect value. The format in which errors are displayed is :  ''' <field-name>: <error> . You entered <value entered by user> '''. Records can then be corrected and re-imported.
   * The spreadsheet importer uses the Jaro-Winkler metric to determine the similarity of two rows. Similarity between rows is checked two at a time. Similar rows are displayed consecutively in another spreadsheet like interface. The user can choose to edit, delete and then import these rows to the database. Errors in these rows are displayed in the same form as described previously.
 
@@ -21 +21 @@
    * Tips:
      * Keep a single worksheet in the spreadsheet.
-     * Keep the number of rows around 100. More rows require more rendering and processing,therefore more time. This could also cause server requests to time out.
+     * Keep the number of rows around 100. More rows require more rendering and processing,therefore more time. This could also cause server requests to time out. (Please note, 100 rows is by no means a limitation, it is a simply a safe number of rows to render and import, keeping in mind the strength of internet connection. The number of rows isn't really a problem in an offline client of course)
 
 
@@ -64 +64 @@
   * Operations that can be performed in this step are identical to step 5.
 
+Limitation:
+  * You cannot import the same spreadsheet again. Causes duplicacy and outright rejection of some records from the database.
+  * Bugs, listed below
+
+Some bugs and improvements:
+  * Need to remove console.log in the JS code. These are very helpful when debugging, so I'll remove them when the project is merged. Also, redirection is currently commented out, will be removed when importer is merged.
+  * Mapping to organisation_id --> org_organisation --> comments works in some cases and does not work in others.
+  * Better representation of nested resources.
+  * The UI of the stages in the wizard may be modified suitably.
+
 == Ushahidi ==
 XSLT available to import Ushahidi data into Sahana Eden's Incident Reporting system