ProgramaticLuceneQueryAccess - Revision history

Tredmond at 13:59, October 2, 2009

2009-10-02T13:59:35Z

2009-10-02T13:58:24Z

2009-10-02T13:57:53Z

2008-08-28T23:24:20Z

2008-05-27T23:03:42Z

2008-05-22T23:30:03Z

categorizing page

2008-01-02T21:50:07Z

2008-01-02T21:49:39Z

2008-01-02T21:45:37Z

2008-01-02T21:16:55Z

@@ Line 3: / Line 3: @@
 * make a phonetic query that uses the lucene indicies and
 * save the project to include the lucene query tab.
-I will assume that you have already obtained the binary or src (http://smi-protege/repos/protege/lucene-query/trunk) for the lucene query plugin.  The code for this example can be downloaded from [[media:TestLuceneQuery.zip]].
+I will assume that you have already obtained the binary or src (http://smi-protege/repos/protege/lucene-query/trunk) for the lucene query plugin.  The code for this example can be downloaded from [[media:TestLuceneQuery.zip|here]].
 The test code I used had the following structure:
 <code><pre>

@@ Line 4: / Line 4: @@
 * save the project to include the lucene query tab.
 I will assume that you have already obtained the binary or src (http://smi-protege/repos/protege/lucene-query/trunk) for the lucene query plugin.  The code for this example can be downloaded from [[media:TestLuceneQuery.zip]].
 The test code I used had the following structure:
 <code><pre>

@@ Line 3: / Line 3: @@
 * make a phonetic query that uses the lucene indicies and
 * save the project to include the lucene query tab.
-I will assume that you have already obtained the binary or src (http://smi-protege/repos/protege/lucene-query/trunk) for the lucene query plugin.
+I will assume that you have already obtained the binary or src (http://smi-protege/repos/protege/lucene-query/trunk) for the lucene query plugin.  The code for this example can be downloaded from [[media:TestLuceneQuery.zip]].
 The test code I used had the following structure:
 <code><pre>

@@ Line 24: / Line 24: @@
 <code><pre>
      private static void indexOntology(KnowledgeBase kb) {
-         new InstallNarrowFrameStore(kb).execute();
+         QueryApi api = new QueryApi(kb);
-         new IndexOntologies(kb).execute();
+        QueryConfiguration config = new QueryConfiguration(kb);
+     }
 </pre></code>
 Now that we have indexed the ontology, we can do a programatic query.  This is done in the following code:
@@ Line 67: / Line 84: @@
+     }
 </pre></code>
 [[Category:Protege developer documentation]]

← Older revision		Revision as of 23:03, May 27, 2008
Line 74:		Line 74:
	This should really support other types of lucene search than phonetic. It looks like this is extremely easy to do but it has been a while since I touched this code.		This should really support other types of lucene search than phonetic. It looks like this is extremely easy to do but it has been a while since I touched this code.

−	[[Category:Protege ~~Developer Documentation]]~~	+	[[Category:Protege developer documentation]]
−	~~[[Category:Protege 3 Documentation~~]]

← Older revision		Revision as of 23:30, May 22, 2008
Line 73:		Line 73:

	This should really support other types of lucene search than phonetic. It looks like this is extremely easy to do but it has been a while since I touched this code.		This should really support other types of lucene search than phonetic. It looks like this is extremely easy to do but it has been a while since I touched this code.
		+
		+	[[Category:Protege Developer Documentation]]
		+	[[Category:Protege 3 Documentation]]

@@ Line 68: / Line 68: @@
 </pre></code>
-<h3>Issues</h3>
+<h2>Issues</h2>
 The indicies are stored in a slightly funny place (protege-dir/lucene/project-name/*).  We may want to choose a better approach and implement that.
 This should really support other types of lucene search than phonetic.  It looks like this is extremely easy to do but it has been a while since I touched this code.

← Older revision		Revision as of 21:49, January 2, 2008
Line 67:		Line 67:
	}		}
	</pre></code>		</pre></code>
		+
		+	<h3>Issues</h3>
		+
		+	The indicies are stored in a slightly funny place (protege-dir/lucene/project-name/*). We may want to choose a better approach and implement that.
		+
		+	This should really support other types of lucene search than phonetic. It looks like this is extremely easy to do but it has been a while since I touched this code.

← Older revision		Revision as of 21:45, January 2, 2008
Line 50:		Line 50:
	* queries that match slot values with the results of a nested query and		* queries that match slot values with the results of a nested query and
	* queries that look inside a restriction for matches to an inner query.		* queries that look inside a restriction for matches to an inner query.
		+
		+	Finally we add the lucene plugin as a tab to the project. I was not quite able to use the code suggested in [[AddingRemovingTabs\|Adding and removing tabs programmatically]] because when I retrieved the project view it was null. The code is as follows:
		+	<code><pre>
		+	@SuppressWarnings("unchecked")
		+	private static void addTab(Project project) {
		+	List errors = new ArrayList();
		+
		+	WidgetDescriptor tabWidgetDescriptor = project.getTabWidgetDescriptor("edu.stanford.smi.protege.query.LuceneQueryPlugin");
		+	tabWidgetDescriptor.setVisible(true);
		+
		+	Collection widgets = project.getTabWidgetDescriptors();
		+	project.setTabWidgetDescriptorOrder(widgets);
		+
		+	project.save(errors);
		+	displayErrors(errors);
		+	}
		+	</pre></code>

← Older revision		Revision as of 21:16, January 2, 2008
Line 44:		Line 44:
	}		}
	</pre></code>		</pre></code>
		+	There are several types of queries (some of which are composed out of other queries) defined in the lucene query plugin including:
		+	* conjuctions and disjunctions of queries,
		+	* queries that can only return a limited set of results,
		+	* queries that find regular expression matches for a slot value,
		+	* queries that match slot values with the results of a nested query and
		+	* queries that look inside a restriction for matches to an inner query.