You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes a repository may end up with two taxonomy terms representing the same thing that should be merged (e.g. two terms for the same individual).
Currently, one would have to manually edit all repository items using the depreciated term to use the favored term. There is a module available, term_merge, for merging terms but it doesn't work for Typed Relation fields, only the core entity reference fields.
This limitation comes from it's dependency term_reference_change. To add support we would have to override their services for identifying reference fields and (possibly) merging.
The text was updated successfully, but these errors were encountered:
Sometimes a repository may end up with two taxonomy terms representing the same thing that should be merged (e.g. two terms for the same individual).
Currently, one would have to manually edit all repository items using the depreciated term to use the favored term. There is a module available, term_merge, for merging terms but it doesn't work for Typed Relation fields, only the core entity reference fields.
This limitation comes from it's dependency term_reference_change. To add support we would have to override their services for identifying reference fields and (possibly) merging.
The text was updated successfully, but these errors were encountered: