# Reviewer Import

**External persons** who do not yet have a Converia account are often responsible for evaluating contributions. In order to assign the contributions to the persons who are to take on the role of reviewer and then to inform them from within the system about the start of the contribution evaluation, they must be entered in Converia. This is usually done by importing reviewers.\
\
The reviewer import works in exactly the same way as the [normal person import](https://manual.converia.de/teilnehmende/personen-und-teilnehmende-verwalten/personen-in-converia-importieren), except for some additional information, and is described in detail in this chapter.

### Preparation of the import data in Excel

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FBEkhhpYsuyWJO1LViMm1%2Fimage.png?alt=media&#x26;token=285f6914-5da7-4273-a571-1a41f2d65787" alt=""><figcaption><p>Fig. 1: Import template + reviewer import</p></figcaption></figure>

To ensure that the importer can process the data correctly, it is necessary to follow the specifications of this import template **exactly**. The CSV template file can be opened and edited as usual in Microsoft Excel. The two sample data sets can be removed.

Leave empty the columns for which there are no values (do **not** delete or reorder these columns).

#### The mandatory information for the data records to be imported is:

* Surname (*Last Name* column)
* Country (*Country* column) – Use the ISO codes (ISO 3166-2 alpha-2 code list, second column in this [Wikipedia list](https://de.wikipedia.org/wiki/ISO-3166-1-Kodierliste)).
* E-mail address (*E-Mail* column) – If the e-mail address is invalid, the personal data record will not be imported.
* Language (column U Lang) – use the language codes DE, EN or FR (only the languages activated for this conference can be used).
* Short title of the topics (column Y Topic List (Short Name)) - separate the entries with commas and without spaces, using the pattern **abc,xyz,123**

The short description of the contribution topics can be defined in the contribution topic setup itself:

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FFWc2SSW8PZbl10U7WywY%2Fimage.png?alt=media&#x26;token=71286457-7ea0-485b-8bef-9d0cbfee5f50" alt=""><figcaption><p>Fig. 2: Abbreviated description of the article topic</p></figcaption></figure>

### Person data records

Personal data sets can be imported with or without a Converia account.

#### Import person with account

A data record can be imported **with an account** by entering a user name (column E *User name*). The data subjects should be informed that an account already exists for them. Otherwise, there is a risk that the persons will create another account, thereby creating [duplicates](https://manual.converia.de/de/teilnehmende/personen-und-teilnehmende-verwalten/doppelte-personeneintraege-finden-und-abgleichen.html).

#### Import person without account

A record can be imported **without an account** by leaving the E column empty. Affected persons should then be able to define their own password and username by clicking on an activation link that can be [sent by email](https://manual.converia.de/preview.php/de/allgemeines/e-mails-aus-converia/anwendungsfaelle/accountinformationen-fuer-importierte-personen-versenden.html), thus activating the Converia account for the imported personal record. Without this activation via link, a duplicate will be created each time the person logs in at the frontend.

{% hint style="warning" %}
For data protection reasons, it is not recommended to import passwords for accounts at this point. For the same reasons, there is no password replacement function for Converia mailings, for example. However, you can send a link to people with an account, which they can use to request a new password. People without an account can set their password using the activation link.
{% endhint %}

### Change the encoding to UTF-8

To ensure that **special characters and umlauts are imported correctly**, it is necessary to set the encoding of the CSV import file to **UTF-8**. To do this in Excel, please save the file as “CSV UTF-8 (separated by commas) (\*.csv)”.&#x20;

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2F2bwbRcxHq40fs9D8uJ6g%2F2025-04-08_15h01_38.png?alt=media&#x26;token=7a967194-76f8-4dfb-88a9-5e981286bed0" alt=""><figcaption><p>Fig. 2: Save import data as CSV with UTF-8 encoding in Excel</p></figcaption></figure>

### Importing data into Converia

* *Show preview* (no import will be carried out at this point).

* The following **error messages** may appear at this step:
  * *Invalid email address.* > Check the email address in the line indicated. The problem may be a space before or after the email address.
  * *Invalid country code. This must correspond to the ISO code.* > Check the country code in the line indicated.
  * *An inactive language is to be imported.* > Change the language in the given line.
  * *Wrong number of columns, use the template.* > Deleting, moving or adding columns causes this error message.

* Check whether all data records are displayed correctly. **Particular attention should be paid to umlauts and special characters.**<br>

  <figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FSXoUw2fogqrqcIJdtAqg%2Fimage.png?alt=media&#x26;token=91dc9948-ce5b-4bab-9c5c-5e20225fd25c" alt=""><figcaption><p>Fig. 6: Incorrect display of special characters</p></figcaption></figure>

* If error messages appear or the display of umlauts and special characters is incorrect, the data records in the import template must be corrected and the conversion to UTF-8 repeated.

* All **records can be checked individually** by clicking on *Next data record example* below (no import will take place yet).

* Make sure that the records have been imported as valuers. If it says No here, you have forgotten to tick the box in the previous step.

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2F5LPepxx7ULT1pwGyPW1Z%2Fimage.png?alt=media&#x26;token=a3af46a4-59e9-4235-9e43-80fb04a6c862" alt=""><figcaption><p>Fig. 7: Final check and import</p></figcaption></figure>

* The *Start import* button only appears under the data records when there are no more error messages.

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FYysD6GBJ7VVMegNw6P4H%2Fimage.png?alt=media&#x26;token=047fa991-749b-42ee-b1d0-449e2418e74a" alt=""><figcaption><p>Fig. 7: Download report</p></figcaption></figure>

* Subsequently, a log is created of how the import went.

{% hint style="warning" %}
If personal data records already exist in the system before the import, it is recommended that you run a duplicate comparison after the import in case there are now duplicate personal records.
{% endhint %}

\
\ <br>

\
\
\ <br>

\ <br>

\ <br>

\ <br>
