Re: [Tracker] Write-back data & default/dummy data

["Juan A. Suarez Romero" <jasuarez igalia com>]

On Tue, 2009-10-27 at 00:58 +0000, Martyn Russell wrote:
> "Unknown" can be used as a valid value in some situations.
>
> The idea that Jurg came up with was to have a COALESCE() SPARQL 
> function, so you could have:
>
>     SELECT COALESCE(nie:title(?n),nfo:fileName(?n),"unknown")
>
> This way it falls back to those values in that order. I quite like this 
> approach, but I wonder if it is enough.

I like the idea too. Really, if this is not enough for some client, I
think she should implement it's own behaviour in the client side.


> > > 2. If we do have a default value to set, should we write this back to
> > > the file?
> >
> > I wouldn't write it back without asking the user first.
>
> We wouldn't.
>
> > This is not the
> > kind of behaviour I'd expect from tracker. (would you like to have all
> > of your videos renamed to unknown-whatever_was_here_before.mov?)
>
> I don't think this will happen anyway. Most of the team are not in 
> favour of doing this from recent discussion on IRC.

Me neither. As far as I understand, default values are not really stored
in tracker, but just returned when there is no value. So if each user
can specify it's own 'default' value, then it doesn't make sense to
write back to file.


> > If there's a dialog giving files with missing tags that could be fixed,
> > that's different.

IMHO this should be done by a 3rd party application. In MAFW we were
promoting the idea of writting daemons that perform behaviour that are
not part of MAFW itself (for example, scrobbling to Last.fm, or changing
Jabber status message with 'Playing <XXX>').

In this case, fixing the missing tags should be done by a different
application, that could use tracker stored values to write to file back.

        J.A.