S6.2 Symbol fields and metadata filled out as required
-
Reference field is selected appropriately for the symbol and is visible
-
Value field contains the name of the symbol and is visible
-
Footprint field contains footprint link for fully specified symbols and must be invisible
-
The footprint field must be empty for generic symbols
-
-
Datasheet entry is filled out, and is invisible
-
For generic symbols, the datasheet field should be a tilde (
~)
-
-
KLC Exception properties are allowed start with "KLC_" and are allowed, but they should only be added after a discussion with a librarian.
-
The symbol contains no other custom fields
Additional documentation is provided via two other fields:
-
Description field contains comma-separated device information
-
For symbols with a default footprint, the simplified footprint name should be appended to the description e.g.
SOIC-8 -
Part name should not be duplicated in the description field
-
-
Keywords field contains space-separated keyword values. These values are used to assist in part searching and should be selected to assist end-users in finding suitable parts
-
Keywords should contain typical aliases for words, Example: Description contains
Operational amplifier⇒ keywords should containopamp. -
Keywords should not include filler words. Example
positive negativeinstead ofpositive and negative -
Any single word which already appears in the description field, should not be included in the keywords field. Example: Description =
50mA Low-Dropout voltage regulator, QFN-16⇒ Keywords could includeLDObut notregulatororQFN -
In case phrases (multiple words which belong together) are used in the keywords, the must not be separated by spaces, but by a dash. Example:
voltage-regulatorinstead ofvoltage regulator -
Words which are prefixes of other words from either the Keywords or Description field should not appear in the keywords. Example: Description =
FPGA with Brown-Out detection, QFN-16⇒ Keywords could includebrownoutbut notbrown
-