Re: Metadata use ideas collecting... :)

Here's a metadata idea that I've been kicking around
for a while:
To augment some of the search ideas people have put
forth in reply to this thread, I'd like to suggest
collecting a list of applications launched, activated,
and what files they wrote to as a very interesting
kind of metadata.

For example:
	If I switch from a word processor to email, there's a
decent chance that the two documents are related.  If
I do it 3 or 4 times in quick succession, there's a
pretty high chance that the two are related.  So if I
start looking for that document I was writing about
business opportunities abroad, such a search could
rely on the fact of my having switched into the email
and then the spreadsheet a number of times to bring up
related documents as a search documents.

	Another use would be to set each virtual desktop as
corresponding to a project, and use the data about
what app ran when and on what desktop, and what files
each app saved to organize to automatically save the
user's data into the appropriate project.  As an even
more ambitious idea, each project could then be
handled in a by CVS-style content management system
which let you handle versions, revisions, undos, etc. 
And of course, you'd be able to turn it all off....

Of course there's a whole raft of privacy issues with
collecting information about what a user's doing, but
this is a natural consequence of having the computer
understand what you're doing - it can tell someone
else.  And I think KDE can handle it will by putting
the user in total control of such data.

Add this to the list of metadata ideas.

Cheers,

Eric


--- "Friedrich W. H. Kossebau"
<[email protected]> wrote:
> Hello!
> 
> There has been at least one big thread two years ago
> on the topic of
> metadata on this list. It hasn't produced a lot if I
> didn't miss
> anything. Thomas Zander showed up with a first
> script based
> implemantation of storing of Extended attributes on
> filesystem with no
> support for but it seems to have died the other day.
> 
> Now I still don't have a real clue what kind and
> structure of metadata
> are usefull at all. So I would like to collect some
> ideas. 
> 
> What need do you have for metadatas? Post your ideas
> on this list, we
> should collect them and build a concept so some of
> the coders hanging
> around might get the taste and really get on
> implementing.
> 
> To show up with the good example I will start and
> take my specific need:
> 
> I would like free defineable attributs that are
> bound either to specific
> mimetypes or all files. Some are with default
> values, some not, so they
> don't need to be set explicitly on a file. There may
> be attributes with
> a fixed set of values, like
> 
> attribut "type" for kword-files has to have a value
> out of (with
> [default]): 
> letter, report, chapter, simple, [unknown]
> 
> attribut "working state" for all files can have a
> value out of:
> created, work in progress, needs review, almost
> finished, done
> 
> I would like this metadata to be changed by those
> who have write access
> to the file and being the same for all, even those
> with only read
> access.
> 
> So I could do hopefully one day in kde (here in
> commandline style):
> find ~/girls -name *loveyou*.kwd -attr "type=letter"
> -mtime +0 -exec rm
> {}\;
> or the like ;)
> 
> Interchangeability with other systems could be a
> problem but there will
> soon be some standards with a reasonable set I
> expect. Friends will
> adjust their attribute sets.
> 
> If you work in a project group you simply have to
> agree on a common set
> of attributes. I don't think this is a great
> problem. You choose what
> you need. No restrictions. 
> 
> 
> And what do you expect from metadata?
> 
> Friedrich
> 
> 

__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com