How do I map and manage translations for faith, gender, and ethnicity?

Peter Rasmussen -

Updated 02/02/15 AA

It is important to map (and translate, if possible) the faith, gender and ethnicity of sources so that these sources can be searched by these demographics. You may come across unmapped source demographics as you read source responses, as you search for sources or if you communicate directly with sources. Some values remain unmapped because AIR has not been told to automatically map those words. (You can change this by using translations, described below.)

Because PIN gives sources the option to write in and describe their own faith, gender and ethnicity in their own words, it would be impossible to automatically map everything. It is possible, however, to manually map these descriptors per source, or create what we call a translation that will automatically do so for any future source who writes in the same thing. If you map source faith, gender and ethnicities as you come across them, your source pool will continue to be accurate for searching and profiling.

  • If you have writer-level AIR access or above, you can map these demographics for individual sources.
  • If you have manager-level AIR access, you can also create translations for demographic descriptors.


To map faith, gender and ethnicity for a single source, do this:

When you find a source who has written a description of their ethnicity, for example, that can be mapped, go to the source profile and open up their source demographics box to edit their ethnicity.


Make the appropriate ethnicity selection and save it. This will save this single source's mapped ethnicity going forward and it will now be searchable. 


This source's ethnicity is now mapped and saved. 



To map descriptors using the Translation tool, do this:

Note: Users with the role of Manager only may manage translations.

First, get to the Manage Translations tool, like this:


Next, pick a translation type:


You can update existing translations:




And add new translations:


Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk