comma separated reports and commas in author names
Hello, Using a snapshot of 3.0 (ver. 3.01.00.001). When I generate a report listing all the catalog items, includes a column for authors, and saving that report comma separated, Base (OOo) treats the authors' last names and first names as different columns (the two parts of names are separated with commas). Is this something I cannot avoid while using comma separated columns or has this problem not been noticed yet? I then saved that report using tabs as separators and it worked properly though. So since Koha has this option of comma separated columns and I am noticing commas in authors' names, perhaps either we (as in 'we in our library') have the authors' names in a wrong format or the comma separated option in Koha is kind of inappropriate for this purpose. Comments? Regards.
Hi, Had similiar problem when converting data from other ILS to Koha-compatible format. I guess such 'collisions' are normal and unavoidable, and there`s nothing permanent we can do about it. It`s not a real pain, though - it would be, if you couldn`t choose separator other than comma. I chose a '{}' separator and got used to using it very quickly. Conclusion: it`s a minor inconvenience, not a real problem - just like adjusting seat and mirrors in a new car. Regards, Tomasz.
Dear Koha Colleagues, Does someone have a good copy of the 3.0 tar.gz? This one unpacks with errors: http://download.koha.org/koha-3.00.00.tar.gz 2.2.9 works alright, but I want to try the latest. Thank you, David -- ITEACHNET.ORG http://iteachnet.org * Sustainable Learning Technologies by International Knowledge Networks, Co., Ltd., Thailand Linux and Open Source/ Cross-platform Everything: Training, hosting, design, development, Server admin, network admin. 66(0)84 329 1183 (cell phone); 66(0)2 260 0640 (office); 66(0)2 260 0646 (fax); E-mail: information@iteachnet.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
On Mon, Sep 8, 2008 at 9:06 AM, David M. Bucknell <dbucknell@iteachnet.org> wrote:
Dear Koha Colleagues,
Does someone have a good copy of the 3.0 tar.gz?
This one unpacks with errors:
Hi David - What kind of errors do you get? I can use that file with no problems, and I haven't heard others report problems. The version I get from the download link is 49266888 bytes and has an md5sum: 0008f53d22333f7f2beb55d9a23b792a -Andy
Hi Andrew, You were right. I was downloading with wget and somehow that corrupted it. Downloading via Firefox worked. Hmm. Sorry for the false report. David ----- Message from andrew.moore@liblime.com --------- Date: Mon, 8 Sep 2008 09:59:50 -0500 From: Andrew Moore <andrew.moore@liblime.com> Reply-To: Andrew Moore <andrew.moore@liblime.com> Subject: Re: [Koha] tar.gz unpacking errors with koha-3.00.00.tar.gz To: "David M. Bucknell" <dbucknell@iteachnet.org> Cc: koha@lists.katipo.co.nz
On Mon, Sep 8, 2008 at 9:06 AM, David M. Bucknell <dbucknell@iteachnet.org> wrote:
Dear Koha Colleagues,
Does someone have a good copy of the 3.0 tar.gz?
This one unpacks with errors:
Hi David -
What kind of errors do you get? I can use that file with no problems, and I haven't heard others report problems.
The version I get from the download link is 49266888 bytes and has an md5sum: 0008f53d22333f7f2beb55d9a23b792a
-Andy
----- End message from andrew.moore@liblime.com ----- -- ITEACHNET.ORG http://iteachnet.org * Sustainable Learning Technologies by International Knowledge Networks, Co., Ltd., Thailand Linux and Open Source/ Cross-platform Everything: Training, hosting, design, development, Server admin, network admin. 66(0)84 329 1183 (cell phone); 66(0)2 260 0640 (office); 66(0)2 260 0646 (fax); E-mail: information@iteachnet.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Tomasz Holdowanski wrote:
Hi, Had similiar problem when converting data from other ILS to Koha-compatible format. I guess such 'collisions' are normal and unavoidable, and there`s nothing permanent we can do about it. It`s not a real pain, though - it would be, if you couldn`t choose separator other than comma. I chose a '{}' separator and got used to using it very quickly. Conclusion: it`s a minor inconvenience, not a real problem - just like adjusting seat and mirrors in a new car.
Regards, Tomasz.
Yup, I agree that it is an inconvenience since using tab as a separator works. I thought I should at least mention it here. Future readers will see that it hasn't gone un-noticed and that it is a known issue with a solution or work around. However, what's not clear to me is why is there an option of the comma separators at all since it is bound to create problems in author fields at least if not in others. You chose "{}". How do you select your own separator? I only have the commas and tabs as two options. Regards.
participants (4)
-
Andrew Moore -
David M. Bucknell -
H.S. -
Tomasz Holdowanski