Taxonomy is a great thing. However I found out that it is rather static implemented in drupal. I started with a main list and taxonomy terms under each topics but after some time I found out I would like to reschedule the terms under another topics. So what I want is
- Dairy
- Milk
- Drink
- Alchohol
- Beer
- Wine
- Alchohol
now I found out that I would like to have a complete topic about wine, since I want to use that for another type of service (forum, gallery, etc) and to expand it further to wine from 1991, 1992, etc.. or I want to move milk
I quess the only way to migrate the content with taxonomy associated to is, is by diving into the database and use some magic sql statements?
It would be nice if drupal had an interface where I can select terms and topics on the left and move them to a new term/topics on the right
I hope this makes sense, otherwise, feel free to ask what I want.
Comments
Comment #1
(not verified) commenteda good fis step for this would be to make one or two html or image mockups which demonstrate the user interface . i would think tha the adin -> content page would be a good starting point.
Comment #2
jonbob commentedYou can freely change the parent of any term with the existing interface.
Comment #3
(not verified) commentedComment #4
(not verified) commentedYou can only change the parent of a term from within a vocabulary.
You cannont move a term from one vocabulary to another.
Comment #5
dkruglyak commentedThis feature is needed
Comment #6
venkat-rk commentedAbsolutely. Even two versions of drupal after this issue was introduced, the taxonomy module remains pretty static. I can't imagine the number of times I have moved terms around within a vocab and across vocabs and it is a nightmare, especially when you have lots of terms.
Taxonomy is a difficult concept to grasp, so having the ability to move terms around dynamically would be a great usability feature.
Comment #7
bertboerland commentedkeeping this one open, seems still a good feature for core!
Comment #8
jo1ene commented+1 for this feature
I manage a ever growing website and I regularly find the need to reorganize, combine, split, etc. taxonomies and terms - to accomodate a new module, for example. I don't think this feature needs an interface. There is already a selection for parent in the edit term form. This selection could be made to include other taxonomies in the same way that the book module's parent selection includes other books or motf's selection includes all menus (excepting the one's you exclude, of course).
On the other hand, such a comprehensive selection tool would likely become unwieldy with large vocabularies. But it would be worth it to me. Could this be accomplished at the module level - allowing those that have a pressing need to have it available, while not cluttering the parent selection for other folks?
Comment #9
gerhard killesreiter commentedif the taxonomy forms have been properly apified (this needs checking) then it might be possible to move a term elsewwhere by adding an form to the "edit" field. this coul dbe done in a contrib module.
Comment #10
brevity commented+1
vocabularies grow over time, so splitting would come in handy ...
first thought one only needs to change the parent of the root of the sub-tree to move (in term_hierarchy), but all terms in the sub-tree have vids specified in term_data that need to be changed, too.
Comment #11
killes@www.drop.org commentednew features go into devel version.
Comment #12
coreb commented(Moving x.y.z version to a real version number) Feature Request => 6.x-dev
Comment #13
venkat-rk commentedPl. ignore if I have misunderstood this issue
----
In case this helps anyone, there is/used-to-be a contrib module called taxonomy_switch that let you move terms from one vocab to another. It worked pretty smoothly when one term was moved to another vocab but when I tried moving a number of terms, they disappeared from the vocab and I couldn't find them on the admin page (although I suspect they were still in the taxonomy table) to move them back.
The category module has a bulk_edit contrib module that does this. It is occasionally buggy but works and might be a useful place to look for ideas if anyone is interested.
Comment #14
bertboerland commentedramdak, you are right, this issue can be closed, see http://drupal.org/project/taxonomy_switch
Comment #15
venkat-rk commentedThanks, bert.
Comment #16
(not verified) commentedComment #17
ionuts71 commentedThere is any solution for Drupal 6? Taxonomy switch module works only for Drupal 4.7 and is only a dev release for 5.x.
Comment #18
mikeker commentedAny movement on this one? As ionuts points out, the workaround module hasn't had any updates since Nov 2007. Seem to me this should be part of the core Taxonomy module...
Thanks.
Comment #19
mokko commentedmodule taxonomy manager can do something similar, but not this.
Comment #20
johnflower commented+1
This feature would save me time.
Comment #21
iernst commented+1
This feature is really needed.
Comment #22
webwriter commentedSubscribing. To a 6 year old thread... wow.
Comment #23
mcurry commentedSubscribing
Comment #24
mcurry commentedDoes anyone know how one would use the Drupal core APIs to perform the desired operations (in 5.x, 6.x, and 7.x), or would this need to be done using raw SQL queries (I'd like to avoid performing raw SQL queries if possible.)
I'm asking this question because I'm hoping the core API has the functionality we need; this kind of plumbing should not be left to module developers.
Ideally, there'd be a core API taxonomy_move_term(...) that would manage the low-level details and shield module developers from the complexity of the database structures, and help prevent damage to the database by contributed module bugs.
Comment #25
heather commented@grateful_drupal_user - i recommend you join the #drupal channel on IRC and ask this question. good luck in your quest!
Comment #26
konstak commentedIt`s still needed...
Comment #27
u210ks commentedYou'll find useful info here: http://drupal.org/node/382944 and here http://drupal.org/project/taxonomy_manager
Comment #28
tim.plunkettThis is won't fix for D6 or D7, if you'd like to see taxonomy_manager added to core, open a feature request against D8.
Comment #29
drupalnesia commentedJust experience this issue, first I move it by SQL manually but since my client need to move very much terms so I create this module:
- https://www.drupal.org/project/term_manager
Current features:
I see another module support Merge Term, but its create new Term even the Target Term same as one of Source Term. This module try to use existing term, not create new term.
Comment #30
gábor hojtsyUpdating title, tags and version number based on recent announcement at https://www.drupal.org/about/core/blog/new-drupal-core-branching-scheme-...
Comment #31
dqdWould like to ask around if there is still enough interest to keep this open as future FR for core. So I opened it temporary just in case. If not feel free to close it again.
Fixed title regarding the comments and the actually wish behind this and to make the intention clear regarding "moving vs replacing".
Comment #32
claudia sotto commentedThis is still a problem in Drupal 10. There was this module "Taxonomy manager", that was solving this problem in Drupal 7, but the version for Drupal 8 and ahead don't have this feature anymore.
Comment #33
dqdfrom #32, what makes
from #28 obsolete as solution.
So we need to find a new approach. I think moving terms is an interesting feature for bigger existing projects and there seem to be no way ou tyet for this.
Comment #34
quietone commentedComment #36
catchVocabularies are bundles now, which makes this even more complicated than it used to be because there are also fields to worry about.
https://www.drupal.org/project/convert_bundles in contrib might be an option.
Because of the bundles/fields issue, I can't see us ever doing this in core, moving to 'needs more info' but I think it should probably be closed as 'by design'.