View | Details | Raw Unified | Return to bug 19012
Collapse All | Expand All

(-)a/koha-tmpl/intranet-tmpl/prog/en/modules/help/tools/import_borrowers.tt (-1 / +1 lines)
Lines 18-24 Link Here
18
18
19
<p style="color: #990000;">Important: Date formats should match your system preference, and must be zero-padded, e.g. '01/02/2008'.</p>
19
<p style="color: #990000;">Important: Date formats should match your system preference, and must be zero-padded, e.g. '01/02/2008'.</p>
20
20
21
<p style="color: #990000;">Important: The fields 'branchcode' and 'categorycode' are required and must match valid entries in your database.</p>
21
<p style="color: #990000;">Important: The fields 'cardnumber', 'surname', 'branchcode', and 'categorycode' are required. Branchcode and categorycode must match valid entries in your database.</p>
22
22
23
<p style="background-color: #ffe599">Tip : If loading patron attributes, the 'patron_attributes' field should contain a comma-separated list of attribute types and values.</p>
23
<p style="background-color: #ffe599">Tip : If loading patron attributes, the 'patron_attributes' field should contain a comma-separated list of attribute types and values.</p>
24
<ul>
24
<ul>
(-)a/koha-tmpl/intranet-tmpl/prog/en/modules/tools/import_borrowers.tt (-2 / +1 lines)
Lines 219-225 If an input record has more than one attribute, the fields should either be ente Link Here
219
    <ul><li>Example 3: &quot;STARTDATE:January 1, 2010&quot;,&quot;TRACK:Day&quot;</li></ul>
219
    <ul><li>Example 3: &quot;STARTDATE:January 1, 2010&quot;,&quot;TRACK:Day&quot;</li></ul>
220
The second syntax would be required if the data might have a comma in it, like a date string.</li>
220
The second syntax would be required if the data might have a comma in it, like a date string.</li>
221
[% END %]
221
[% END %]
222
<li><b>Required fields: </b>The fields 'branchcode' and 'categorycode' are required and must match valid entries in your database.</li>
222
<li><b>Required fields: </b>The fields 'cardnumber', 'surname', 'branchcode', and 'categorycode' are required. Branchcode and categorycode must match valid entries in your database.</li>
223
<li><b>Password: </b>Values for the field 'password' should be stored in plaintext, and will be converted to a Bcrypt hash (if your passwords are already encrypted, talk to your system administrator about options).</li>
223
<li><b>Password: </b>Values for the field 'password' should be stored in plaintext, and will be converted to a Bcrypt hash (if your passwords are already encrypted, talk to your system administrator about options).</li>
224
<li><b>Date formats: </b> Date values should match your system preference, and must be zero-padded.
224
<li><b>Date formats: </b> Date values should match your system preference, and must be zero-padded.
225
    <ul><li>Example: '01/02/2008'</li></ul>
225
    <ul><li>Example: '01/02/2008'</li></ul>
226
- 

Return to bug 19012