zeitgeist team mailing list archive

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

On 15 November 2010 21:07, Seif Lotfy <602211@xxxxxxxxxxxxxxxxxx> wrote:
> SNIP
> So lets say I have a file that has been moved from /home/seif/foo to
> /home/seif/bar. This means I query for all events where subject_uri =
> /home/seif/foo so I get all results until the point it was moved, right? And
> if I ask for /home/seif/bar I get all events with subject_uri =
> /home/seif/foo as well as all subject_uri = /home/seif/bar ... ?

We still do strict template matching. If you query for event with
subject_uri=bar then you wont get any events with subject_uri=foo,
disregarding the subject_current_uri.

Otoh if you query for events with subject_current_uri=bar you will get
all events for subject_uri=foo too because these events will have been
set to subject_current_uri=bar. Note that we are *not* being clever
about matching on both the subject_uri and subject_current_uri fields.
It's still strict matching on the subject_current_uri field that gives
you these results.

-- 
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 :)