From kde-doc-english Fri Apr 18 19:22:34 2014 From: Burkhard =?ISO-8859-1?Q?L=FCck?= Date: Fri, 18 Apr 2014 19:22:34 +0000 To: kde-doc-english Subject: [kde-doc-english] Nepomuk - Baloo (Desktop Search) Transition and missing User information Message-Id: <2751315.cvOJYSm53J () parodia> X-MARC-Message: https://marc.info/?l=kde-doc-english&m=139784896914474 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart1949207.irH4pe3N9c" This is a multi-part message in MIME format. --nextPart1949207.irH4pe3N9c Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Hi, first time I saw the new Baloo KCM Desktop Search I was really surprise= d=20 compared with the Nepomuk KCM (3 Tabs, lot of options). I had a lot of questions how indexing works + what is indexed and assum= ed the=20 typical KDE User familiar with the Nepomuk KCM would have similar quest= ions. So I filed a BR https://bugs.kde.org/show_bug.cgi?id=3D332030 > one mot= h ago, but=20 got no response. Reading some discussions about this topic (transition nepomuk -> baloo)= I=20 noticed a lot of user questions about this issue. So I started to collect some infos from Vishesh#s Blog, mailing list th= reads,=20 and community.kde.org/Baloo. This info collection is attached (no valid docbook article). What do you think, does it make sense to write a docbook article with a= nswers=20 to the basic and most important user questions from these info collecti= on? If yes, can anyone help doing this to file a RR for baloo? Thanks=20 --=20 Burkhard L=FCck --nextPart1949207.irH4pe3N9c Content-Disposition: attachment; filename="index.docbook" Content-Transfer-Encoding: quoted-printable Content-Type: application/docbook+xml; name="index.docbook" ]>
Desktop Search SebastianTrueg= trueg@kde.org 2014-04-18 &kde; 4.13 KDE KControl baloo desktop search Introduction https://bugs.kde.org/show_bug.cgi?id=3D332030 Baloo is a metadata and search framework which is a successor to the Ne= pomuk=20 project. It primarily provides - * An API for searching * A way of storing relations between entities * File indexing * Email and Contact Indexing * timeline kioslave http://community.kde.org/Baloo: Migrating data from Nepomuk to Baloo=20 Nepomuk was used to store the tags, ratings, and user comments in Files= . This data can be migrated by running the nepomukbaloomigrator. There = is no continuous synchronization between Baloo and Nepomuk. Nepomuk was= also used to store indexed information about Files, Emails and Contact= s. Baloo shall reindex this information directly from the source.=20 [ Running Nepomuk and Baloo together=20 Nepomuk and Baloo can both coexist without issues. However, it may not = be the best idea to run both of them on the same system as they both wo= uld then be indexing your files, emails and other data and taxing the s= ystem heavily, populating their databases.=20 Tags, ratings and comments will be not be synchronized between Nepomuk = and Baloo after the initial migration. The majority of Nepomuk applications just rely on its tags, ratings and= comments features. Baloo offers a simple asynchronous API for modifyin= g that file metadata. This metadata is now stored with the extended att= ributes of the file instead of storing it in a separate database. Dolphin, GwenView,=20 http://vhanda.in/blog/2014/04/desktop-search-configuration: The old module was built on top of Nepomuk and it explicitly mentions t= hat on the top. While =E2=80=9CNepomuk=E2=80=9D was a decently known br= and within the KDE Community, a normal user cannot be expected to know = what it is. It also presented a plethora of options in order to disable and enable = Nepomuk, the File Indexer (used to say Strigi) and the PIM indexing. It= also provides ways to control the indexing and labels to show what exa= ctly is going on. With the new module we have removed all of these options. The user shou= ld not need to know about the project called =E2=80=9CBaloo=E2=80=9D, a= nd indexing is an internal implementation detail in order to make searc= hes faster. It doesn=E2=80=99t need to be broadcasted. Additionally now that we=E2=80=99re so much faster, we can no longer af= ford to inform the user about each file. We often indexing hundreds of = files per second. Plus, the files are indexed in multiple stages. The old module=E2=80=99s primary function was to control what is indexe= d. This was done in another tab=20 This allowed the user to set which types and mimetypes of files should = be indexed, control the list of regular expressions which should be mat= ched against the filename, and control the list of directories which sh= ould be indexed, and which should not. We now index your HOME directory by default and allow you to black list= certain directories which you may not want to appear in the search res= ults The custom regular expression and mimetype filtering has been removed. = We believe that it wasn=E2=80=99t something an average user would know = or care about. Also, we don=E2=80=99t think anyone should need to micro= -optimize the indexer to such a level This current release does not fully support removable media. By default= all removable media are not indexed. You can however remove them if th= e blacklist in order to index them. There is no explicit =E2=80=9CEnable/Disable=E2=80=9D button any more. = We would like to promote the use of searching and feel that Baloo shoul= d never get in the users way. However, we are smart about it and IF you= add your HOME directory to the list of =E2=80=9Cexcluded folders=E2=80= =9D, Baloo will switch itself off since it no longer has anything to in= dex This new KCM does remove a large number of options, but we considered t= hose to potential optimizations from the Nepomuk days when we were not = that performant. Baloo does still support most of these options, they j= ust have sane defaults and are no longer exposed. Vishesh Handa in thread Systems Settings - Desktop Search on kde-devel@= kde.org Here is how it currently works - * By default your HOME directory is indexed, and all other external mou= nts are=20 are excluded. * The UI will show the list of all excluded mounts and excluded folders= that=20 have been manually added. So if you want some external mount to be indexed, just remove it from t= he=20 blacklist. >=20 > will it be possible to run KDE without baloo enabled? >=20 Yes. You can go to System Settings -> Desktop Search -> Exclude Folders= , and=20 add your $HOME directory over there. Otherwise you can also edit the baloofilerc file and add the following = - [Basic Settings] Indexing-Enabled=3Dfalse ~/.kde/share/config$/baloofilerc https://bugs.kde.org/show_bug.cgi?id=3D333020 No way to index directori= es off root via UI Editing the ~/.kde/share/config/baloofilerc file and adding: "folders[$e]=3D/data2/,$HOME/" will give the desired results.
--nextPart1949207.irH4pe3N9c Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kde-doc-english mailing list kde-doc-english@kde.org https://mail.kde.org/mailman/listinfo/kde-doc-english --nextPart1949207.irH4pe3N9c--