For all tasks which are focused around people (Create/update people, Credit volunteers with hours globally, Add/remove people from lists, and others), you have three options:
If none of these apply, IFI will ignore that record and continue on to the next.
For these people-focused tasks, you should always enable the "Person lookup" module, and provide it as many fields as you have available. The more data you give it, the better a job it will do in finding the person in VSys, and in sorting the most likely prospects to the top.
These are the fields that the person lookup module can use. All of them refer to the current person.
Field |
Explanation |
Example value |
Family name |
Last name |
|
First name |
Given name |
|
Full name |
Given name and family name |
|
Middle name |
|
|
Name backwards |
Family and given name, family name first |
|
Gender |
|
|
Phone |
Any phone number. Any formatting is ignored |
|
Any standard e-mail address, capitalization is ignored |
|
|
Age |
Age as of the current date |
|
DOB |
Date of birth. For dBase and Excel, enter dates so that the source program understands them; for tab-delimited, use |
|
Address |
First line of any address |
|
City |
City/town/village for any address |
|
State |
State/province for any address |
|
Postal code |
Zip/postal code for any address |
|
Person number |
The Person number field on the Additional data panel |
|
Import reference |
For people previously imported from Volunteer Works or other programs, the ID they had in that previous application |
|
Type |
Existing person type |
|
Person lookup module-specific options
Person lookup import reference offset |
When data is being imported from multiple databases, e.g. two or more Volgistics systems, the imported ID value for a person such as Kiosk ID would often be duplicated, with people in both systems sharing the same value. To work around that, put an import reference offset here, e.g. "SOUTH". When looking for a person, and the Import reference ID value is "1234", VSys will instead look for "SOUTH1234". |
If a person does not exist... |
If this is checked, and an incoming record has enough data to create a person, if IFI cannot find an existing person it will make a new one without first prompting you. |