You are here

README.txt in Taxonomy Manager 6.2

Same filename and directory in other branches
  1. 8 README.txt
  2. 5 README.txt
  3. 6 README.txt
  4. 7 README.txt
  5. 2.0.x README.txt
README - TAXONOMY MANAGER 
**************************


SHORT PROJECT DESCRIPTION
--------------------------
This module provides a powerful interface for managing vocabularies of the taxonomy module.
It's especially very useful for long sets of vocabularies.

Features:
  * dynamic tree view
  * mass deleting
  * mass adding of new terms
  * moving of terms in hierarchies
  * merging of terms
  * fast weight changing with up and down arrows (and AJAX saving)
  * AJAX powered term editing form
  * simple search interface


REQUIREMENTS
------------
  - Taxonomy module enabled
  - JavaScript enabled in your browser
  - a user with 'administer taxonomy' permission


INSTALLATION
------------
1. Place the entire taxonomy_manager directory into your Drupal sites/all/modules/ directory.

2. Enable the taxonomy manager module by navigating to:

     administer > site building > modules


USING THE TAXONOMY MANAGER
--------------------------
To use the Taxonomy Manager go to administer > content management > taxonomy manager. This page
contains a list of all available vocabularies. By clicking at one of the vocabularies, you get 
redirected to the Taxonomy Manager interface, where you can edit the whole tree structure and
terms. 
If you want to edit any general vocabulary settings or if you want to create a new one, go to 
the categories (administer > content management > categories) page.

