A tag does not save the way you typed it. Every tag is re-capitalised on the way into UNI, so autocad and AutoCAD both come back as Autocad. That is the rule working rather than a fault, and it applies everywhere tags are used: publications, journals, skills, profile fields and team-member positions. Projects have no tag field alike.
The rule
- Every word gets one capital letter, at the front. The rest of that word is lowercased.
- Capitals inside a word are lost. AutoCAD becomes Autocad, iPhone becomes Iphone, openBIM becomes Openbim. There is no way to keep them.
- A capital follows every hyphen and apostrophe too, because the rule reads those as word breaks. So e-commerce becomes E-Commerce, o'brien becomes O'Brien, and 3d becomes 3D.
- Runs of spaces collapse to one.
Twenty-nine acronyms are kept in capitals
One list survives the rule, whether it is the whole tag or a single word inside a longer one:
CEO, CFO, CTO, COO, CMO, CIO, CPO, VP, SVP, EVP, HR, IT, UI, UX, AI, ML, API, SEO, SEM, PR, R&D, QA, BA, PM, PO, GM, MD, PA and EA.
So ai research saves as AI Research. Anything not on that list is treated as an ordinary word, which is why BIM, CAD, GIS and HVAC come back carrying a single capital.
Thirty characters, and a long tag is refused rather than shortened
A tag name holds 30 characters, spaces included. A longer one is not trimmed to fit: the save fails and the tag is not added at all. If a tag will not save and everything else looks right, count the characters. Two shorter tags will do the work of one long one, and they will each be found by more people.
Tags are shared, so yours joins one that already exists
A tag is a single object used across UNI, not a private label on your own work. Typing one that already exists attaches your work to that tag and adds one to its count. That is the whole reason capitalisation is enforced: without it the same word would sit under several spellings and none of them would gather anything.
You may occasionally meet two tags that look identical. Where that happens they were created under different capitalisation before being normalised, and choosing either one is fine.
Disciplines do not work this way
Disciplines come from a fixed catalogue UNI maintains, so they are never re-spelled and you cannot invent one. Tags are the free-text field; disciplines are the filing. See How many disciplines a project can carry.