[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: GSoC Ideas involving Baloo
From:       Denis Steckelmacher <steckdenis () yahoo ! fr>
Date:       2014-03-13 16:36:17
Message-ID: 5321DE81.3000501 () yahoo ! fr
[Download RAW message or body]

On 03/13/2014 03:52 PM, Vishesh Handa wrote:
>> * Support for arbitrary attributes in the file search store (so that we
>> don't need to add explicit support for the hundreds of properties that
>> JPEG and MP3 files can have), if you think that it's a good idea
>
> I'm not sure I understand, could you please elaborate.
>

I have explored the code of the file indexers, and there is a file named 
properties.h (it declares the valid properties that can be used when 
extracting files). This list is quite extensive and seems to alleviate 
my problem: I thought that only the 5-6 properties listed at the 
beginning of the file search store source code (in Baloo Core) were 
available.

By the way, PropertyInfo is also very interesting and it may be 
interesting to use it in the query parser (so that the user can enter 
"artist is Foo" and queries like that). This justifies putting the query 
parser in a separate library to avoid a cyclic dependency between Baloo 
Core and kfilemetadata.

>> * "Remote" file extractors: if the user asks for it, such extractors
>> could be used to query IMDB for tags and attributes. This should not be
>> automatic as downloading web pages takes time and bandwidth, but having
>> a button in FileMetadataWidget to perform this task may be useful to
>> many people. Nepomuk had a concept of "indexing level", does a similar
>> concept exist in Baloo?
>
> Having online content is always useful, but in the right settings. It may not
> be very useful in Dolphin which is after all a file manager, but it would be
> very very useful in a media application.
>
> In that case the media player would be responsible for deciding when to fetch
> the online data. And then, we don't really need to store that information in
> the same index as the current files. Unless this needs to be part of the global
> search.
>
> This is probably best discussed with the multimedia guys, Plasma Media Center,
> and Jorg who did the Nepomuk web-extractor.

Okay, I will talk to them. Storing this kind of meta-data directly in 
the Baloo database could be useful because it would allow a generic 
application (like a Baloo browser or search engine, or a file manager) 
to find documents and media content based on any search. For instance, 
an application like Plasma Media Center (or even Plasma Active) could 
display files sorted by album, author, composer, series, origin, type, etc.


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]