zeitgeist team mailing list archive

[Seif Lotfy <602211@xxxxxxxxxxxxxxxxxx>]

OK what would happen if we use our uri table as our lookup table and add
the above table as the uri_tracking_table

Another though would be actually to have the normal uri_table and a new update_uri_table
where we link and id to its new id

so moving foo to bar will give us
============================

id | value
---------------
1 | foo.txt
2 | bar.txt

id | new_value_id
-----------------------
1 | 2


now in case we move bar.txt to lol.txt we just update the DB again by checking the all value_ids = 2 and change it to 3 and add a new row...

id | value
---------------
1 | foo.txt
2 | bar.txt
3 | lol.txt

id | new_value_id
-----------------------
1 | 3
2 | 3


so if the user asks for raw events we do what we always did
if the user asks for updated events (updated subject_uris) we will need to join once... It comes with a cost of performance but I think we can handle it

We need to actually sprint on that issue.

I marked this as effecting Unity since when I move a file i don see it
in unity anymore

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