Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9

This tool is designed for importing candidate images (i.e. headshots) en masse into Flow for Elector. In preparation for using this tool, all the candidate headshots should be placed into a single folder. The tool uses the headshot name to search for matching candidates that are available in the Flow database and then assigned the images as matches are found.

Headshot filename format

The filename format is composed of 3 sections with each section separated by an underscore character ( _ ):

Format

Example

1

Last Name

all UPPERCASE letters
replace all spaces with an underscore character _

LASTNAME
LASTNAME1_LASTNAME2

2

First Name

First letter upper case and the rest lowercase
replace all spaces with an underscore character _

If there is more than a single first name, the names should be concatenated with the underscore character

Firstname
First_name

Firstname1_Firstname2

3

Party Code

a single word with all UPPERCASE letters

PC
LIB

Examples

Generic Format Sample

Specific Sample

LASTNAME_Firstname_PARTY

TRUDEAU_Justin_LIB

LASTNAME1_LASTNAME2_Firstname_PARTY

VAN_DER_VEEN_Jessica_NDP

LASTNAME_Firstname1_Firstname2_PARTY

LEBLANC_Paul_Emile_PC

Hyphenated Names

Note that hyphenated names are treated as a single word by the tool. For example, 'GOODWIN-CLAIRMONT_Vanessa_GRN' indicates that the candidate's last name is: 'Goodwin-Clairmont' and the first name is 'Vanessa'. The same goes for first names. For example, 'ZHANG_Regan-Heng_GRN' indicates that the candidate's last name is 'Zhang' and the first name is 'Regan-Heng'.

Troubleshooting

Tip

Take a closer look at the log file that is generated by the tool. Most likely there will be some unmatched headshot images after the tool is run, particularly on the initial runs.

The tool tries its best to match the candidate names and party information parsed from the filenames against the information in the Flow database. The most likely cause of these mismatches will be that the candidate names in the Flow database do not match exactly the name parsed from the headshot files.

The simplest way to solve this issue is to modify the mismatching filenames such that the candidate names match exactly and then re-run the tool again. Alternatively, If there are less than a handful of unmatched headshots left, you can opt to use the Flow interface to assign the headshot images to the candidates manually.


  • No labels