Feature request: Allow Acronym alongside element name and alias

[Ron Beernink]

I propose that element properties include a new "Acronym" property in addition to the existing "Name" and "Alias" properties, and that a general search includes this data.

An example of how this helps to model and search on an application component object

• A finance platform can have a Name of "Financial Information Management System"
• The Alias can be the name that users commonly refer to it, e.g. Oracle Financials
• The Acronym would be FMIS

[li]A search should return this object if either "Financial", "Oracle" or "FMIS" is entered as the general search value.
[/li][/list]

[qwerty]

There's a thing called Glossary where one could put these in. If you start with this the next would want to have a translation in Kisuaheli and ancient Greek too.

q.

[Sunshine]

I propose that element properties include a new "Acronym" property in addition to the existing "Name" and "Alias" properties, and that a general search includes this data.
An example of how this helps to model and search on an application component object
A finance platform can have a Name of "Financial Information Management System"
The Alias can be the name that users commonly refer to it, e.g. Oracle Financials
The Acronym would be FMIS

Have you considered using keyword field or a tagged value for one of those?
We use
Name: Financial Information Management System
Alias: FMIS
TaggedValue "COTS Name": Oracle Financials

A search should return this object if either "Financial", "Oracle" or "FMIS" is entered as the general search value.

You can create a custom search and save it to operate like that

[Ron Beernink]

Apologies about the belated response.   I like the suggestion to use a tag value to handle an application acronym.  And yes, useful to also handle acronyms in the glossary.

Thanks people

[Paolo F Cantoni]

Apologies about the belated response.   I like the suggestion to use a tag value to handle an application acronym.  And yes, useful to also handle acronyms in the glossary.

Thanks, people

Why stop at one more "name".  We allow up to half-a-dozen names (as properties - tags).  We are standardising our shapescripts (since we use out own MDG) to allow the selection of the appropriate name for the item (on a per-diagram basis) using User Specified Diagram Properties.

"A rose by any other name would smell as sweet"...

Paolo