Ticket #620 (closed defect: fixed)

Opened 7 weeks ago

Last modified 7 weeks ago

default localsearch should find things and rank them higher

Reported by: leosauermann Owned by: ChristianKohlschutter
Priority: major Milestone: m36-redmeteor
Component: comp-localsearch Version:
Keywords: Cc:

Description

At the moment, localsearch does not find things in the first results. entering the label(nao:preflabel, rdfs:label, nao:personalIndentifier) of a thing does not retrieve it, or ranks it so bad that it isn't shown.

this is apparent in pimo classbrowser's search and in pimo searchperspective.

  • Problem: user's will remember the labels of their things (=their tags) and will search for them.
  • possible solution: the rank of things must be higher than any information element containing the same name. Could be implemented by searching first for things and then fro information elements (then the ranking algorithm would not be changed)

Change History

Changed 7 weeks ago by christiankohlschutter

I have recently changed LocalSearch to filter out more resource types than before, maybe this is the reason. Could you please provide more details about the data you are going to find? (e.g., provide some testdata and a query).

Cheers, Christian

Changed 7 weeks ago by leosauermann

Things: I search for instances of pimo:Thing. I think you did not filter out these :-)

if you take claudia's testdata, search for "CID". the search result shows anything BUT the cid project. (it shows 42 unimportant information elements, but NOT the important CID project with URI http://www.sap.com/people/claudia#CID

Changed 7 weeks ago by heikohaller

I seem to have the same problem and It seems to me it is not a ranking problem, since none of my PIMO Things are found at all. Crawled documents are found, but not stuff that I create in PIMO.

Changed 7 weeks ago by christiankohlschutter

I have deactivated type-based resource filtering again. I think this was the culprit.

The RDF repository data had been tidied up recently -- and the ontology information which was used to build up the filtering rules got removed from the repository, which resulted in too sharp filtering (i.e., all subclasses of Pimo:Thing were filtered out).

Please let me know if it works for you now (check out localsearch from SVN)

Christian

Changed 7 weeks ago by leosauermann

Deactivating the filtering is weird - the search had "search all categories" selected, so all should be included... hm.

Anyway, it works better now.

Things are still not ranked higher.

Another optimization could be: when a Thing exists for an InformationElement? resource (related using occurrence or groundingoccurrence) the InformationElement? could be filtered out (= searching for claudia should return the PIMO:Person claudia as first hit, finding the occurrences of claudia can be done when clicking claudia..)

Changed 7 weeks ago by leosauermann

btw: commit to ETP! we need this in the nightly builds

Changed 7 weeks ago by christiankohlschutter

  • status changed from new to closed
  • resolution set to fixed

Good to hear that it's working for you. I have committed the changes to ETP (LocalSearch 1.2.6).

Optimizing the ranking process is another issue which also involves tweaking other components. The "missing things" bug really was caused by a LocalSearch-internal binary filter (not the "category" filter), which became unnecessary now that the RDF dataset is much cleaner than it was before.

Considering this issue as closed.

Note: See TracTickets for help on using tickets.