[Koha-patches] [PATCH] [SIGNED-OFF] Bug 5373: Adds cardnumber to the field list of the Import Patrons NOTES.

[Nicole Engard]

From: Garry Collum <gcollum at gmail.com>

Adds 'cardnumber' as an option to the list of possible fields in the NOTES section of the patron import tool.

Signed-off-by: Nicole Engard <nengard at bywatersolutions.com>
---
 .../prog/en/modules/tools/import_borrowers.tmpl    |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/koha-tmpl/intranet-tmpl/prog/en/modules/tools/import_borrowers.tmpl b/koha-tmpl/intranet-tmpl/prog/en/modules/tools/import_borrowers.tmpl
index 510c8d7..80d7979 100644
--- a/koha-tmpl/intranet-tmpl/prog/en/modules/tools/import_borrowers.tmpl
+++ b/koha-tmpl/intranet-tmpl/prog/en/modules/tools/import_borrowers.tmpl
@@ -144,8 +144,8 @@
 <ul>
 <li>The first line in the file must be a header row defining which columns you are supplying in the import file.</li>
 <li><b>Download a starter CSV file with all the columns <a href="?sample=1">here</a>.</b>  Values are comma-separated.</li>
-<li>OR choose which fields you want to supply from the following list:<ul><li>
-    <!-- TMPL_LOOP name="columnkeys" -->'<!-- TMPL_VAR name="key" -->', <!-- /TMPL_LOOP -->
+<li>OR choose which fields you want to supply from the following list:<ul>
+<li>'cardnumber'<!-- TMPL_LOOP name="columnkeys" -->, '<!-- TMPL_VAR name="key" -->'<!-- /TMPL_LOOP -->
 </li></ul></li>
 <!-- TMPL_IF NAME="ExtendedPatronAttributes" -->
 <li>If loading patron attributes, the 'patron_attributes' field should contain a comma-separated list of attribute types and values. The attribute type code and a colon should precede each value. For example: <b>INSTID:12345,LANG:fr</b> or <b>STARTDATE:January 1 2010,TRACK:Day</b>. If an input record has more than one attribute, the fields should either be entered as an unquoted string (previous examples), or with each field wrapped in separate double quotes and delimited by a comma: <b>&quot;STARTDATE:January 1, 2010&quot;,&quot;TRACK:Day&quot;</b>.  The second syntax would be required if the data might have a comma in it, like a date string.
-- 
1.5.6.5