Re: [Tracker] The Utopian idea, Tracker as it should be

[Vishesh Handa <me vhanda in>]

Hey Philip

On Mon, Sep 22, 2014 at 1:32 PM, Philip Van Hoof <philip codeminded be> wrote:

These relationships are vastly more important than typical
content-search data. 

I'm not going to deny that these relationships aren't important. They are not currently used in KDE. When some project in KDE decides that they require these formal relationships they can look into tracker or any other approach.

It's a nut that we must crack, rather than give up and create yet
another persistently stored Map<string, string>.

If Baloo is about a persistently stored Map<string, string> on
key-value pairs related to content of files on your FS: then Baloo
doesn't get metadata at all.

Baloo is just an index of your file's contents + metadata. Nothing more. They were ambitious plans earlier to incorporate relations and other similar concepts during the initial move from Nepomuk, but they all have been dropped.

updatedb and locate are good, and grep is good too. Combine the two
and you have a perfect solution. No need for a Baloo index. This is
not what Tracker and Nepomuk are about, at all.

Yup. I'm not trying to say that Baloo is a replacement for Nepomuk or Tracker.

 

>> small amount of information that we need to store - user tags
>> and ratings are stored in the xattr of the files.

But no relationships with other domains? Pity. With huge respect for
the technical implementation of Baloo, that nonetheless means you
developed not that much.

It also doesn't solve not that much that strings, cat, grep, updatedb
and locate also didn't already solve.

Baloo can be viewed as a glorified grep with a persistent index. It wouldn't be a big leap.

  

> Good luck with your project though Vishesh!

Yes. Good luck nonetheless. Maybe someday we can outsource simple
indexing of easily searchable content to Baloo?

Sure. 

From an implementation point of view we're currently using the Xapian full text index.

--
Vishesh Handa