dhis2-devs team mailing list archive

[noreply@xxxxxxxxxxxxx]

------------------------------------------------------------
revno: 709
committer: Morten Olav Hansen <mortenoh@xxxxxxxxx>
branch nick: dhis2-docbook-docs
timestamp: Thu 2013-03-21 17:40:47 +0700
message:
  import-export: more about conflicts, identifier matching
added:
  src/docbkx/en/resources/images/import_export/import_summary_conflicts.png
modified:
  src/docbkx/en/dhis2_user_man_import_export.xml


--
lp:~dhis2-documenters/dhis2/dhis2-docbook-docs
https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs

Your team DHIS 2 developers is subscribed to branch lp:~dhis2-documenters/dhis2/dhis2-docbook-docs.
To unsubscribe from this branch go to https://code.launchpad.net/~dhis2-documenters/dhis2/dhis2-docbook-docs/+edit-subscription

=== modified file 'src/docbkx/en/dhis2_user_man_import_export.xml'
--- src/docbkx/en/dhis2_user_man_import_export.xml	2013-03-21 09:47:30 +0000
+++ src/docbkx/en/dhis2_user_man_import_export.xml	2013-03-21 10:40:47 +0000
@@ -148,9 +148,33 @@
             <emphasis role="bold">1</emphasis> new organisation unit, <emphasis role="bold"
             >1332</emphasis> updated, and <emphasis role="bold">4</emphasis> organisation unit
           levels.</para>
+        <para>Below you can see another example.</para>
+        <mediaobject>
+          <imageobject>
+            <imagedata width="100%" fileref="resources/images/import_export/import_summary_conflicts.png"/>
+          </imageobject>
+        </mediaobject>
+        <para>Here you can see that the organisation unit Nduvuibu MCHP had a unknown reference to
+          an object with UID "aaaU6Kr7Gtpidn", which means that an object with this UID was not
+          present in your imported file, and it could not be found in the existing database. Its
+          important to note that even if a reference could not be found, the object will still be
+          imported, but you might have to fix this directly in DHIS 2 later, if the reference should
+          have pointed to something else.</para>
       </section>
     </section>
     <section>
+      <title>Matching identifiers in DXF2</title>
+      <para>The DXF2 format currently support matching for two identifiers, our own UID, and also a
+        possible external identifier called code. When our importer is trying to search for
+        references (like the one above), it will first go to the UID field, and then to the code
+        field. This allows you to import from legacy systems without having a UID for every metadata
+        object. I.e. if you are importing facility data from a legacy system, you can leave out the
+        UID field completely (DHIS 2 will fill this in for you) and the put the legacy systems own
+        identifiers in the code field, this identifier is required to be unique. This not only works
+        for organisation units, but for all kinds of metadata, allowing for easy import from other
+        systems.</para>
+    </section>
+      <section>
       <title>Importing data from DHIS 1.4</title>
       <para>There are two ways to import data from a DHIS 1.4 database; 1) through the 1.4 XML-based export files, or 2) directly from the DHIS 1.4 data file (.mdb). Both are accessible from the DHIS 1.4 Import menu under Import in the Import-Export module.</para>
       <para>It is critical that all data integrity violations which are present in the DHIS 1.4 database be fully resolved before attemtping an import into DHIS 2. You can check the data integrity of DHIS 1.4 through the CORE Module-&gt;Advanced-&gt;Data integrity checks. A report will be generated of all data integrity violations which should be resolved prior to importing into DHIS 2.</para>

=== added file 'src/docbkx/en/resources/images/import_export/import_summary_conflicts.png'
Binary files src/docbkx/en/resources/images/import_export/import_summary_conflicts.png	1970-01-01 00:00:00 +0000 and src/docbkx/en/resources/images/import_export/import_summary_conflicts.png	2013-03-21 10:40:47 +0000 differ