Bug 17151 - Extended patron attributes not importing when using double quotes
Summary: Extended patron attributes not importing when using double quotes
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-19 01:03 UTC by Danielle Elder
Modified: 2020-01-10 11:40 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Danielle Elder 2016-08-19 01:03:05 UTC
Patron import tool directions on Patron Import Tool Page states:
_____________

   Example 2: STARTDATE:January 1 2010,TRACK:Day

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:

    Example 3: "STARTDATE:January 1, 2010","TRACK:Day"

The second syntax would be required if the data might have a comma in it, like a date string.
____________

Only the second example works "STARTDATE:January 1 2010,TRACK:Day"

The double quotes import does not work. Loading the patron will fail with a "Line 2 could not be parsed!" error. 

Partners of BWS are also reporting this same behavior.
Comment 1 Carlos Lopez 2018-11-15 02:21:55 UTC
We've found (version 1711) that if we do not double-quote or separately double-quote patron attributes only one will be loaded
(example 1: ORG:PILGRIM,ROLE:UG)
(example 2: "ORG:PILGRIM","ROLE:UG")
but if we put double-quotes around the entire set of patron attributes they load properly
(example 3: "ORG:PILGRIM,ROLE:UG")