Difference between revisions of "PIM/Akonadi/SearchInfrastructure"

View View source History
< PIM‎ | Akonadi
Jump to: navigation, search
(Create page and add file)
 
m (3 revisions imported)
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
 +
All about the search infrastructure of Akonadi.
 +
 +
== Concept ==
 +
 
Concept of the Akonadi search infrastructure:
 
Concept of the Akonadi search infrastructure:
  
 
[[File:Akonadi-search-infrastructure 20090723.png]]
 
[[File:Akonadi-search-infrastructure 20090723.png]]
 +
 +
== Query Language ==
 +
 +
Options:
 +
* SPARQL: de-facto standard by now (used by Nepomuk and Tracker), but way too complex for automatic query transformations.
 +
* XESAM (?)
 +
 +
 +
== Search Backends ==
 +
 +
Requirements:
 +
* fast enough
 +
* cross-platform
 +
* persistent/live search with change notifications
 +
 +
=== Possible Backends ===
 +
 +
* Nepomuk with Sesame2 or Virtuoso
 +
* Tracker (?)
 +
* XESAM (?)
 +
 +
=== Delegation to Resources ===
 +
 +
* Requires query transformation
 +
* Requires management for live searches
 +
* Requires the ability to report search results (needs protocol extension) [done by now]
 +
 +
 +
== Virtual Collections ==
 +
 +
Virtual collections are used to report results, for details see [[PIM/Akonadi/VirtualCollections]].
 +
 +
== Nepomuk Feeder Agents ==
 +
 +
* The delete/add approach removes otherwise added information such as tags when an item is modified.
 +
* Category to tag conversion uses non-Fast Nepomuk resources.
 +
 +
 +
[[Category:PIM]] [[Category:Akonadi]]

Latest revision as of 13:01, 11 March 2016

All about the search infrastructure of Akonadi.

Concept

Concept of the Akonadi search infrastructure:

Akonadi-search-infrastructure 20090723.png

Query Language

Options:

  • SPARQL: de-facto standard by now (used by Nepomuk and Tracker), but way too complex for automatic query transformations.
  • XESAM (?)


Search Backends

Requirements:

  • fast enough
  • cross-platform
  • persistent/live search with change notifications

Possible Backends

  • Nepomuk with Sesame2 or Virtuoso
  • Tracker (?)
  • XESAM (?)

Delegation to Resources

  • Requires query transformation
  • Requires management for live searches
  • Requires the ability to report search results (needs protocol extension) [done by now]


Virtual Collections

Virtual collections are used to report results, for details see PIM/Akonadi/VirtualCollections.

Nepomuk Feeder Agents

  • The delete/add approach removes otherwise added information such as tags when an item is modified.
  • Category to tag conversion uses non-Fast Nepomuk resources.
Retrieved from "https://community.kde.org/index.php?title=PIM/Akonadi/SearchInfrastructure&oldid=53751"

This page was last edited on 11 March 2016, at 13:01. Content is available under Creative Commons License SA 4.0 unless otherwise noted.