...
The first step in testing our KEE project is to compile our lookup database for the entities using the KEE command line tool. This is accomplished by running the following command (with the present working directory set to the folder for our KEE project):
| Code Block |
|---|
>> squirro_kee compile |
After running this command, a db/ folder will be created within our KEE project, this folder includes the lookup database (lookup.json) used to identify known entities. If we take a look at this file, we will see a lookup entry for each of the entities within the csv file, as well as the details for each entity within the csv file. For example:
...
Fixtures are created using this method by running the kee get_fixture command:
| Code Block |
|---|
>> squirro_kee get_fixture 'pRVNr9H7QJG_UXhwHjQH3A' '2aEdt4H0R7uwVfbScYadpA' |
...
Once we have a fixture created, we can use the kee command line tool to test the KEE extraction on the fixture. To test a KEE project using the set of fixtures within that KEE project folder, we run the command:
| Code Block | ||
|---|---|---|
| ||
>> squirro_kee -v test |
This will produce a basic summary output that shows which tags (keywords) were added to each fixture by the KEE. For our example KEE project, running this command produces:
| Code Block |
|---|
>> squirro_kee -v test
- Running fixture demo
- 4 (100%) correct results:
[u'Adrian Fox', u'District Manager', u'District Representative', u'Jane Doe']
- 0 ( 0%) missed results: []
- 0 ( 0%) extra results: []
- Processed 1 fixtures
- 4 (100%) correct results
- 0 ( 0%) missed results
- 0 ( 0%) extra results |
...
To upload a KEE project to a Squirro server, the kee upload command is used.
| Code Block |
|---|
>> squirro_kee upload |
After the KEE project is uploaded to a Squirro server, the KEE will be available as an enrichment under the Enrich tab of the Squirro frontend. Each uploaded KEE project requires a unique name which can be customized within the kee section of the config.json file, as shown below.
...