Commit | Line | Data |
---|---|---|
6a488035 TO |
1 | {* |
2 | +--------------------------------------------------------------------+ | |
232624b1 | 3 | | CiviCRM version 4.4 | |
6a488035 TO |
4 | +--------------------------------------------------------------------+ |
5 | | Copyright CiviCRM LLC (c) 2004-2010 | | |
6 | +--------------------------------------------------------------------+ | |
7 | | This file is a part of CiviCRM. | | |
8 | | | | |
9 | | CiviCRM is free software; you can copy, modify, and distribute it | | |
10 | | under the terms of the GNU Affero General Public License | | |
11 | | Version 3, 19 November 2007 and the CiviCRM Licensing Exception. | | |
12 | | | | |
13 | | CiviCRM is distributed in the hope that it will be useful, but | | |
14 | | WITHOUT ANY WARRANTY; without even the implied warranty of | | |
15 | | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. | | |
16 | | See the GNU Affero General Public License for more details. | | |
17 | | | | |
18 | | You should have received a copy of the GNU Affero General Public | | |
19 | | License and the CiviCRM Licensing Exception along | | |
20 | | with this program; if not, contact CiviCRM LLC | | |
21 | | at info[AT]civicrm[DOT]org. If you have questions about the | | |
22 | | GNU Affero General Public License or the licensing of CiviCRM, | | |
23 | | see the CiviCRM license FAQ at http://civicrm.org/licensing | | |
24 | +--------------------------------------------------------------------+ | |
25 | *} | |
26 | {htxt id="id-emailFormat-title"} | |
27 | {ts}Email Format{/ts} | |
28 | {/htxt} | |
29 | {htxt id="id-emailFormat"} | |
30 | {ts}Select the email format preferred by this contact. Select 'Both' to send HTML and Text formats.{/ts} | |
31 | {/htxt} | |
32 | ||
33 | {htxt id="id-bulkmail-title"} | |
34 | {ts}Bulk Mailings{/ts} | |
35 | {/htxt} | |
36 | {htxt id="id-bulkmail"} | |
37 | {ts}If you are using the CiviMail component to send mailings to contacts, this field provides additional control over which email address is used. By default, CiviMail sends mail to each contact's preferred email address. If the contact has multiple locations, then the preferred email of the primary location is used. However, if the contact prefers to have CiviMail ('bulk') mailings set to an alternate email address - check the 'Use for Bulk Mailings' box next to that email address.{/ts} | |
38 | {/htxt} | |
39 | ||
40 | {htxt id="id-optOut-title"} | |
41 | {ts}Opt Out{/ts} | |
42 | {/htxt} | |
43 | {htxt id="id-optOut"} | |
44 | {ts}This option is designed to be set by the contact themselves when they don't want to receive bulk email from your organization (they set it using the opt-out action from a CiviMail mailing). Please think before changing it, as it will override the preference they have set.{/ts} | |
45 | {/htxt} | |
46 | ||
47 | {htxt id="id-onhold-title"} | |
48 | {ts}Email Hold{/ts} | |
49 | {/htxt} | |
50 | {htxt id="id-onhold"} | |
51 | {ts}This flag is most commonly used to mark an email address that is bouncing. If you are using the CiviMail component, emails that bounce excessively are automatically placed on hold and mailings are not sent to this address as long as it is marked hold. You can also set (or unset) this option manually - but remember that emails will not be sent to this address as long as it is marked 'On Hold'.{/ts} | |
52 | {/htxt} | |
53 | ||
54 | {htxt id="id-preferred_communication_method-title"} | |
55 | {ts}Preferred Communication{/ts} | |
56 | {/htxt} | |
57 | {htxt id="id-preferred_communication_method"} | |
58 | {ts}Select the preferred method(s) of communicating with this contact.{/ts} | |
59 | {/htxt} | |
60 | ||
61 | {htxt id="id-privacy-title"} | |
62 | {ts}Privacy{/ts} | |
63 | {/htxt} | |
64 | {htxt id="id-privacy"} | |
65 | {ts}Select the appropriate Privacy Options.{/ts} | |
66 | <p>{ts}Contacts with 'Do not email' will be excluded from receiving CiviMail mailings, and the Send Email activity will be disabled for them. However they will still receive email for contribution receipts and event registration confirmations.{/ts}</p> | |
67 | <p>{ts}Contacts with 'Do not SMS' will be excluded from receiving Bulk SMS messages, and the Send SMS activity will be disabled.{/ts}</p> | |
68 | <p>{ts}Contacts with 'Do not mail' will be excluded when mailing labels are created.{/ts}</p> | |
69 | {/htxt} | |
70 | ||
71 | {htxt id="id-sharedAddress-title"} | |
72 | {ts}Shared Address{/ts} | |
73 | {/htxt} | |
74 | {htxt id="id-sharedAddress"} | |
75 | <p>{ts}Check this option if you want to link this address to another contact's address. For example, you might want to link a person's "Work" address to their employer's address. Or, you might want to link their "Home" address to a Household record. Changes made to the linked address will automatically be applied to this address. For example, if you use an employer (organization) address for an individual's work address - any updates to the employer address will also be applied to the individual's work address.{/ts}</p> | |
76 | <p>{ts}You can use an address belonging to an existing contact or create a new contact by selecting the desired contact type from the select field. If you link an individual's address to an organization, an employee-employer relationship will be automatically created. If you link an individual's address to a household, a household member relationship is created.{/ts}</p> | |
77 | {/htxt} | |
78 | ||
aa62b355 OB |
79 | {htxt id="id-communication_style-title"} |
80 | {ts}Communication Style{/ts} | |
81 | {/htxt} | |
82 | {htxt id="id-communication_style"} | |
83 | <p>{ts}Choose how you communicate with this contact, e.g. on formal or familiar terms.{/ts}</p> | |
84 | <p>{ts}Depending on the CiviCRM setup, email and postal greetings (see below) may be automatically adapted accordingly; or the information can be used in other ways.{/ts}</p> | |
85 | {/htxt} | |
86 | ||
6a488035 TO |
87 | {htxt id="id-greeting-title"} |
88 | {ts}Greeting{/ts} | |
89 | {/htxt} | |
90 | {htxt id="id-greeting"} | |
91 | {capture assign=docLink}{docURL page="user/common-workflows/tokens-and-mail-merge"}{/capture} | |
92 | <p>{ts}Use the greeting/address options to determine how you would like the contact's salutation and name displayed for different communication methods. When you send an email or export a list of records to a .csv file for mail merging, the greeting and addressee fields will reflect your preferences.{/ts}</p> | |
93 | <p>{ts 1=$docLink}You may also create a customized greeting and use field tokens to insert fields of your choice. For more information on available tokens, see the online documentation %1.{/ts}</p> | |
94 | {/htxt} | |
95 | ||
96 | {htxt id="id-edit-street-elements-title"} | |
97 | {ts}Street Address{/ts} | |
98 | {/htxt} | |
99 | {htxt id="id-edit-street-elements"} | |
100 | <p>{ts}CiviCRM will attempt to split street addresses into separate elements (street number, street name and unit/apt) to help you make lists and reports where you need to sort by street number (and/or separate addresses with odd and even numbers). For most addresses, this is done for you automatically. However, you can manually edit these elements, and potentially handle addresses that are in unusual formats, by clicking 'Edit Address Elements'.{/ts}</p> | |
101 | {/htxt} | |
102 | ||
103 | {htxt id="id-edit-complete-street-title"} | |
104 | {ts}Street Editing{/ts} | |
105 | {/htxt} | |
106 | {htxt id="id-edit-complete-street"} | |
107 | <p>{ts}Click here to return to editing the street address as a single field. Addresses which don't fit the expected format for address elements can still be saved by entering them in the single 'Street Address' field.{/ts} | |
108 | {/htxt} | |
109 | ||
110 | {htxt id="id-current-employer-title"} | |
111 | {ts}Current Employer{/ts} | |
112 | {/htxt} | |
113 | {htxt id="id-current-employer"} | |
114 | <p>{ts}You can select an existing organization record here, OR type in the name of a new organization if this person's employer is not already in your database. However, if you want this person to share their work address with their employer AND that organization doesn't exist yet - leave this field blank and use the Shared Address feature in the Address pane below to create the employer record AND enter the employer address. The 'current employer' relationship will be automatically created for you.{/ts}</p> | |
115 | {/htxt} | |
116 | ||
117 | {htxt id="id-website-title"} | |
118 | {ts}Website{/ts} | |
119 | {/htxt} | |
120 | {htxt id="id-website"} | |
121 | <p>{ts}Record one or more web addresses (URLs) associated with this contact. Examples include personal web addresses like a Facebook or Twitter page, as well as links to a company or organization web site or page.{/ts}</p> | |
122 | {/htxt} | |
123 | ||
124 | {htxt id="id-upload-image-title"} | |
125 | {ts}Contact Image{/ts} | |
126 | {/htxt} | |
127 | {htxt id="id-upload-image"} | |
128 | <p>{ts}Upload a photo or icon that you want to be displayed when viewing this contact.{/ts}</p> | |
129 | {/htxt} | |
130 | ||
131 | {htxt id="id-internal-id-title"} | |
132 | {ts}CiviCRM ID{/ts} | |
133 | {/htxt} | |
134 | {htxt id="id-internal-id"} | |
135 | <p>{ts}Every contact in CiviCRM has a unique ID number. This number will never change and is the most accurate way of identifying a contact.{/ts}</p> | |
136 | {/htxt} | |
137 | ||
138 | {htxt id="id-external-id-title"} | |
139 | {ts}External ID{/ts} | |
140 | {/htxt} | |
141 | {htxt id="id-external-id"} | |
142 | <p>{ts}Use this field to store a unique identifier. This is generally used to link contacts with records in a related or legacy application. When migrating data from another system, import the unique contact identifier from the old system to this field. You can then use it to match imported contributions and other transactional data to the corresponding contact record.{/ts}</p> | |
143 | {/htxt} | |
144 | ||
145 | {htxt id="id-address-name-title"} | |
146 | {ts}Address Name{/ts} | |
147 | {/htxt} | |
148 | {htxt id="id-address-name"} | |
149 | <p>{ts}Enter a descriptive name for this address block such as "Summer Home", "School Address", etc.{/ts} | |
150 | {/htxt} | |
151 | ||
152 | {htxt id="id-postal-code-suffix-title"} | |
153 | {ts}Postal Code Suffix{/ts} | |
154 | {/htxt} | |
155 | {htxt id="id-postal-code-suffix"} | |
156 | <p>{ts}Enter optional 'add-on' code after the dash ('plus 4' code for U.S. addresses).{/ts}</p> | |
157 | {/htxt} | |
158 | ||
159 | {htxt id="id-geo-code-title"} | |
160 | {ts}Geocoding{/ts} | |
161 | {/htxt} | |
162 | {htxt id="id-geo-code"} | |
163 | {capture assign=docLink}{docURL page="user/initial-set-up/installation-and-basic-setup" text="(Refer to the Mapping and Geocoding section in the Installation and Basic Setup Chapter)"}{/capture} | |
164 | <p>{ts}Latitude and longitude may be automatically populated by enabling a Mapping Provider.{/ts} {$docLink}</p> | |
165 | {/htxt} | |
166 | ||
167 | {htxt id="id-geo-code-override-title"} | |
168 | {ts}Override Geocoding{/ts} | |
169 | {/htxt} | |
170 | {htxt id="id-geo-code-override"} | |
171 | <p>{ts}Check this box if you want to assign latitude and longitude manually rather than letting your mapping provider assign it. This is useful for addresses in locations where your mapping provider is not able to provide accurate geocoding.{/ts}</p> | |
172 | {/htxt} | |
173 | ||
174 | {htxt id="id-street-address-title"} | |
175 | {ts}Street Address{/ts} | |
176 | {/htxt} | |
177 | {htxt id="id-street-address"} | |
178 | <p>{ts}Street number, street name, apartment/unit/suite - OR P.O. box.{/ts}</p> | |
179 | {/htxt} | |
180 | ||
181 | {htxt id="id-supplemental-address-title"} | |
182 | {ts}Supplemental Address{/ts} | |
183 | {/htxt} | |
184 | {htxt id="id-supplemental-address"} | |
185 | <p>{ts}Supplemental address info, e.g. c/o, department name, building name, etc.{/ts}</p> | |
186 | {/htxt} | |
187 | ||
188 | {htxt id="id-source-title"} | |
189 | {ts}Contact Source{/ts} | |
190 | {/htxt} | |
191 | {htxt id="id-source"} | |
192 | <p>{ts}Use this field to store a description of how/why this contact was added to the database. This field is usually auto-filled when a contact is created from a public form i.e. Event Registration.{/ts}</p> | |
193 | {/htxt} | |
194 |