USB hdd support

[Maximilian Kossick]

Sorry, of course the unique value is the primary key in the ATF table. The 
filename is the primary key in both the statistics and tags table. That's why 
I called it primary key, but it's obviously just a foreign key in the ATF 
table. I'll change the wording on the wiki page.

Concerning "User-defined labels", I have nothing to add to what Andrew wrote 
below. What he wrote is exactly what I meant by it. 

Cheers, Max

> Not trying to speak for Max here, but just reading what he's written
> on the Wiki:
>
> The whole "User-defined labels" section doesn't really seem to ever
> intersect with the concept of labels as you have taken to understand
> it (ie as a way of adding freeform metadata tags for songs as in bug
> 89314.) Instead it seems like just giving the devices names so that
> they can be referred to easily, something I think that must be done,
> else it would be ludicrously confusing.
>
> As for the ATF section, I agree it's either wrong or maybe a
> mistranslation.
>
> I'll make some quick changes.
>
> Andrew
>
> On 31/05/06, Jeff Mitchell <kde-dev at emailgoeshere.com> wrote:
> > Max--
> >
> > Haven't looked at this fully yet, as I'm just glancing at it before I
> > head out the door, but a couple of things I saw off the bat:
> >
> > User-defined labels:  the concept of labeling is something we've kicked
> > around for a while now.  This would solve problems people have right now
> > where there's a situation like having "Paul Simon" and "Simon and
> > Garfunkel" (not the greatest example, but you get the picture).  In many
> > cases the user wants to keep those artist tags in the file, but be able
> > to find it by looking for Paul Simon.  A label that could be assigned
> > dynamically to tracks and contain a subset of user-chosen items would be
> > great (think of Gmail's labels).  If you come up with a good way to do
> > labeling, then you could not only have labels for songs, but you could
> > automagically create labels that cover available parts of the collection
> > and use the functionality for either.  So as you think about device
> > labels, keep song labels in mind too.
> >
> > ATF and dynamic collection:
> > You are correct that ATF associates a unique value with a file to keep
> > track of it, even if amaroK is closed, without requiring services to be
> > constantly on and watching file changes (have fun reinventing the wheel,
> > Gnome multimedia SoC hacker wannabe).  What you got wrong is that the
> > file's "primary key" as it were is not the absolute file name/URL.  After
> > all, this is what can get inconsistent!  Relying on the URL would solve
> > nothing whatsoever.  The file's primary key is an 8-character randomly
> > generated string embedded in the file's metadata.  This is then used to
> > figure out where files moved around to, and to update the absolute file
> > name/URL in the database.  How you'd use this with dynamic collections is
> > probably to have the device identifier as you mentioned, and then have
> > ATF lookups return not just the URL but the device identifier as well.
> >
> > --Jeff
> >
> > On Tuesday 30 May 2006 07:47, Maximilian Kossick wrote:
> > > Hi
> > > I have created a wiki page for this topic:
> > > http://amarok.kde.org/amarokwiki/index.php/Dynamic_Collection
> > >
> > > It explains what I want to do in some more detail.
> > >
> > > Cheers, Max
> >
> > _______________________________________________
> > Amarok mailing list
> > Amarok at kde.org
> > https://mail.kde.org/mailman/listinfo/amarok
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/amarok/attachments/20060531/2c7eb752/attachment.sig>