The import file has to be a text file (with <code>.txt</code> at the end) encoded in UTF-8. It has to <strong>strictly</strong> follow the required format.
<h4>Required manipulation using the web interface</h4>
<p>
The following tables can not be imported from a file and have to be manipulated using the web interface.
</p>
<ul>
<li>
Semester
</li>
<li>
Program
</li>
<li>
Part
</li>
<li>
User
</li>
<li>
Assistant
</li>
<li>
Experiment
</li>
<li>
Semester Experiment
</li>
</ul>
<h4>Optional values</h4>
<p>
If an attribute is optional/nullable and has no value, then <code>NULL</code> (uppercase) has to be written.
</p>
<h4>How to understand the tables in the next section</h4>
<h5>ID</h5>
<p>
None of the mentioned ids in the import file is meant as a database id. The ids here only refer to the imported instances. The id in the database is assigned automatically.
</p>
<p>
Here is the format of a table in the "Tables" section:
</p>
<h5>Table</h5>
<ul>
<li>
id → 0 / 1 / 2 / ... (starts with 0 and has step
If <code>student_number</code> is found in the database but <code>first_name</code>, <code>last_name</code> or <code>uni_email</code> do not match, a warning is given during the import. Pay attention to warnings!
</li>
<li>
<code>bachelor_thesis</code> and <code>bachelor_thesis_work_group</code> are only updated in the database if they are not <code>NULL</code>. This prevents overriding values written using the web interface.
</li>
<li>
If <code>note</code> is not <code>NULL</code> then it is appended to the note in the database if the student already exists in the database. It will not overwrite existing notes.