Nepomuk/FileIndexer/ca: Difference between revisions

From KDE UserBase Wiki
(Created page with "=== Arquitectura ===")
(Updating to match new version of source page)
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<languages/>
<languages/>
{{Historic}}


{{Note|1=This page documents the Nepomuk File Indexer and how it can be configured.}}
{{Note|1=This page documents the Nepomuk File Indexer and how it can be configured.}}


<span id="File_Indexer"></span>
== Indexador de fitxers ==
== Indexador de fitxers ==


Nepomuk serves as the primary file indexer for the KDE Workspace.
Nepomuk serves as the primary file indexer for the KDE Workspace.


<span id="Architecture"></span>
=== Arquitectura ===
=== Arquitectura ===


Line 13: Line 17:
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.


==== Changing the default behavior ====
<span id="Changing_the_default_behavior"></span>
==== Canviar el comportament per omissió ====


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 <tt>nepomukstrigirc</tt> and adding the following options -
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 <tt>nepomukstrigirc</tt> and adding the following options -
Line 33: Line 38:
* 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.
* 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 ===
<span id="Startup_Scan"></span>
=== Iniciar l'escaneig ===


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 <tt>nepomukstrigirc</tt>.
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 <tt>nepomukstrigirc</tt>.
Line 45: Line 51:
This will disable the startup scan of all the indexed files.
This will disable the startup scan of all the indexed files.


=== File Indexing Errors ===
<span id="File_Indexing_Errors"></span>
=== Errors indexant fitxers ===


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 <tt>nepomukstrigirc</tt>.
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 <tt>nepomukstrigirc</tt>.
Line 57: Line 64:
This will cause all the file errors to be written to the <tt>$KDEDIR/share/data/nepomuk/file-indexer-error.log</tt> file. You might want to check this file and report the errors by uploading the relevant file and error on [http://bugs.kde.org bugs.kde.org]
This will cause all the file errors to be written to the <tt>$KDEDIR/share/data/nepomuk/file-indexer-error.log</tt> file. You might want to check this file and report the errors by uploading the relevant file and error on [http://bugs.kde.org bugs.kde.org]


=== File Formats ===
<span id="File_Formats"></span>
=== Formats de fitxer ===


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.
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.
Line 63: Line 71:
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 <code>nepomukindexer '''''fileUrl'''''</code>. 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.
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 <code>nepomukindexer '''''fileUrl'''''</code>. 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.


[[Category:System]]
[[Category:Sistema/ca]]

Latest revision as of 05:25, 19 May 2024

Other languages:

Historic page

This page is of historic interest only. The content of the page is obsolete.


Note

This page documents the Nepomuk File Indexer and how it can be configured.


Indexador de fitxers

Nepomuk serves as the primary file indexer for the KDE Workspace.

Arquitectura

With KDE Workspace 4.10, the Nepomuk File Indexer indexes the files in two phases. The first phase, called Basic Indexing, just extracting the filename, modification date, and mimetype. The second phase is responsible for looking inside the file and extracting information such as the Artist, Album and Title.

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.

Canviar el comportament per omissió

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.

Iniciar l'escaneig

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.

Errors indexant fitxers

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

Formats de fitxer

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.