一个术语可以有多个来自不同词汇表的父项吗？
Drupal 分类法中可能吗？ 我有很多与消费产品相关的页面都在以下词汇中：
- 电子产品
- 洗衣机
- 电视
- 移动
- 汽车
- 电气
...各种
现在索尼电视都将出现在电视中，也出现在电子< /强>。 是否可以在分类学中做到这一点，即从属于不同词汇表的多个父母继承。
Is it possible in Drupal Taxonomy?
I've many pages related to consumer products to be in following vocabularies:
- Electronics
- Washing maching
- TV
- Mobile
- Cars
- Electrical
... all sorts of
Now Sony TV would go in TV and also in Electronics.
Is it possible to do it in Taxonomy ie to inherit from multiple parents which belong to different vocabularies.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
Drupal 6 允许设置多个术语父项。
向术语添加多个父项将导致 segemntacaoTeste 词汇表在每个术语上查找多个父项。由于使用拖放轮廓界面时不支持多个父级，因此如果启用此选项，拖放将被禁用。如果您选择有多个父母，您将只能使用术语编辑表单来设置父母。
您可以随时重新启用拖放界面，方法是将该词汇表中的术语的多个父项减少为单个父项。
Drupal 6 permits to set multiple term parents.
Adding multiple parents to a term will cause the segemntacaoTeste vocabulary to look for multiple parents on every term. Because multiple parents are not supported when using the drag and drop outline interface, drag and drop will be disabled if you enable this option. If you choose to have multiple parents, you will only be able to set parents by using the term edit form.
You may re-enable the drag and drop interface at any time by reducing multiple parents to a single parent for the terms in this vocabulary.
与每个术语有多个父项相比，最好使用其他字段（例如外部 Id 或 rtid）来引用不同的词汇表。
it is better to use other fields, e.g external Id, or rtid for referring to different vocabularies as compared to having multiple parents per term.
Drupal 分类系统的创建并不是为了包含相互重叠的术语。这会打乱术语使用的层次顺序。
在您的示例中，电视应该是电气的子级，因为所有电视都是电气的。
The drupal taxonomy system is not created to have terms that overlap each other. That would mess up the hierarchal order that terms are used for.
In your example, TV should be a child of Electrical, since all TV's are electrical.
我很确定，这个问题的作者已经找到了他的答案，但如果其他人仍在寻找这样的解决方案，这似乎是一个好的开始。
http://drupal.org/project/term_relations
我不确定这个解决方案对于 D7 有多成熟，但是如果我们想避免创建自定义模块，这应该是最好的开始。
I'm pretty sure, that author of this issue has found his answer, but in case if someone else still looking for such solution, this seems to be good start.
http://drupal.org/project/term_relations
I'm not sure how mature this solution is for D7, but if we want to avoid custom module creation, this should be best start.