I have several user fields that use taxonomy-based terms (e.g., languages spoken by user) that I would like to import into my D7 site.

I believe that I need to "explode" the terms using feeds tamper, but I would like to know if there are other steps I need to take and also to confirm that this is known to work for users, and not just for nodes.

Also, I already have the taxonomy terms in the D7 database so I would like to match the terms rather than the term IDs. Is that feasible?

Comments

twistor’s picture

All of those things should work. Make sure you configure the target to search by term name. Have you actually tried it yet?

nielsvoo’s picture

Issue summary: View changes

Maybe i don't understand you answer right but it looks like this target "search by term name" option is only available in the taxonomy processor and not for the user processor. In my case i just want to import users were some fields containing term names. I want to connect those on the available options in a list not by term ID but by Term Name.

How can i achieve this?

Thanks in advance.
Nielsvoo

MegaChriz’s picture

Status: Active » Fixed
  1. Add a taxonomy reference field on the user account. To do this, go to Administration > Configuration > People > Account settings > Manage fields (admin/config/people/accounts/fields) and there add a field of type "Term reference". Call the field for example "Interests" (field_interests).
  2. Create a feed importer and as processor select "User processor".
  3. On the mapping settings, map your source field to the taxonomy reference field. If you called that field "Interests" as in the example, map the field to "Interests (field_interests)".
  4. On the target configuration you can configure how terms should be searched by and if it should create new terms if they are not found. The defaults should be fine, which is "Search taxonomy terms by: Term name".

Use the taxonomy term processor if you only want to import terms themselves (without associating them with user or node).

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.