Feature Request

Current Behavior: The Glossary alphabet index works correctly for English in the site glossary page, where terms are listed and grouped under their corresponding English alphabets. However, for non-English languages such as Japanese and Chinese, glossary terms are not grouped under their corresponding native language characters. Instead, all terms fall under the "#" section , making it extremely difficult to navigate and use the Glossary effectively. Expected Behavior: When the knowledge base language is set to a non-English language, the Glossary alphabet index should display the native characters of that specific language so that glossary terms are correctly grouped and listed under their corresponding characters, consistent with how English terms are handled. This should be supported across all non-Latin languages including but not limited to: Japanese - Hiragana / Katakana Chinese - Simplified / Traditional characters Arabic - Arabic script Korean - Hangul

In English, we have a term 'Widget'. However, when we go and try and import the value into French, the term is still 'Widget' but we want to be able to import the translated value. Our company uses our own translation service outside of Doc360; therefore, the workaround of having Doc360 do the translations AND have the value show as 'English' in the French glossary page in the Portal is very confusing and misleading.

It would be great if we could provide an option to edit the glossary name after it's creation. Currently, we are not providing the ability for the users to edit the glossary name.

We need the ability to add categories of Glossary terms, so one word can have multiple glossary definitions depending on the subject.

Currently in the AI Glossary recommendation, the glossary terms are auto-capitalized on insertion, which affects grammar and readability. It will be better if the glossary term stays in its original format (not automatically capitalized).

In the example, we have a glossary entry for the abbreviation "LE". This results in all instances of the letters "le" (which are a lot in German) to be recommended for the glossary term. This behavior needs to be improved, either by recommending glossary terms only when they appear in isolation or by introducing settings that the user can make.

When you enter a search term in Eddy, it refers to the article where the term appears, but does not list the definition. Because glossary term definitions are extremely valuable sources of information (explaining important concepts), they should be AI-searchable.

I would like to customize the word shown for the glossary term "metric". In this sentence, it must say "metrics" to make grammatical sense, but because the term in the glossary is "Metric" it is displayed as such.

Have the ability to define a definition in each languages for a same glossary entry. This is most valid for acronyms that are standards in an industry.

Our subject-matter glossary entries need to go through SME review before they are published. This requires kind of a mini-workflow like for articles (including a Publish step). Alternatively, I could imagine that labels or - in this case - simply a "Needs Review" flag would work as well. In any case, it should be possible to create a glossary entry without automatically publishing it right away.