Add in a synonyms feature

Resurfacing this feature request for v3 if possible. Very similar need (see screenshot), except I'm using glossify_taxonomy instead of node:

- Have a term such as President of the United States
- Create field_acronym plain text field for same taxonomy, then enter POTUS into that field
- Glossify would treat either the name or field_synonym equally, applying to whichever appears first on a page

Great module! We're using it with the book module as a glossary of terms, which display as pop-ups on hover.

Hello, I am sharing a patch I refactored for my colleague @yospyn.

As mentioned @yospyn we have synonyms in a term field which need to be called 'field_synonym' (Just add this field and your synonyms to use the patch).

Thanks to @JakeAPoe for the patch I used it for this version 3 patch.

I'd like this very much. I think it should allow to select a certain field with a list of synonyms from the source entity.

Please use MRs instead of patches!

Raising the priority and hope someone finds the time for the implementation!

joao.ramos.costa → made their first commit to this issue’s fork.

prudloff → changed the visibility of the branch 3269949-synonyms to hidden.

We might need a wider entity type support: in the project I would have the use of synonyms, the glossary definitions are nodes.

Second that.
There might be glossary terms/explanations that are more complex than what just a taxonomy term allows for.

Hi @phily,
In fact, in the project where I apply the patch from this MR, we're using synonyms module, but only because synonyms field matches the one used here.

I think you're right — and when I have some time, I’ll take a look. I know that using the service provided by the module won’t work, since we’re grouping the synonyms differently, but maybe it’s possible to make the query a bit more complex, not sure. Need a proper analysis .

Thank you

I still think this would be a really helpful feature, also for a different case: If an entity (for some good reasons) has a different title, than it should represent as glossary term.

Typically you'd see synonyms as a list of additional terms, but it might also be just one "Glossary" synonym that represents the entity in texts, for (stupid) example: "Imprint". Maybe the Imprint needs to be named "Our imprint", but should appear linked on "Imprint" everywhere... So even if it's only a single term on certain nodes and not a lst, this would be great. I'd then call it "alias"

We were in need of such a feature for a few customers, so I took the time to finish this. It works similar to the approach by @joao.ramos.costa, I appreciate the work and urge to give him credit, once this is reviewed and merged.

You basically have to create a Text (plain, long) field called "field_glossify_synonyms" on the bundle you wish to enable synonyms on. Then when you create a bundle, for example "Technology" you can define "Tech" and "IT" as their synonyms in the "field_glossify_synonyms" text field.

Now when you type either Technology, Tech or IT, all of these terms will be glossified and link to the main node (if link is enabled).

We can improve on this in the feature through adding support for "Synonyms" in the future. I haven't used the module yet, and I am unsure whether it would add much overhead.

grevil → closed merge request !40

grevil → changed the visibility of the branch 3.x to hidden.