The iKnow technology does not have a default user interface. This chapter describes a few sample user interfaces provided with iKnow. These can provide a convenient starting point when developing a query interface specific to your use of iKnow.
How to Display iKnow User Interfaces
from the Caché Cube, access Studio.
from the File drop-down menu, select Change Namespace. Select the %SYS namespace. Click OK.
from the File drop-down menu, select Open.
from the Open window, make sure that Include System Items is checked. Then select %iKnow->UI->and the desired user interface. Click Open. The source code for the user interface appears in the Class Editor (the main Studio window).
click the View Web Page icon (the planet Earth icon). The user interface displays in your default browser. (Note that abstract classes cannot be displayed.)
This is the superclass for all other portals and pages in the %iKnow.UI
package. It groups a lot of reusable materials such as handling of domain ID, the "selected" source ID, metadata filters and paging for iKnow query-driven tables and groups. It is abstract, and cannot be run by itself, but should not impose restrictions on subclasses or component names, as long as the corresponding panes (optDomainPane, txtTermPane, optSourcePane and filterPane) are used.
The Loading Wizard, which provides a source file management interface.
The query portal interfaces, which provide different displays of source data, showing iKnow indexing and dictionary matching.
A management and maintenance interface that allows a user to easily choose (or manage) Domain and Configuration objects and then load files from a filesystem directly into a domain using %iKnow.Source.File.Lister
. It also provides functionality to load metadata values from a CSV (comma-separated values) file with rows corresponding to files previously loaded through the File Lister. This operation automatically creates previously nonexistent metadata fields on the fly.
This is a sample Zen page query display interface with broad application. It shows a wealth of information about the various language elements identified by iKnow, including entities, CRCs, CCs and paths, providing a contextual at-a-glance view of what's in your data. The generic filters option allows for easily selecting subsets of a domain based on metadata criteria and the summary option provides quick access to the contents of the sources themselves. This interface provides a sample of how iKnow Smart Indexing can be used to quickly overview and navigate a large set of documents.
The Knowledge Portal offers straightforward examples of calling the different iKnow Query APIs from Zen, including top entities, similar entities, and related entities, with the frequency and spread for each.
This sample Zen page query display interface is a simplified version of the Knowledge Portal. It displays entities and sources only. It does not display CRCs, CCs and paths. It provides filtering and summary capabilities, but by default it shows the full text of the source.
This sample Zen page query display interface looks at the Smart Indexing results for a single document to verify the correctness of the analysis done by the iKnow analysis engine. It shows how iKnow cuts up each sentence into a sequence of concepts (bold and highlighted), relations (underlined), and non-relevants (italic). The page also shows a frequency-sorted list of detected Concepts and CRCs. This page provides an option for loading input manually. This page offers an example of how %iKnow.Queries.SentenceAPI.GetParts()
can be used for custom highlighting.
This sample Zen page query display interface gives for each document an overview of the different matching results in the document. It allows for easy browsing through match results against a dictionary and allows you to display the details of each individual match. It uses %iKnow.Matching.MatchingAPI.GetHighlightedSentences()
to display the text with dictionary matches highlighted in color, and %iKnow.Matching.MatchingAPI.GetMatchElements()
to display the details of a specific match including the dictionary name, its item and term, the match score, type of match and the entity matched. This interface provides a sample of how iKnow Smart Matching can be used to combine predefined information with Smart Indexing results.