Index Data
(Available for Content, Agentstore, DIH, and Proxy components.)
In the Index tab, you can use the wizard to index data. This is equivalent to sending the DREADD
or DREADDDATA
actions. For information about these actions, see the Content Component Help.
To index data
-
On the Choose Data page, click an option to specify the data to index:
- Text. Copy and paste the data directly into the text box. The data must be in either IDX or XML format. For more information about the IDX format, see the Knowledge Discovery Administration Guide.
- UTF-8 encoded local files. Click Choose files to browse and select IDX or XML files on your local disk.
-
Files on server. Type the file names of IDX or XML files that are accessible to the server through the file system. To add more than one file, click + to add a new row. Click - to delete a row if you no longer need it.
NOTE: If you add multiple files, Knowledge Discovery Admin submits each file as a separate index command. All the other settings that you specify are the same for each file.
- Click Next. The Choose Database page opens.
- Choose the database that you want to index your data to. By default, Knowledge Discovery Admin reads the destination database from the document, but you can click Select the database from the list, then click the arrow and choose the database that you want to index your data to from the list.
- Click Next. The Kill Duplicates page opens.
-
(Optional) Specify how to process duplicate documents.
-
Specify how to identify duplicate documents:
Default Uses the option specified for KillDuplicates
in the[Server]
section of the Content component configuration file.None Allows duplicate documents in the data index and does not replace or delete the documents. Reference If the document being indexed has the same DREREFERENCE
field value as a document that already exists in the index, Content deletes the existing document and replaces it with the new document.% match If the content of the document being indexed is more than N
percent similar to the content of a document that already exists in the index, Content deletes the existing document and replaces it with the new document.Field Names If the document being indexed contains a FieldName
Reference field with the same value as theFieldName
Reference field in a document that already exists, the Content component deletes the existing document and replaces it with the new document. -
Specify how to treat duplicate documents.
Keep existing documents, instead of new ones, in case of conflict If you selected Reference or Field Names for Where to look for duplicates, selecting this option discards the duplicate document and keeps the matching document that the data index already contains. Move to the database listed in this field: [enter database field] Specifies the name of a field in duplicate documents that contains the name of the database to move duplicate documents to. Or move to this database: [select database] Move the duplicate to the specified database.
-
- Click Next.
-
Click Next. The Summary page opens, displaying the action that will be sent to the server. The action is automatically constructed as you complete the wizard. It is shown for reference only; you cannot edit the action directly.
- Select the priority for indexing, which determines how the action is queued, then click Index to send the action and index the data. After the data is sent, you can click Sync to manually flush the index cache to disk, which makes the data searchable.
If you need to edit any of your settings, you can click Previous to move back through the pages of the wizard, or click Reset to clear all settings and start again from the beginning.