Importing conflict
Trunkhorn - April 3, 2009 - 16:14
| Project: | Taxonomy CSV import/export |
| Version: | 6.x-2.4 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
For example, when importing these 2 items in a csv:
USA,States,Alabama,Counties,Autauga
and
USA,States,Arizona,Counties,Apache
with the option selected for:
Child term names or one term array structure
and
Ignore existing terms and create new ones
The result is that the "Apache" county for "Arizona" is going under "Counties" below "Alabama"
and
"Counties" is not being written as a child for "Arizona", only for "Alabama"
Even if I manually create "Counties" as a child for "Arizona" and then try to import
USA,States,Arizona,Counties,Apache
the same result occurs. Of course, this is on a much larger number of items, but I believe that simplifies as best I can.
#1
Hi,
Currently, Taxonomy csv doesn't allow duplicate words and "Ignore existing items and creates new ones" is an option about terms in an existing vocabulary and not about imported terms.
But you're right, it should be possible to import this type of words list (with "non indexable" terms) and it's an important item in the to do list (next month).
Presently, the solution is to remove States and Counties.
Sincerely,
Daniel Berthereau
Knowledge manager
#2
Hello Daniel,
Thanks for a lightening fast response. What was actually interesting is that when I ran a test using those same settings, but actually chopped off the items below counties, taxonomy csv allowed the duplicates for each state to have its own "Counties" tag under it. I was quite surprised by that.
So for the full list it allowed duplicates with this example:
USA,States,Alabama,Counties
and
USA,States,Arizona,Counties
But wouldn't allow each of those counties to be used differently, even though each of those "counties" had their own specific termID.
You probably know that already, but I thought I'd share that anyway. I will definitely keep this module on my radar and check out your changes.
#3
Hi,
To import a structure is complex and it is even more when there are duplicates.
The problem is to recognize what existing term matches with imported term. Currently, as in older versions of taxonomy_csv, it is not possible to have duplicates for parents, but only for the last term of a line and if the option is "ignore".
Next release will clarify this type of problem, as you can see in help since the 3.0 release.
Regards,
Daniel Berthereau
Knowledge manager