[Kde-pim] Does KMail Searching Work for Anyone?

[Christian Mollekopf]

On Fri, Jan 13, 2012, at 03:39 PM, Volker Krause wrote:
> On Thursday 12 January 2012 18:35:32 Allen Winter wrote:
> > On Thursday 12 January 2012 8:02:37 AM Allen Winter wrote:
> > > On Tuesday 13 December 2011 9:04:01 PM Allen Winter wrote:
> > > > I'm using master and l don't get any hits when I search.
> > > 
> > > Searching still fails completely for me and many others.
> > > I recall Volker mentioning something about a mismatch with certain nepomuk
> > > files that need to be updated in kdepim and/or kdepim-runtime.    But I
> > > don't have details.
> > > 
> > > Please, this must be fixed for the 4.8 release.
> > 
> > Additionally, I'm pretty sure Nepomuk is also involved with the contact
> > searching which may explain why the addresslineedit doesn't know much about
> > my addressbook.
> > 
> > I can create duplicate entries in my address book because the contact search
> > job always fails to find anything .
> > 
> > Something is broken with nepomuk.
> 
> Looking at the code I see that the Akonadi server is still assuming to
> find 
> the item id in the URI. From what I can see in my Nepomuk output, that's
> no 
> longer the case, with the new feeder and DMS, we now get random nepomuk:/ 
> URIs. Instead, the Akonadi item id seems to be in a custom property now. 
> Christian, can you confirm this?
> 

Yes, that is correct.

You can limit the search to akonadi items by filtering by type
(Vocabulary::ANEO::AkonadiDataObject()).
It would also be possible to limit the search by looking for the
ANEO::akonadiItemId property, although this was just added for backwards
compatibility and filtering by type is preferred.

So add
outer.addSubTerm(ResourceTypeTerm(Class(Vocabulary::ANEO::AkonadiDataObject())));
to the query and remove any assumptions about the uri.

> The corresponding Akonadi server code is in 
> akonadi/server/src/search/nepomuksearchengine.cpp, URI to item id
> translation 
> happens right at the top. Not exactly sure yet how to extract it from the 
> property, might need some changes to the SPARQL query to begin with, so
> it's 
> in the result set at all?
> 

URI to item id translation is definitely not doable anymore.
Request the NIE:url property from the queryservice, which should then be
available in the delivered result set.
NIE:url contains the full akonadi uri, ANEO::akonadiItemId would contain
the id only (would work too though).

I hope someone else can fix this as I'm running out of time with my
first exams coming up on monday...

Cheers,
Christian

_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/