Well I just spent all morning wrestling with this, so I figured I'll post my results here.
First, the above awk magic from versatil looks promising, but I didn't seem to have the same csv file format that he was using. I noticed that if I chose to export to "Outlook contacts", then the resulting CSV file did have the field "CATEGORY". So theoretically just rearranging that awk command could have helped, and I would have done this for a smaller number of lines. I was dealing with hundreds of contacts, with multiple-line notes and other complications.
So. I eventually discovered that the
REST down/up-loads *do* actually contain tag information. The problem is that they refer to the tags by id, not by name.
My source/destination servers were the result of zmztozmig, and the actual tags themselves had been created for me on the new server. Same name, different IDs.
On each server, you can see the user's tag list like so
Quote:
|
zmmailbox -z -m username gat
|
I found that using a combination of createTag, deleteTag, and renameTag, I was able to make the destination server's tag list have the same IDs as the source server.
Once the tags have the same ID's on source and destination server, the REST file format download and upload resulted in the desired effect: the destination address book now shows each contact as having the same tags it had in the source.
Quote:
curl -u username : password http://server/service/home/username/contacts.tgz
curl -u username : password --upload-file contacts.tgz ttp://server/service/home/username/contacts?fmt=tgz
|