The interface contains a search bar, a toolbar with some operations, a tree view and if a term
gets selected a form for editing the term data.
The following lines describe all operations and some terminology.

 - Tree View
     The tree view shows all terms of the vocabulary with their hierarchical relations. If your
     list of terms gets very long, there is a paging mechanism included with a page size of 50 terms. 
     If you are having hierarchical vocabularies, all parent terms have a plus symbol, which 
     means you can expand them to show their child terms. Use the minus symbol to collapse
     them again.
     In multiple hierarchies, if one term has more parents, the term gets shown under 
     each of its parents. 
     
 - Adding of terms
     For adding new term, click on the 'Add' Button. A fieldset containing some textfields expands.
     If you want to close this fieldset, click 'Cancel'.
     To insert a new term, fill in any textfield. Each textfield can only contain one term. 
     You don't have to fill in all textfields, they can be left empty. 
     Depending on your hierarchy settings, it's possible to insert terms and to directly assign 
     a parent to them. If you want to do this, select a parent term in the tree view by marking 
     the checkbox. If you have multiple hierarchies enabled, it's even possible to assign the 
     new inserted terms to more parents at once by selecting more terms in the tree view.
     
 - Weight Editing
     Every term has a weight. This weight determines the position the terms get listed. If terms
     have the same weight, they are ordered alphabetically. 
     If you want to change the weight, you have 3 ways to do that.
       1st way: select the terms you want to move by one position (can be more terms at once) and press
                either the up or the down button in the toolbar. All saving is done automatically through 
                AJAX.
       2nd way: every term in tree view has a mouseover effect. When you move your mouse over a term, two
                small up and down arrows will appear. Click them to move this term by one
                position.
       3rd way: click on the term, where you want to change the weight. A form for editing the 
                term data appears on the right side of the tree view. At the bottom of this 
                form, there is a select field, which shows the current weight. By changing the
                value, the tree view gets automatically reordered and the values are saved to the
                database through AJAX.
 
 - Deleting
     If you want to delete terms from the vocabulary, select them by marking the checkbox and click
     the 'Delete' button. A fieldset, where you have to confirm the deletion, expands. 
     For hierarchical vocabularies (single or multi), the fieldset contains an option, which says:
     'Delete children of selected, if there are any'. Check this if you want to delete all children 
     of a selected parent term. Otherwise, if you are deleting the last parent of terms, the terms
     get added to root level.

 - Moving
     This operation is only available in hierarchical (single or multiple) vocabularies. It allows
     you to change hierarchies by moving terms from one parent to one other.
     Select all terms you want to move by marking the checkbox. Click the 'Move' button. A fieldset with
     some options expands.
     This fielset contains a autocomplete field, where you have to determine the parent term (under which
     the terms should be moved). If you want to move terms to the root level, leave this field empty. 
     This autocomplete form allows you to either choose a parent term from the list of exisitng terms
     or to insert a new terms, which will be used as parent (this parent term will be added to the root 
     level). 
     In multiple hierarchical vocabularies, it's possible to move terms to more parents in one step by
     inserting more terms into the autocomplete field and separating them by commas. Additional, there
     appears an option ('Keep old parents and add new one'), which prevents the replacing of old parents.
 
 - Merging
     With the merging action, you can put terms with the same meaning together (e.g. your vocabulary
     contains: SoC, Summer of Code, GSoC, Google Summer of Code). All terms, that get merged into 
     one other, get synonyms of resulting term (here called merged or main term). Additional
     all term-node association gets automatically updated (this means nodes, that had a merging term
     assigned, now get the resulting merged term instead). All merging terms are deleted afterwards. 
     In the Taxonomy Manager, you can do that by selecting all terms you want to merge and to click
     the 'Merge' button. A fieldset with an autocomplete field an some options expands. In the 
     autocomplete field you have to specify the resulting merged term (into which the selected get merged). 
     The merged term can be either chosen from the list of existing terms or can be inserted automatically
     and used as merged term.
     Additional, there are some options available (they depend on the vocabulary settings). If you want
     to add any kind of relations (parents, children, related terms) from the merging terms to the
     resulting merged term, select one (or more) of them.
     
     The default taxonomy term page, which shows all assigned nodes, is overriden by the Taxonomy
     Manager, so that former merged terms can be considered (if someone calls a term, that was merged, 
     it redirects to the resulting merged term).
     
     NOTE: At the moment, the Taxonomy Manager only cares about the term-node association inserted
           into the term_node table (by the taxonomy module). If you are using any CCK modules, like 
           CCK Taxonomy or Content Taxonomy, which (can) save the term - node association in cck tables, 
           don't use the Merging action, because changes are not handled.
           If you are using Views filters instead of the default taxonomy term page, merged terms are 
           either respected.
           If you want to customize this by yourself or have some other module, you can use following 
           function taxonomy_manager_merge_get_main_term($tid) for getting the main term id (if there 
           is any main term, else return 0). The term merge history gets saved in the 
           taxonomy_manager_merge table (main_tid, merged_tid) and gets additional cached, so that 
           checking for a merged terms causes nearly no performance loss.
 
 - Editing term data
     If you want to edit or read some term properties, click on the term. A fieldset on the right side
     of the tree view gets loaded. This contains all term related information and can be edited. If you
     want to change the term name or the description, fill in any changes you want and click the saving 
     symbol. All saving is done through AJAX, so no reload is necessary.
     Additional, this page contains listing of synonyms, related terms and parents (depends on your 
     vocabulary settings). 
     Every listed entry has an delete operation. By clicking the delete symbol, the relation gets deleted.
     In case of synonyms, the names get deleted from the database. If you are deleting a related term or a 
     parent, this doesn't delete the term itself, only the relation. 
     For adding new synonyms, the listing has a textfield below. Insert there any new synonym and click the 
     plus symbol.
     For adding a new related term or a new parent (if multi hierarchy), there is a autocomplete field below
     the listing. Use this to insert new terms or to choose existing ones and assign them to the current term. 
 
 - Using the search
     At the top of the page, there is a collapsed fieldset, called 'Search'. This search allows you to 
     directly select an existing term for editing. Else, if your input doesn't match an existing term, 
     the value will be used for filtering root level terms (this doesn't affect any child term).



AUTHOR
------
Matthias Hutterer 
User: mh86@drupal.org
Email: m_hutterer@hotmail.com

File

README.txt
View source
  1. README - TAXONOMY MANAGER
  2. **************************
  3. SHORT PROJECT DESCRIPTION
  4. --------------------------
  5. This module provides a powerful interface for managing vocabularies of the taxonomy module.
  6. It's especially very useful for long sets of vocabularies.
  7. Features:
  8. * dynamic tree view
  9. * mass deleting
  10. * mass adding of new terms
  11. * moving of terms in hierarchies
  12. * merging of terms
  13. * fast weight changing with up and down arrows (and AJAX saving)
  14. * AJAX powered term editing form
  15. * simple search interface
  16. REQUIREMENTS
  17. ------------
  18. - Taxonomy module enabled
  19. - JavaScript enabled in your browser
  20. - a user with 'administer taxonomy' permission
  21. INSTALLATION
  22. ------------
  23. 1. Place the entire taxonomy_manager directory into your Drupal sites/all/modules/ directory.
  24. 2. Enable the taxonomy manager module by navigating to:
  25. administer > site building > modules
  26. USING THE TAXONOMY MANAGER
  27. --------------------------
  28. To use the Taxonomy Manager go to administer > content management > taxonomy manager. This page
  29. contains a list of all available vocabularies. By clicking at one of the vocabularies, you get
  30. redirected to the Taxonomy Manager interface, where you can edit the whole tree structure and
  31. terms.
  32. If you want to edit any general vocabulary settings or if you want to create a new one, go to
  33. the categories (administer > content management > categories) page.
  34. The interface contains a search bar, a toolbar with some operations, a tree view and if a term
  35. gets selected a form for editing the term data.
  36. The following lines describe all operations and some terminology.
  37. - Tree View
  38. The tree view shows all terms of the vocabulary with their hierarchical relations. If your
  39. list of terms gets very long, there is a paging mechanism included with a page size of 50 terms.
  40. If you are having hierarchical vocabularies, all parent terms have a plus symbol, which
  41. means you can expand them to show their child terms. Use the minus symbol to collapse
  42. them again.
  43. In multiple hierarchies, if one term has more parents, the term gets shown under
  44. each of its parents.
  45. - Adding of terms
  46. For adding new term, click on the 'Add' Button. A fieldset containing some textfields expands.
  47. If you want to close this fieldset, click 'Cancel'.
  48. To insert a new term, fill in any textfield. Each textfield can only contain one term.
  49. You don't have to fill in all textfields, they can be left empty.
  50. Depending on your hierarchy settings, it's possible to insert terms and to directly assign
  51. a parent to them. If you want to do this, select a parent term in the tree view by marking
  52. the checkbox. If you have multiple hierarchies enabled, it's even possible to assign the
  53. new inserted terms to more parents at once by selecting more terms in the tree view.
  54. - Weight Editing
  55. Every term has a weight. This weight determines the position the terms get listed. If terms
  56. have the same weight, they are ordered alphabetically.
  57. If you want to change the weight, you have 3 ways to do that.
  58. 1st way: select the terms you want to move by one position (can be more terms at once) and press
  59. either the up or the down button in the toolbar. All saving is done automatically through
  60. AJAX.
  61. 2nd way: every term in tree view has a mouseover effect. When you move your mouse over a term, two
  62. small up and down arrows will appear. Click them to move this term by one
  63. position.
  64. 3rd way: click on the term, where you want to change the weight. A form for editing the
  65. term data appears on the right side of the tree view. At the bottom of this
  66. form, there is a select field, which shows the current weight. By changing the
  67. value, the tree view gets automatically reordered and the values are saved to the
  68. database through AJAX.
  69. - Deleting
  70. If you want to delete terms from the vocabulary, select them by marking the checkbox and click
  71. the 'Delete' button. A fieldset, where you have to confirm the deletion, expands.
  72. For hierarchical vocabularies (single or multi), the fieldset contains an option, which says:
  73. 'Delete children of selected, if there are any'. Check this if you want to delete all children
  74. of a selected parent term. Otherwise, if you are deleting the last parent of terms, the terms
  75. get added to root level.
  76. - Moving
  77. This operation is only available in hierarchical (single or multiple) vocabularies. It allows
  78. you to change hierarchies by moving terms from one parent to one other.
  79. Select all terms you want to move by marking the checkbox. Click the 'Move' button. A fieldset with
  80. some options expands.
  81. This fielset contains a autocomplete field, where you have to determine the parent term (under which
  82. the terms should be moved). If you want to move terms to the root level, leave this field empty.
  83. This autocomplete form allows you to either choose a parent term from the list of exisitng terms
  84. or to insert a new terms, which will be used as parent (this parent term will be added to the root
  85. level).
  86. In multiple hierarchical vocabularies, it's possible to move terms to more parents in one step by
  87. inserting more terms into the autocomplete field and separating them by commas. Additional, there
  88. appears an option ('Keep old parents and add new one'), which prevents the replacing of old parents.
  89. - Merging
  90. With the merging action, you can put terms with the same meaning together (e.g. your vocabulary
  91. contains: SoC, Summer of Code, GSoC, Google Summer of Code). All terms, that get merged into
  92. one other, get synonyms of resulting term (here called merged or main term). Additional
  93. all term-node association gets automatically updated (this means nodes, that had a merging term
  94. assigned, now get the resulting merged term instead). All merging terms are deleted afterwards.
  95. In the Taxonomy Manager, you can do that by selecting all terms you want to merge and to click
  96. the 'Merge' button. A fieldset with an autocomplete field an some options expands. In the
  97. autocomplete field you have to specify the resulting merged term (into which the selected get merged).
  98. The merged term can be either chosen from the list of existing terms or can be inserted automatically
  99. and used as merged term.
  100. Additional, there are some options available (they depend on the vocabulary settings). If you want
  101. to add any kind of relations (parents, children, related terms) from the merging terms to the
  102. resulting merged term, select one (or more) of them.
  103. The default taxonomy term page, which shows all assigned nodes, is overriden by the Taxonomy
  104. Manager, so that former merged terms can be considered (if someone calls a term, that was merged,
  105. it redirects to the resulting merged term).
  106. NOTE: At the moment, the Taxonomy Manager only cares about the term-node association inserted
  107. into the term_node table (by the taxonomy module). If you are using any CCK modules, like
  108. CCK Taxonomy or Content Taxonomy, which (can) save the term - node association in cck tables,
  109. don't use the Merging action, because changes are not handled.
  110. If you are using Views filters instead of the default taxonomy term page, merged terms are
  111. either respected.
  112. If you want to customize this by yourself or have some other module, you can use following
  113. function taxonomy_manager_merge_get_main_term($tid) for getting the main term id (if there
  114. is any main term, else return 0). The term merge history gets saved in the
  115. taxonomy_manager_merge table (main_tid, merged_tid) and gets additional cached, so that
  116. checking for a merged terms causes nearly no performance loss.
  117. - Editing term data
  118. If you want to edit or read some term properties, click on the term. A fieldset on the right side
  119. of the tree view gets loaded. This contains all term related information and can be edited. If you
  120. want to change the term name or the description, fill in any changes you want and click the saving
  121. symbol. All saving is done through AJAX, so no reload is necessary.
  122. Additional, this page contains listing of synonyms, related terms and parents (depends on your
  123. vocabulary settings).
  124. Every listed entry has an delete operation. By clicking the delete symbol, the relation gets deleted.
  125. In case of synonyms, the names get deleted from the database. If you are deleting a related term or a
  126. parent, this doesn't delete the term itself, only the relation.
  127. For adding new synonyms, the listing has a textfield below. Insert there any new synonym and click the
  128. plus symbol.
  129. For adding a new related term or a new parent (if multi hierarchy), there is a autocomplete field below
  130. the listing. Use this to insert new terms or to choose existing ones and assign them to the current term.
  131. - Using the search
  132. At the top of the page, there is a collapsed fieldset, called 'Search'. This search allows you to
  133. directly select an existing term for editing. Else, if your input doesn't match an existing term,
  134. the value will be used for filtering root level terms (this doesn't affect any child term).
  135. AUTHOR
  136. ------
  137. Matthias Hutterer
  138. User: mh86@drupal.org
  139. Email: m_hutterer@hotmail.com