zeitgeist team mailing list archive

[Mikkel Kamstrup Erlandsen <mikkel.kamstrup@xxxxxxxxx>]

On 15 November 2010 21:08, Siegfried Gevatter <rainct@xxxxxxxxxx> wrote:
> 2010/11/15 Michal Hruby <michal.mhr@xxxxxxxxx>:
>> I still didn't understand why would the current_uri be part of event,
>> isn't it by definition a property of the subject? That way you don't
>> need to update dozens of events, just one subject entry...
>
> A subject is part of an event, there is no global "subject entry"
> since the subject represents a snapshot of an object at a particular
> time instant (with some properties -eg. mimetype- which it has at that
> instant).

I understand your confusion Michal. The deal is that while subjects
are conceptually disjoint from the event they are still stored
together with the event in the event table (as an optimization). Also
as Siegfried says - the event subject is a snapshot (like a normal log
statement) so it makes even more sense to store it together with the
event as we do.

-- 
Monitoring Create/Move/Copy Files events
https://bugs.launchpad.net/bugs/602211
You received this bug notification because you are a member of Zeitgeist
Framework Team, which is subscribed to Zeitgeist Framework.

Status in Unity: Triaged
Status in Unity Files Place: Triaged
Status in Zeitgeist Framework: Confirmed
Status in Zeitgeist Datahub: Confirmed

Bug description:
An issue we are facing at the moment is that ppl lose track of there files in a timeline if the file was moved around or renamed. I would propose using taskview or patch nautilus to actually grab those events and either:
1) Modify the uris in the uris table
2) Create a new table with    | new_id | old_uri_id | event | to map uris to their actual ids and the event that allowed the change, this would allow us to track a history of renaming or moving a file. It will look a bit like the following:

9 | 9 | 48124  # CREATE EVENT
12 | 9 | 48126 # MOVE EVENT

In other words the last row means uri 12 was moved from uri 9 with event 48126

UPDATE:

3) Create a changable_uri table that is a map of the uri table. it gets updated upon moved and rename.
We then add new resulttype that allow you to ask for either pureSubject or adaptedSubject. depending on which one is chosen we then use the according table in the join of the find_events_query :)