Many of our customers work with different networks that have overlapping members. It is usually the case that each network will be managed in a separate sumApp project, be shown in it's own Kumu map and have different kinds of questions. But in a Tier IV account, where there is an overlap of members between two or more of the projects within a single account, you can import the rank-able question connections from the population of one project into another - thereby reducing the 'ask' of those overlapping members.
4) Run the import matching function based on the mapping indicated. Takes you to the next import step.
5) Store the mapping for future use.
When mapping options, you are defining how to translate the selections in one dataset into the, potentially different, options in another datasest.
So, in the example above:
- First note that in this instance, the sending project (#1) and the receiving project (#2) have the same number of options. It could also be that you have more options on either side than the other.
- In this instance, the option language is very similar, so we can just select the corresponding option on the right side for each option on the left.
- It will end up looking like the image below.
It won't always be that simple a correspondence. You may even choose not to import some responses because there simply isn't a good option to map it to in the receiving project.
- For instance, suppose you have 'I know of this person' on the left, but on the right, you only have options for actual relationships, not just 'knowing of'. In that case, you shouldn't map the connection. You'd select 'None' from the drop-down list on the right.
- Or perhaps you have 4 options on the left, to move into just 2 options on the right. You might end up with something like the image below.
The bottom line is - be sure to think through your option mapping carefully!
Step 4 - Saving the mapping
If you know you plan to repeat this exact import again, in exactly the same way, it will save a little time if you save what you just mapped out.
To do that, click 'Store mapping'.
1) Name the mapping set - keeping in mind that each stored mapping has to have a different name, so be as specific as possible.
2) Click on 'Save mapping'
Step 5 - Review list of possible imports and select whose connections to import
Once you have run your option mapping by clicking on the 'Map Connections' button on the mapping page, you will see the import list.
1) It lists everyone who a) exists in both projects and b) had connections to others in both projects
2) It lists how many connections each person has that can be imported - note that it only shows if there are NEW connections to import, it doesn't count connections imported previously. (in this case, there are only a couple new members in the receiving list for connections to be imported for)
3) Select which members connections to import. You may have some reason not to import someone's connections - this enables you to leave those individuals not selected.
4) Back - takes you back to the import mapping page.
5) Import - runs the import and takes you to the connections list - which is sorted on the most recent - so you can see the connections that came over.