http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5379 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #7 from Katrin Fischer <katrin.fischer@bsz-bw.de> 2010-11-15 09:01:52 UTC --- Not sure I tested the right thing, but here are my results ;) I tested on current HEAD and on the new branch new/awaiting_qa/bug_5379 with different test cases for 2 patron attributes. The file I used was loaded successfully before in 3.01.61. I used a unique patron attribute as matching key during import, overwriting matching records, replacing all patron attributes. "BORROWER#:222,SECOND_ID:222" Overwriting to existing patrons with attributes works without problems. --- "BORROWER#:223,SECOND_ID:222" For testing I changed one of the matching keys, so that one patron would be added as new to the database. I got following error message for this patron: 1 not imported because they are not in the expected format (last...) I think the error is due to the already existing cardnumber in my database. After I changed the cardnubmer too, the patron loaded without problems. A better error message would be good. --- "BORROWER#:222","SECOND_ID:224" I changed my patron attributes in an attempt to follow the help instructions. This resulted in deletion of my second patron attribute from the overwritten patron record. No error message was displayed, although the number of fields was not matching my header row. The help seems not correct here or is misleading? --- "BORROWER#:222,'SECOND_ID:224, test'" Deleted both patron attributes from the existing patron. --- "'BORROWER#:222','SECOND_ID:224, test'" 1 not imported because they are not in the expected format .. What is the right syntax to import more than 1 patron attribute with patron attributes containing commas? -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.