dustinchang / relfinder

Automatically exported from code.google.com/p/relfinder
0 stars 0 forks source link

Missing items in autocompletion #20

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I am missing terms in the autocompletion list. I understand there is a
limit to what autocompletion is returning to preserve performance, but
there is no way to use a node that does exist but is not returned by
autocompletion.

For example, if I have a page called 'Chemistry' and I type 'Chemistry' in
the search form, autocompletion is giving me a list of pages that include
'Chemistry' in the title but it is missing the 'Chemistry' page itself. 

And since there is no way to submit the form without selecting from
autocompletion, I cannot use that page as a starting node.

RelFinder should provide a way to enter a term and validate it exists
without having to go through autocompletion.

Original issue reported on code.google.com by lalqu...@gmail.com on 16 Nov 2009 at 7:10

GoogleCodeExporter commented 9 years ago
Beta version (http://relfinder.semanticweb.org/RelFinderBeta.swf) already has a
direct input feature in the disambiguation window.

Original comment by stegeman...@googlemail.com on 1 Dec 2009 at 2:36

GoogleCodeExporter commented 9 years ago
This is a good first step.

Is there anyway to not have to provide a full URI when selecting direct input ?

Users will typically not know the full prefix of the URI. I would expect 
RelFinder 
to resolve the direct input against the default graph of the data source.

Original comment by lalqu...@gmail.com on 15 Dec 2009 at 8:22

GoogleCodeExporter commented 9 years ago
The disambiguation/suggestion window has now the possibility to browse through 
all
results for an input string. So every object of an endpoint should be trackable.

Original comment by stegeman...@googlemail.com on 18 Dec 2009 at 12:51

GoogleCodeExporter commented 9 years ago

Original comment by stegeman...@googlemail.com on 5 Feb 2010 at 1:51