Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Service Manager9.51

Use > Knowledge Management > Knowledge Management administration > Knowledge Management migration > Document import considerations for attachments

Document import considerations for attachments

Before importing documents into HPE Service Manager, consider the following regarding attachments.

All attachments should be in an attachments folder under the XML source directory.
Shared Content attachments should have the file name prefixed with "shared_" followed by a unique string used as the legacyid for attachments followed by an underscore and the file name.
shared_<legacyId>_<filename>
Example:
shared_1234567890_Logo.jpg.
Attachment links (shared or owned) in the source XML should have the format href=/answers/attachments/1234567890 where 1234567890 is the legacyid of the attachment. Embedded attachments should use src= instead of href=.
Document owned attachments (that is, documents not shared) should have the file name prefixed with a unique string used as the legacyid for attachments followed by an underscore and the file name.
<legacyId>_<filename>
Example:
1234567890_Logo.jpg