...
the term appears in the document
a sourced definition is valid
a definition’s online source is publicly available
the definition applies to the term based on the context of its use in a document
the definition is grammatically correct
the definition is concise
the definition does not include inaccurate or unnecessary information
any formatting issues are present that need correction
the term is designated properly (i.e. noun, organizational task, asset, etc.)
sub-tasks (other forms, hierarchy, synonyms) are completed correctly
There are a series of term-entry rules that should be used as a starting point. By following the Ten Commandments of Term Entry, your term will likely be approved.
Specific reasons that a term task may be returned:
The term is not entered in American or U.S. style English (i.e. honor vs honour)
The term is not entered in singular form (i.e. technology vs technologies)
The standard term is entered as an acronym or in shorthand (i.e. virtual local area network identifier vs VLAN ID)
Note: Official product names released by the manufacturer are an exception to this rule.
The offered definition does not apply based on the context of the citation (i.e. defining a service as something of value offered when the term contextually refers to a system application)
The definition is not designated correctly (i.e. a software application is entered as a noun when it should be an asset)
The source is not publicly available (i.e. a definition that comes from a website behind a paywall we must assume that not all users are members and thus likely cannot access the source)
The source is not authoritative (i.e. do not use internet forums, Wikipedia, or general sales and marketing material as a source)
Other forms are missing/incorrect (Note: if a term has multiple designations you must add other forms for all of them or the definition with other forms missing will not appear as a selectable option in the tagging task)
The term hierarchy does not contain at least twenty (20) semantic relationships
...