Extended import routine with import patterns and doublet check

From Wikipedia

To facilitate the import of contacts from external sources an editor for import patterns and a doublet check system have been implemented.

Import patterns:
Only in some cases the given field structure in the contacts manager of PHProjekt matches the order of the import table. For a one-time import the manual the rearranging of the columns of the import table might fit, but if you want to import an external table several times you should use the editor for the import patterns.

Since the import pattern only apply to csv files, you reach the editor via the menu 'import -> other table', the first form is below the dialogue for the real import.

You can create an new pattern, modify or delete an existing one. The import patterns belong only to the author. For the creation of modification of a pattern you are asked to upload an example import file in the csv format. This file will be queried and all fields with the value from the first row of this file will be displayed. Then the user can select a field from the contacts module which should match during the import. After saving the pattern you can apply the pattern in the import dialogue 'other format' and the import routine follows the filed assignment given in the chosen pattern.

Doublet check:

If you want to import an external contact list several times or some databases at once you face the same problem what to do with identical records. The new version of PHProjekt offers you to apply a user defined doublet check during the import.

After selecting one of the available import type s (e.g. KDE address book, Outlook) you get to the upload form the menu for the doublet check. This must be activated with the check box of the same name of course.

Then select those fields which should be taken for a check whether the content match any of the existing records.. The combination of these criteria is the condition that a import record will be regarded as a doublet of an existing entry in the database.

Now the user can select what should happen with the doublets:

• Discard the imported records, don't import them at all
• Assign the imported record as a child object of the parallel record.
• In the next version you will have the ability to replace the records in the database
  
  

Don't forget to approve your import list at the end!