This module allows to import/export taxonomies, structures or simple lists of terms into/from a vocabulary from/to a CSV file, a url or a copy-and-paste text.
Csv format is a simple list of values separated by a delimiter, often comma (,) or semicolon (;), and enclosures, often quotation marks ("). If you are unsure how to create a CSV file, you might want to use OpenOffice Calc or another spreadsheet application to export your data into a CSV file.
Multiple formats can be used to import or export vocabulary. Except with some formats, the first column contains the term name. You can specify what you want to export and how additional columns should be imported.
Vocabulary structure should be imported first when multiple files are used. So choose options Fields and links, flat, structure, polyhierarchy, first level of parents or children before relations, descriptions, etc.
Terms are imported as simple terms. Additional columns are ignored. Example:
DiamondGoldWoodThis option allows to import full term definitions and direct links to other terms.
Format is: term name, term id, vocabulary id, term description, weight, number of synonyms, number of first level parents, number of first level children, number of related terms, list of synonyms, list of first level parents ids, list of first level children ids, list of related terms ids, list of vocabulary ids of related terms.
Only term name should be defined. Other values can be empty. Ids are not internal term ids or vocabulary ids, but a unique identifiant. Ids can be a number or a name. In most case, you can use true name. In fact, term ids need to be specific only for duplicate term names in order to identify each item. So for duplicates, you can use term name with a serial number. Main term id is needed only when term name is a duplicate one.
Example with one synonym, two first level parents, no children, one relation with a term of another vocabulary:
Drupal, , Knowledge management, "Created by Dries Buytaert in 1998", 10, 1, 2, 0, 1, Drop, CMS, CMF, Open source, SoftwareTerm 1, , Vocabulary 1, "Description of term 1", 10, 1, 2, 0, 1, Synonym 1, Direct parent 1, Direct parent 2, Related term 1, Vocabulary of related term 1With this source content, destination is determined by source. If third column is empty, a new vocabulary will be created. If it's a name or a number, a vocabulary will be created if it doesn't exist. This process is used for related terms too. If vocabulary of a related term is not defined, vocabulary of main term is used. Warning: It's not recommended to change the vocabulary of a term with links.
A simpler option, Full term definitions, allows to import only definitions.
Use this option to import a lot of terms in order to create a flat vocabulary. All items in your file will be imported as terms. Example:
Clothes, Trees, HousesParis, DrupalUse this option to create a tree structure of a vocabulary (geography, classification...). To import a hierarchy with multiple parents as a genealogical one, it's advised to use "Polyhierarchy", "First level children" or "First level parents" imports.
Your file can be written with two schemes and a mixed one.Animal, Mammal, WhaleAnimal, Mammal, MonkeyAnimal, Mammal, HumanMammal, HumanMammal > is imported as a first level term and not as a < Animal > term child as in previous line.
World Asia Japan Tokyo Korea Seoul
World,Asia,,Japan,,,Tokyo,,Korea,,,Seoul,Europe,,France,,,Paris,,Italia,Abruzzo,Chieti,Chieti,,,,,CivitaluparellaParis > will be automatically added as a child of < France > and so on.
Partial lines are allowed, so a next line can be:
,,Switzerland,BernSwitzerland > will be added as a child of < Europe > and of course < Bern > as a child of < Switzerland >.
In same way, above lines can be simplified to:
World, Asia, Japan, Tokyo,, Korea, SeoulWorld, Europe, France, ParisSeoul > will become a child of < Japan >.
Use this option to create a a polyhierarchical structure, as a genealogy.
Format is the same than tree structure: each term is the child of previous item: parent, child, sub-child... and so on.
There are four differences. First, the first item doesn't need to be a root. Second, duplicate terms are always merged, except when one is the direct parent of the other one, because it's forbidden in Drupal. So, if the vocabulary is monohierarchical and without non-direct duplicate terms, as in the previous geographical example, result is the same than with previous option. Third, lines can be partial too, but in some case of duplicates, result may differ. Last, polyhierarchy can be recursive.
For example, lines may be:
Grand-Mother, Mother, DaughterGrand-Father, Mother, SonGrand-Mother 2, Father, DaughterGrand-Father 2, Father, Son , , Son 2 , UncleGrand-Mother 2, UncleFather, Son 3This choice allows to create a vocabulary in which terms can have more than one parent, as in a genealogy (polyhierarchy).
The first item is imported as a term, the second and next as first level parents of first term. For example, lines may be:
Daughter, Mother, FatherSon, Mother, FatherSon 2, FatherSon 3, FatherMother, Grand-Mother, Grand-FatherFather, Grand-Mother 2, Grand-Father 2Uncle, Grand-Mother 2, Grand-Father 2This choice allows to create a vocabulary in which terms can have more than one parent, as in a genealogy (polyhierarchy).
The first item is imported as a term, the second and next as first level children of first term. For example, lines may be:
Mother, Daughter, SonFather, Daughter, Son, Son 2, Son 3Grand-Mother, MotherGrand-Father, MotherGrand-Mother 2, Father, UncleGrand-Father 2, Father, UncleWarning: in Drupal 7, related terms have been removed and replaced by fields. So this option is available only with Drupal 6. To get same functionnality, you need to create a "relations" field.
Use this option to create links between terms, as "see also" in an encyclopedia.
The second and next columns will be imported as related terms of the first column term. For example, a line may be:
Baobab, Madagascar, GhostBaobab > will be related to < Madagascar > and < Ghost >. An option allow you to create subrelations, here between < Madagascar > and < Ghost > (see below).
This option allows to import full term definitions. Format is: name, weight, description, list of synonyms if any. Example:
Street, 1, "A urban way", Avenue, RoadFull term fields and links, allows to import not only definitions, but links to other terms too.
The second column will be imported as the term description of the first column term. Example:
"Baobab","An African tree"The second column will be imported as weight of the term defined by first column. Example:
Baobab, 3The second and next columns will be imported as synonyms terms of the first column term. Example:
"United Kingdom","Great Britain","England"This format is used by Taxonomy manager to export vocabularies. Columns are: vocabulary id, term id, term name, term description, first level parent 1, ..., first level parent n. Example:
"1"; "25"; "Louis XVII"; "King of France"; "Louis XVI"; "Marie-Antoinette"Taxonomy CSV allows to import structure and properties of terms.
Source can be configured with the first field set. See formats.
You can import your terms from a file or with a text area. Simply check your choice. File can be a local file path or a url.
Advanced settings allows to set non standard delimiter and enclosure.
You can import your terms in a existing vocabulary or create a new one. You can import your terms too in a duplicate of an existing vocabulary.
When you want to import a new taxonomy into an existing one, it is recommended to process in three steps in order to allow a good import.
If you only want to create a new vocabulary, the first choice is sufficient, unless when you have multiple files for one vocabulary.
When source content is Full term definitions and links, destination is determined by source. If third column is an id, a new vocabulary will be created. If it's a name, a vocabulary will be created if it doesn't exist. If it's empty or zero, a vocabulary will be autocreated, duplicated or used depending on the destination option. This process is used for related terms too.
Destination can be configured with the next field set. You can specify what will become existing terms. Four choices are possible, or less matching your source content:
Update current terms when name matches with imported ones and merge existing descriptions, parents, synonyms and related terms with new ones. Duplicates are removed. This choice is recommended if you want to keep a vocabulary and if you have descriptions, parents, synonyms and related terms you don't want to lose.
Update current terms if name matches, but remove existing descriptions, parents, synonyms and related terms. Choose this option if you are want to create a clean new vocabulary without losing existing terms.
Be careful: if there is no description, parent, synonym or related term, i.e. the line contains only a term in the first column, this removes the existing.
Let current terms as they are and create a new term for the first column term.
Warning: This can create duplicate terms. It is recommended to use this option only if you are sure that imported taxonomy contains only new terms or if your vocabulary allows multiple parents.
Create a new term for each term on the line.
To import big taxonomies (from 1000 or 10000 lines depending on the server) when access to time and memory settings of server are forbidden, it is recommended first to disable some other taxonomy related modules as "pathauto" before import. Settings aren't lost when you disable a module - and not uninstall it -. After import process, modules can be reactivated.
Second, you can use file import. Third, you can reduce log level. Fourth, you can use these tweaks.
To disable internal cache allows to import vocabularies of any size. Internal cache is used to speed up process, to reduce access to sql base and to be informed about process. When disabled, no information about results can be displayed except eventual first error or warning.
As to calculate vocabulary hierarchy is memory intensive, this option allows to set hierarchy manually without verify it.
If you are sure that vocabulary to import is well formated (utf8, order of items...), you can disable checks. This option increases import speed by 5%.
Taxonomy CSV allows to export structures et properties of terms of one or all vocabularies.
Simply choose what you want to export (see formats) and how to export. Some formats may be unavailable.
," by default, semicolon ";" or tabulation) between terms can be chosen in Advanced settings in the second fieldset. You can choose a custom delimiter too. Delimiter is a one character string. Example with delimiter < ¤ >:term 1¤This field has commas, a semicolon (;), a quotation mark (") and a tabulation, but it will be correctly imported."), specialy if they contain non-ASCII letters or if imported items, in particular descriptions, contain the chosen delimiter. Example:"term 1","This field has a comma, but it will be correctly imported."") are automatically managed.
To import terms, user need one permission:
To export terms, user need one permission:
These permissions are often associated with these ones:
Another Drupal module allows CSV import too, despite its name: taxonomy XML. Its approach is different: it uses one file compliant to thesauri standard ISO 2788, i.e. a three columns csv file: term, type of link (relation, description, synonym...), item, or, for specialists, subject, predicate, object. Additional fields are managed as the third one. For Drupal 4.7 and Drupal 5, taxonomy batch operations is available too. So choose the module best matching your needs.
For export, you can use Taxonomy XML too or one of backup modules. Taxonomy CSV is a more specialised tool which allows more precise tuning.