You can use the wildcard characters that are listed in this table in any of your search terms.
| Search terms | Description | Example |
|---|---|---|
| Type a single term with no special decorations | Returns all asset with the single word listed in the metadata | Type Claims. |
| "term1 term2" | Bracket two related terms with quotation marks. Returns all assets with the exact phrases in the metadata. | Type "process model" to group these like terms together. |
| " ? " | Represents a single wildcard. character. Returns
all assets with alternative spellings. Note: You cannot use a question
mark as the first character in a search.
|
Type B?lls to return terms like bells or balls. |
| " * " | Represents a multiple character wildcard. Use
asterisks to retrieve alternate variations of terms. Note: You can
use the asterisk in place of the first or last letter of the search
term. You cannot use "*.*" as a search query.
|
Type long* to return terms like long, longer, or longest. |
| " ~" | Use a tilde at the end of a single word to search
assets with close spelling variations. Note: To make this search more
powerful, include a numeric indicator between 0 and 1. The higher
number returns the matches that are closest to the original search
term. Example: boat~0.9 returns coat
|
Type throat~ to return terms like boat, float, or coat. |
| AND | Use this Boolean operator in all uppercase letters in your search queries. The default Boolean operator is always AND. | Type "processing model" AND claims to return terms with the related terms "process model" and also claims. |
You can use one or more search fields in any combination, or choose the last modified date to narrow the focus of your search.
| Field labels | Description | Example | Query syntax |
|---|---|---|---|
| All of the words | Type a string of terms to search on in any order. | service credit implementation | "service credit implementation" |
| With the exact phrase | Type a string of related terms to search in the exact order. | service implementation | "service implementation" |
| At least one of the words | Type a group of terms, from which only one needs to match any of the words in the asset metadata . | service design model | service OR design OR model |
| None of the words | Type terms that you know are not included anywhere in the asset metadata. | claims | -claims Note: If you search with NOT or
"-" without any other search terms, no results are returned.
|
| ID | Type the alpha and numeric string that is in the unique ID of the asset. | {0000-1111-2222-3333} | (\{0000\-1111\-2222\-3333\}) |
| Name | Type a term that is part of the asset name. | Claims | name:(Claims) |
| Description | Type a term or phrase that is in the asset description. | audit records human resource | description:(audit records human resource) |
| Owners | Type the name of the asset owner. Note: There
can be more than one owner of the asset.
|
John Smith | owner:(John Smith) |
| Last Modified by | Type the name of the user who last modified the asset. | Anna Baker | lastModifiedBy:(Anna Baker) |
| Last modified | Choose a range of dates in the date chooser. | June 13, 2007 - June 15, 2007 | lastModified:([20070613 TO 20070615]) |
The search index in Rational® Asset Manager relies on punctuation to break document content into meaningful information chunks for search. In other words, it tokenizes the information by not recognizing blank characters and excluding characters within a string constant or delimited identifier. When a document is stored in the Rational Asset Manager index, punctuation such as periods and other terms that need punctuation such as "http://" are not stored in the index.
When you search for assets by using a wildcard, use these rules and examples to help you successfully find assets.
However, when you use the wildcard character "*" in a search term, your text is no longer tokenized. When this occurs you are not able to find the assets that you are looking for. You must manually tokenize your terms in the search field. Use these examples as a reference to creating effective search terms by using wildcard characters.
Scenario: The document contains the line: type="impl:AssetDiscussionForum".
Use this search term with the "*" wildcard character:
Scenario: Host names are stored as a single token but are not stored with the "http://" portion of the name. Using regular search terms makes it easy to find host names. However, if you include a "*" wildcard character in the search, then it is possible that you might not find the correct file. The document in this example contains the line: wsdl:definitions targetNamespace="http://core.ws.web.repository.ram.ibm.com".
Use these search terms with the "*" wildcard character:.
If assets contain XML artifacts, such as WSDL files, and if XML indexing rules have been set up for the asset type, then you can find assets based on the elements, attributes, and values of an XML artifact.
attribute:(element[attribute='value' attribute='value'])where element, attribute, and value are the specific names of an element, attributes, and attribute values from the XML file. Wildcards are permitted.
attribute:(schema[targetNamespace='http://core.ws.web.repository.ram.ibm.com']) attribute:(targetNamespace='http://core.ws.web.repository.ram.ibm.com') attribute:(schema[targetNamespace='*ws.web*']) attribute:(targetNamespace='*'])
attribute:(element[name='value'])
attribute:(path[name='value'])
attribute:(name='value')
attribute:(name='value' name2='value2') attribute:(element[name='value' name=value2'])
attribute:(text()='Operational') attribute:(status[text()='Operational'])The same path and element rules apply.