"term ids need to be specific only for duplicate term names in order to identify each item"

I was importing a very big vocabulary with this module but couldn't solve some problems.
I had some dupilcated term, let's say cities with the same exact name of the countries (that are parents of that cities) and so for those I used:

Term1,Term1_city,locality,,0,1,1,0,0,Synonim,Term1 <- this last Term1 is the parent (in the next line)
Term1,,locality,,0,0,1,4,0,Child1,Child2,Child3,Child4,Term1_city <- this last Term1_city is the city child with the same name of the country father (I used the id, the second word in previous line)

Well, using this lines gave me a messy vocabular.

I also tried to replicate the bug in a easy way.
Construct a vocabulary like this:

Parent
    |-- Child1
    |-- Parent

Export it via “CSV Export”(full term fields and links)
and re-import it via “CSV Import” and you’ll see...

Comments

Daniel_KM’s picture

Daniel_KM commented

Hi,

That is right, there is a problem when duplicate terms are used with this import mode.

Often, I explain not to use duplicate terms, as they are difficult to manage by the web manager or the end user... So the first suggestion is to use terms as "Roma (provincia)" and "Roma (city)" :

Parent (Urban area)
    |-- Child1
    |-- Parent (City)

The second suggestion is to use hierarchical tree structure import mode, because there is no bug with this mode :

parent, child1
parent, parent

The third suggestion is useful if duplicate terms are not too many : you can add a code to duplicate terms, import them with full term import mode, and edit them manually after import process.

The last suggestion is to wait for a patch...

Daniel Berthereau
Knowledge manager

Balbo’s picture

Balbo commented

Thx Daniel, I actually did apply for the first suggestion.

I posted this because it was a bug I didn't find in the issue queue.

Daniel_KM’s picture

Daniel_KM commented
Version: 6.x-4.9 » 6.x-4.10

Hi,

I just released the bug fix, so you can use now "full term fields and links" import with duplicate terms.

Sincerely,

Daniel Berthereau
Knowledge manager

Daniel_KM’s picture

Daniel_KM commented
Status: Active » Closed (fixed)