+1 to Mikkel on using it for deletes too, having two different systems
doesn't make sense.
Also, I'd keep uri and current_uri as separate things (current_uri
being a new parameter in event, that's why it's a nice array...), else
this is going to be a real mess.
Monitoring Create/Move/Copy Files events
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
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
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
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 :)
Mailing list: https://launchpad.net/~zeitgeist
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~zeitgeist
More help : https://help.launchpad.net/ListHelp