Nepomuk/FileIndexer/de: Difference between revisions
Neverendingo (talk | contribs) (Created page with "{{Note|1=Diese Seite beschreibt die Nepomuk-Dateiindizierung und wie sie konfiguiert werden kann.}}") |
(Updating to match new version of source page) |
||
(5 intermediate revisions by 2 users not shown) | |||
Line 3: | Line 3: | ||
{{Note|1=Diese Seite beschreibt die Nepomuk-Dateiindizierung und wie sie konfiguiert werden kann.}} | {{Note|1=Diese Seite beschreibt die Nepomuk-Dateiindizierung und wie sie konfiguiert werden kann.}} | ||
== | == Dateiindizierung == | ||
Nepomuk | Nepomuk dient als primäre Dateiindizierung für den KDE Arbeitsbereich. | ||
=== | === Architektur === | ||
Mit dem KDE Arbeitsbereich 4.10 indiziert die Nepomuk-Dateiindizierung die Dateien in zwei Phasen. Die erste Phase namens Basisindizierung extrahiert den Dateinamen, Änderungsdaten und MIME-Typ. Die zweite Phase ist verantwortlich für den Inhalt der Datei und extrahiert Information wie den Artisten, das Album und Titel. | |||
By default the Basic Indexing always runs, and can be controlled by suspending the Nepomuk File Indexer via the Nepomuk Controller. File Indexing is only performed, by default, when the user is idle. | By default the Basic Indexing always runs, and can be controlled by suspending the Nepomuk File Indexer via the Nepomuk Controller. File Indexing is only performed, by default, when the user is idle. |
Latest revision as of 05:21, 6 June 2013
Dateiindizierung
Nepomuk dient als primäre Dateiindizierung für den KDE Arbeitsbereich.
Architektur
Mit dem KDE Arbeitsbereich 4.10 indiziert die Nepomuk-Dateiindizierung die Dateien in zwei Phasen. Die erste Phase namens Basisindizierung extrahiert den Dateinamen, Änderungsdaten und MIME-Typ. Die zweite Phase ist verantwortlich für den Inhalt der Datei und extrahiert Information wie den Artisten, das Album und Titel.
By default the Basic Indexing always runs, and can be controlled by suspending the Nepomuk File Indexer via the Nepomuk Controller. File Indexing is only performed, by default, when the user is idle.
Changing the default behavior
Based on your requirements, the user can change the default behavior and allow the FileIndexer to always run. This default behavior can be changed by editing the nepomukstrigirc and adding the following options -
[Indexing]
BasicIQDelay=0
FileIQDelay=0
NormalMode_FileIndexing=suspend
The following options can be changed -
- BasicIQDelay - By default, the basic indexing queue doesn't wait between files. An artificial delay can be introduced by this parameter.
- FileIQDelay - File Indexing is an intensive process. One might want a delay between files, so that the indexing runs slower.
- NormalMode_FileIndexing - This can be either "suspend" or "resume". If it is set to "resume" then the file indexer, will always be run during normal indexing.
Startup Scan
On starting the Nepomuk File Indexer, it scans through all the files marked for indexing and checks if they have been modified. This scan on startup may take some amount of time. By default it is not configurable. It can however, be avoided by adding this parameter to the nepomukstrigirc.
[General]
disable initial update=true
This will disable the startup scan of all the indexed files.
File Indexing Errors
Due to bugs and incorrect files one occasionally might encounter files which cannot be indexed. One can log the indexing errors in that case by changing the following parameter in nepomukstrigirc.
[General]
debug mode=true
This will cause all the file errors to be written to the $KDEDIR/share/data/nepomuk/file-indexer-error.log file. You might want to check this file and report the errors by uploading the relevant file and error on bugs.kde.org
File Formats
With the KDE Workspace 4.10 release, we no longer rely on Strigi for file indexing. We now rely on our own home-grown indexer which use libraries already heavily used within KDE.
In 4.10, we support most Image, Video, and Audio formats. We are however lacking in Document Formats and only support PDF. If you can encounter some file which you think has not been indexed, you can manually index it by manually running the following command nepomukindexer fileUrl
. Make sure you have Nepomuk debug messages. If the file has been successfully indexed, and Nepomuk has not managed to successfully extract the required information, then please file a bug report with the relevant details.