Keyword Search
Use the Keyword option to search components in the Code Insight Data Library based on their names or character strings with in a component name. Enter the required character strings in the Keyword field to define your search input. This search input is accompanied and defined based on the Operator dropdown selection that allows for more refined search results.
Use the Keyword field in conjunction with the Operator dropdown selection as follows:
|
•
|
Contains (Any Term)—Enter one or more character strings found within a component name. |
|
•
|
Begins With—Enter one or more character strings that match the prefix of a component name. |
|
•
|
Exact Match—Enter the full component name exactly as it appears in the Code Insight Data Library. |
|
•
|
All Terms—Enter multiple strings found within a component name. Multiple strings must be separated with spaces (not commas), and they can appear in any order. |
For instance, to search components that contain both Tomcat and Apache, enter: Tomcat Apache in the Keyword field.
The search will filter the component names based on the specified string in the Keyword field and the selected Operator dropdown.
Note:The search is case-insensitive, so it filters to all such components, no matter the upper or lower case used in the strings in the Keyword field or in the actual component name.
In general, the name of a component is a unique identifier that can be based on the project, package, or gem name of the component or on another convention such as the component’s author or repository. For your reference, the following shows the common conventions used for component names in the various forges:
|
•
|
Apache— <PROJECT_NAME>, for example “apache-batik” |
|
•
|
Debian—<PACKAGE_NAME>, for example “0ad” |
|
•
|
GitLab—<AUTHOR/ORGANIZATION>-<REPOSITORY_NAME>, for example: |
|
•
|
“cryptsetup-cryptsetup” (as found in component URL: https://gitlab.com/cryptsetup/cryptsetup) |
|
•
|
“redhat-bison” (as found in component URL: https://gitlab.com/redhat/centos-stream/rpms/bison) |
|
•
|
NuGet Gallery— <PACKAGE_NAME>, for example “newtonsoft.json” |
|
•
|
Pypi—<PACKAGE_NAME>, for example “hash_ring” |
|
•
|
RubyGems— <GEM_NAME>, for example “x-editable-rails” |
|
•
|
Other— <PROJECT_NAME>, for example “openssl” |
To search for components by a keyword, do the following:
|
1.
|
On the Global Component & License Lookup > Components tab, select the Keyword option. |
|
2.
|
Select a required search defining criteria from the Operator dropdown list prior to specify your search input in the Keyword field, for more refined search results. |
|
3.
|
In the Keyword field, enter the required character strings, found in the name of the component(s) for which you are searching, based on the Operator dropdown selection. For more information, see the introductory content (just above) in this section. |
Note: If a component that you want to explore is not available with the keyword search, try the URL, forge, or component ID search. If you are still unable to locate the component, the component might not exist in the Code Insight Data Library nor be saved as a custom component.