Table of Contents
The contact module allows you to manage, well, contacts. Those can be business-related or private. It can handle individuals and companies, and much more. This chapter explains the contact module, including it's configuration.
You can import contact data from vCard files. more.groupware supports vCard files with one or multiple contact definitions in them. It can set the private option according to the vCard's CLASS type, can create company entries from ORG definitions if you like, and supports most of the basic data a vCard can hold.
To import a vCard, click on the 'Import vCard File' link in the submenu, enter the file's location in the form field and click on 'Import'. The file will be processed, and you will see the contact list again. A notice will tell you how many contacts and/or companies have been created.
![[Note]](images/admonitions/note.png) | Note |
|---|---|
The HOME and WORK types for emails are not used. In fact the type parameter is completely ignored for email addresses. Currently the following entities are unused and get silently ignored: FN, PHOTO, LABEL, MAILER, TZ, GEO, ROLE, LOGO, AGENT, CATEGORIES, PRODID, REV, SORT-STRING, SOUND, UID, KEY as well as any extended (X-) types. This may seem like a long list, but some just have no corresponding field in the more.groupware database and most are almost never used. The FN entity is ignored as we use the N entity to fetch the name from a vCard. Future versions of more.groupware may add support for PHOTO, TZ, GEO, ROLE, LOGO and CATEGORIES. The following 'meta information' entities are silently ignored as well: NAME, SOURCE. This shouldn't hurt anybody... really. | |
Here are some more notes about how vCard processing works: