Development/Tutorials/Metadata/Nepomuk/StrigiService: Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 2: | Line 2: | ||
series=[[../|Nepomuk]]| | series=[[../|Nepomuk]]| | ||
name=Nepomuk Strigi Service| | name=Nepomuk Strigi Service| | ||
pre=[[../ | pre=[[../FileWatchService|File Watch Service]]| | ||
next=[[../QueryService|Query Service]]| | next=[[../QueryService|Query Service]]| | ||
reading=[[../NepomukServices|Nepomuk Services]], [[../NepomukServer|Nepomuk Server]]| | reading=[[../NepomukServices|Nepomuk Services]], [[../NepomukServer|Nepomuk Server]]| | ||
Revision as of 20:35, 17 November 2008
Nepomuk Strigi Service
| Tutorial Series | Nepomuk |
| Previous | File Watch Service |
| What's Next | Query Service |
| Further Reading | Nepomuk Services, Nepomuk Server |
Nepomuk Strigi Service
The Nepomuk Strigi service uses the libstreamanalyzer library provided by Strigi to analyze all files in the configured folders and store their metadata in the Nepomuk repository.
The service monitors certain events such as a change in the battery status (will not index when running on batteries) or if the hard disk space is running low. In the latter case indexing is suspended until hard disk space is freed.
The service provides a D-Bus interface org.kde.nepomuk.Strigi which is exported at nepomukstrigiservice. It allows to suspend/resume the indexing, index specific folders or files and informs about the current status of Strigi.
This service is supposed to be configured via the Nepomuk KCM.