Bug 241842 - In new version when exporting address book (csv) fields are missing and language of field names are mixed up
Summary: In new version when exporting address book (csv) fields are missing and langu...
Status: RESOLVED LATER
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-15 19:36 UTC by Martin L ü c h e m
Modified: 2010-06-30 11:38 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
difference between header from csv export (10.05 KB, application/vnd.oasis.opendocument.spreadsheet)
2010-06-22 15:15 UTC, Martin L ü c h e m
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin L ü c h e m 2010-06-15 19:36:53 UTC
Version:           unspecified (using Devel) 
OS:                Linux

I export address book to csv. Now most of the germand field names dissappear and some are mixed up. This makes it impossible to reuse this as databse input for serial letters.

Reproducible: Didn't try




OS: Linux (x86_64) release 2.6.32-5-amd64
Compiler: cc
Comment 1 Tobias Koenig 2010-06-17 15:16:51 UTC
Hej,

can you please be more specific what is wrong?
I can't get any valuable information from 'get mixed up' or 'disappear'.
Attaching some example files would help to illustrate the problem...

Ciao,
Tobias
Comment 2 Martin L ü c h e m 2010-06-22 15:15:35 UTC
Created attachment 48224 [details]
difference between header from csv export
Comment 3 Martin L ü c h e m 2010-06-22 15:18:03 UTC
Hi Tobias,

sorry for the unclear description. I was a bit astonished about the differences. In my opion a change like that should have offered a way of conversion from Version a to version b. Address data is such an important data that changes of fields are not easy to handle.

A) What did I do?

1. Switched to the new akonadi version of kaddressbook

2. Export of addressbook data to csv

3. Trying to use the export file as import für serial letter used before within my oartner program

B) What is the difference between the two csv files?

1. Export alte Version																		Formatierter Name	Nachname	Vorname	Zusätzliche Namen	Titel-Abk. (vor Name)	Titel-Abk. (nach Name)	Spitzname	Geburtstag	Straße (privat)	Staat/Bundesland (privat)	Staat/Bundesland (privat)	Postleitzahl (privat)	Land (privat)	Aufkleber (Privatadresse)	Straße (geschäftlich)	Stadt (geschäftlich)	Staat/Bundesland (geschäftlich)	Postleitzahl (geschäftlich)	Land (geschäftlich)	Aufkleber (Geschäftsadresse)	Telefon (privat)	Telefon (geschäftlich)	Mobiltelefon	Fax privat	Fax (geschäftlich)	Autotelefon	ISDN	Pager	E-Mail-Adresse	Mail-Programm	Titel	Rolle	Organisation/Firma	Abteilung	Notiz	Homepage	Beruf	Name des Assistenten	Name des Managers	Name des Partners	Büro	IM-Adresse	Jahrestag	Blog

2. Export alte Version																
Formatted Name	Honorific Prefixes	Given Name	Additional Names	Family Name	Honorific Suffixes	Nick Name	Geburtstag	Jahrestag	E-Mail (bevorzugt)	E-Mail (2)	E-Mail (3)	E-Mail (4)	Home Address Street	Home Address City	Home Address State	Home Address Zip Code	Home Address Country	Home Address Label	Business Address Street	Business Address City	Business Address State	Business Address Zip Code	Business Address Country	Business Address Label	Home Phone	Business Phone	Mobile Phone	Home Fax	Business Fax	Car Phone	ISDN	Pager	E-Mail-Programm	Title	Role	Organisation	Notiz	Homepage																C) The problem

1. Why mixing up german and english filed names?

2. Why are there different fields? Why are there less (!) fields in the new version?

3. Why is it impossibel to edit the fields "Formatted Name	Honorific Prefixes	Given Name	Additional Names" directly within the frontend?

=> it is impossible to use this as an import file to e.g. Open Office database because a) field names are mixed up and b) how shall I be sure that this will not change with the next release? Please remember: Open Office will not directly read the csv file!

Regards, Martin
Comment 4 Tobias Koenig 2010-06-30 11:12:07 UTC
Regarding your questions:

1) I don't know why mixes up German and English translations, I guess the
   of the translations are not installed correctly.

2) Why there are less fields: KAddressBook in 4.4 is a complete rewrite of the codebase of 4.3,
   therefor there has been some regressions (aka not all features of previous version have been ported).
   I think in a future version they will be back

3) Dito, in KAddressBook 4.5 the editor for the single name parts will be back.

4) I can't follow you why it should be _impossible_ to import the new CSV format into OpenOffice.
   Whether the header is German or English is absolutely irrelevant to import something and OpenOffice
   allows to reorder columns after import, so you can adapt the new format easily to the old format.
   Note that CSV is not standardized from the sematical point of view, so there is no need that the
   sequence of columns must be kept the same over time. The CSV importer must be flexible enough to
   cope with it.
Comment 5 Martin L ü c h e m 2010-06-30 11:38:48 UTC
Hallo Tobias Koenig,

Am Mittwoch, 30. Juni 2010, um 11:12:10 schrieb Tobias Koenig:
> 1) I don't know why mixes up German and English translations, I guess the
>    of the translations are not installed correctly.

I did not change anything in this area, so why should this been mixed up?

> 
> 2) Why there are less fields: KAddressBook in 4.4 is a complete rewrite of
> the codebase of 4.3,
>    therefor there has been some regressions (aka not all features of
> previous version have been ported).
>    I think in a future version they will be back

This would be very useful!

> 
> 3) Dito, in KAddressBook 4.5 the editor for the single name parts will be
> back.
> 
> 4) I can't follow you why it should be impossible to import the new CSV
> format into OpenOffice.
>    Whether the header is German or English is absolutely irrelevant to
> import something and OpenOffice
>    allows to reorder columns after import, so you can adapt the new format
> easily to the old format.
>    Note that CSV is not standardized from the sematical point of view, so
> there is no need that the
>    sequence of columns must be kept the same over time. The CSV importer
> must be flexible enough to
>    cope with it.

Well if you link the OpenOffice Database to a table, then the fild names 
should not change. Ifthere is a good reason to change them - ok! But in this 
case I cannot see any reason. Unfortunately in Open Office the only import 
form Kaddressbook that works is csv...

Regards, Martin