Re: Best way of using Beagle to index data CDs



The basic principle of a static index for a CD isn't out of the
ballpark, the plan for handling removable drives is pretty much just
that (although eventually we might want to integrate the indexes to
save space/query time) While hundreds of static indexes will defiantly
impact query time, it shouldn't be prohibitive.

The API for user-customizable attributes exisits, we need to do some
more integration for this kind of thing, I'm not sure how the static
indexer will handle it, but you could try using nautilus emblems (the
main FSQ indexes them) or the other option is to name your static
indexes and just work off of that, I don't think we do alot with what
static index something came from in beagle-search, but beagle-query
--verbose should reveal the static index that a hit came from. (I
think, if not it would be trivial addition to allow the user to define
a 'name' for the static index and map a property to that)

Cheers,
Kevin Kubasik

On 10/17/07, Nikolai Weibull <now bitwi se> wrote:
> Please direct me to the right mailing list if this isn't the
> appropriate one for things like this.  There doesn't seem to be a
> dashboard-users mailing list.
>
> I would like to use Beagle to index my data CDs.  I figured that
> static indexes was the way to go, but I haven't quite determined the
> best way of doing it.  My initial idea was to create an index for each
> CD, so that I could simply remove the index associated with a CD if I
> threw out the CD.  But then I started worrying about using hundreds of
> static indexes.  My idea then was to merge the static indexes into a
> master index that I could rebuild whenever an index was added or
> removed, using $(beagle-manage-index merge).
>
> Does this make sense?  Does anyone have a better suggestion?
>
> Also, I figured that I wanted to add an attribute to each file indexed
> in this way that says what CD it is on, for example, 'disc:N', where N
> is an integer.  There doesn't seem to be a way of doing this yet with
> beagle-build-index.  Is this something that would be interesting to
> see as a patch, or are user-defined attributes outside the scope of
> Beagle?
>
> Thanks!
> _______________________________________________
> Dashboard-hackers mailing list
> Dashboard-hackers gnome org
> http://mail.gnome.org/mailman/listinfo/dashboard-hackers
>


-- 
Cheers,
Kevin Kubasik
http://kubasik.net/blog


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]