Re: [Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events
Agreed I think I am overthinking it a bit. I am pretty ok with this solution but we shouldn't jump dive into it unless we are pretty comfortable all of us. What will break is also an issue for me.. On Tue, Nov 16, 2010 at 11:06 PM, Mikkel Kamstrup Erlandsen < mikkel.kamst...@gmail.com> wrote: > On 15 November 2010 21:07, Seif Lotfy <602...@bugs.launchpad.net> 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 direct subscriber > of the bug. > > 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 :) > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/unity/+bug/602211/+subscribe > -- This is me doing some advertisement for my blog http://seilo.geekyogre.com -- 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 :) ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events
On 15 November 2010 21:07, Seif Lotfy <602...@bugs.launchpad.net> 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 :) ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events
On 15 November 2010 21:08, Siegfried Gevatter wrote: > 2010/11/15 Michal Hruby : >> 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 :) ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events
2010/11/15 Michal Hruby : > 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). -- Siegfried-Angel Gevatter Pujals (RainCT) Free Software Developer 363DEAE3 -- 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 :) ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events
I completely agree that current_uri as a new parameter however once u use it u will need to use the the logic i described before: 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 ... ? I dont mind using it for deletes. As I said its a nautilus patch On Mon, Nov 15, 2010 at 8:21 PM, Michal Hruby wrote: > 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... > > -- > Monitoring Create/Move/Copy Files events > https://bugs.launchpad.net/bugs/602211 > You received this bug notification because you are a direct subscriber > of the bug. > > 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 :) > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/unity/+bug/602211/+subscribe > -- This is me doing some advertisement for my blog http://seilo.geekyogre.com -- 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 :) ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events
+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 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 :) ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events
TBH I am not fond of the idea of having the file monitor inside Zeitgeist. Zeitgeist is about events first. Also this means we will need to reside on inotify and this is a BIG NO from me again. Unless we have fanotify I dont even think we should look at the solution being inside Zeitgeist TBH. I however do like the idea of extending the event table as a fallback solution for now, although it really does break the idea of an event is immutable. I am trying to convince myself that this is not an issue though. So I want to propose a new solution that builds on top of Mikkel's idea. * change the event table to include current_subject_uri * add a logic that handles MOVE/COPY/RENAME events * listen to MOVE/COPY/RENAME events from outside sources such as nautilus (by patching, ssickert has a patch) What do you think? On Thu, Nov 11, 2010 at 9:27 AM, Mikkel Kamstrup Erlandsen < mikkel.kamst...@gmail.com> wrote: > All of these clever remapping schemes scare me a bit to be honest. > They all seem to imply a non-negligible impact on our query time, and > a considerable amount of logic. > > A simpler and more performant scheme, which requires an API break (!), > is to simply add an extra field on our Subject structure > "current_uri". In the DB we represent this as an extra column on the > 'event' table which holds the URI id of the current location of the > subject. > > Doing it like this would require that the file monitor lives inside > Zeitgeist - and not as an extension, but as a core component, since it > requires a special db structure. The file monitor would then directly > modify the 'current_uri' column of the 'event' table on file events. > This breaks our "events are immutable" invariant - which i'm otherwise > very fond of... So there are many drawbacks to this approach. > > Despite all the drawbacks something inside me tells me that something > like this is the right solution. > > I very much dislike adding advanced stuff like a file monitor as a > core component, but we could make up for this, by having it be like a > stub, that didn't do anything by default, but would have to be > instrumented by an extension or something... So it requires air fair > deal of thought architecture wise... > > -- > Monitoring Create/Move/Copy Files events > https://bugs.launchpad.net/bugs/602211 > You received this bug notification because you are a direct subscriber > of the bug. > > 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 :) > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/unity/+bug/602211/+subscribe > -- This is me doing some advertisement for my blog http://seilo.geekyogre.com -- 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 w
Re: [Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events
All of these clever remapping schemes scare me a bit to be honest. They all seem to imply a non-negligible impact on our query time, and a considerable amount of logic. A simpler and more performant scheme, which requires an API break (!), is to simply add an extra field on our Subject structure "current_uri". In the DB we represent this as an extra column on the 'event' table which holds the URI id of the current location of the subject. Doing it like this would require that the file monitor lives inside Zeitgeist - and not as an extension, but as a core component, since it requires a special db structure. The file monitor would then directly modify the 'current_uri' column of the 'event' table on file events. This breaks our "events are immutable" invariant - which i'm otherwise very fond of... So there are many drawbacks to this approach. Despite all the drawbacks something inside me tells me that something like this is the right solution. I very much dislike adding advanced stuff like a file monitor as a core component, but we could make up for this, by having it be like a stub, that didn't do anything by default, but would have to be instrumented by an extension or something... So it requires air fair deal of thought architecture wise... -- 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 :) ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events
I am aware of that issue and am brainstorming to solve it. for that we will need to have 2 more columns lets try your example: event with foo.txt uri_id | value | new_uri_id | old_uri_id | - 1 | foo.txt | -1 | -1 event "renaming/moving" foo.txt to bar.txt uri_id | value | new_uri_id | old_uri_id | - 1 | foo.txt | 2 | -1 2 | bar.txt | -1 | 1 event "creating" new foo.txt. uri_id | value | new_uri_id | old_uri_id | - 1 | foo.txt | -1 | -1 2 | bar.txt | -1 | 1 This implies that foo.txt is new since it has no old uri not does it have a new one however bar.txt is linked to foo.txt since the old foo.txt is its origin. This will allow me to search bar.txt and get foo.txt as a result (which is not good for feature events) but foo.txt is not linked to bar.txt We need more time for that issue On Tue, Nov 9, 2010 at 2:39 PM, Siegfried Gevatter wrote: > 2010/11/9 Seif Lotfy <602...@bugs.launchpad.net>: > > OK I think we can just add 1 column that links to the new uri in the uri > > table so it becomes > > Keep in mind that the same URI can be reused for different things, > though. I may rename foo.txt to bar.txt and create a new foo.txt. > > -- > Monitoring Create/Move/Copy Files events > https://bugs.launchpad.net/bugs/602211 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Zeitgeist Framework: Confirmed > Status in Zeitgeist Datahub: Incomplete > > 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 :) > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/zeitgeist/+bug/602211/+subscribe > -- This is me doing some advertisement for my blog http://seilo.geekyogre.com -- 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 Zeitgeist Framework: Confirmed Status in Zeitgeist Datahub: Incomplete 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 :) ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events
2010/11/9 Seif Lotfy <602...@bugs.launchpad.net>: > OK I think we can just add 1 column that links to the new uri in the uri > table so it becomes Keep in mind that the same URI can be reused for different things, though. I may rename foo.txt to bar.txt and create a new foo.txt. -- 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 Zeitgeist Framework: Confirmed Status in Zeitgeist Datahub: Incomplete 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 :) ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events
Keep an LRU cache[1] of inotify watches (or GFileMonitors more likely) on the last 350 used files. Log some relevant event when they change. This could be done either from an extension or a DP. The tricky part os probably making sure that we don't log a lot of dupe entries (I'm not sure the DataSourceRegistry is enough here). [1]: Reviving my old impl from the bzr history would probably be sanest - there are some very bad Python lru cache implementations floating the interwebs. Caveat emptor. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events
awesome :) On Sun, Nov 7, 2010 at 9:15 PM, S. Sickert wrote: > I agree that 95% of the user never use the commandline, so that's not a > big problem. > > AFAIK renaming in nautilus is just moving the file. > > -- > Monitoring Create/Move/Copy Files events > https://bugs.launchpad.net/bugs/602211 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Zeitgeist Framework: Confirmed > Status in Zeitgeist Datahub: Incomplete > > 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 > > > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/zeitgeist/+bug/602211/+subscribe > -- This is me doing some advertisement for my blog http://seilo.geekyogre.com -- 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 Zeitgeist Framework: Confirmed Status in Zeitgeist Datahub: Incomplete 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 ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events
Nautilus can tell us when a file is being renamed or moved from whithin nautilus. On Sun, Nov 7, 2010 at 7:27 PM, S. Sickert wrote: > Reading through all the comments - it seems to me that there are two > problems to tackle: > > 1) Determine which files are interesting for the user - this can be done > with the Taskview API > > 2) Keep track of these files - this must be done with inotify, as there > are many programs which don't notify anybody about file changes. (e.g > mv, batch-renamer, ...). There is still the problem of "offline" (we are > not running) changes, but I don't see any solution except scanning the > whole filesystems, which is also very suboptimal. > We can keep track of files as long as applications tell us if they are moving them around. Currently only nautilus and commandline can undertake such activities. But how many normal users use commandline. There is NO WAY we will use inotify so the best solution right now is to get the info: 1) moving and copying over nautilus -> taskview -> zeitgeist 2) renaming shoul be done over nautilus -> zeitgeist > > Of course there is a bit redundancy between 1 and 2 (e.g. move already > known files with nautilus) and must be filtered out. > > -- > Monitoring Create/Move/Copy Files events > https://bugs.launchpad.net/bugs/602211 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Zeitgeist Framework: Confirmed > Status in Zeitgeist Datahub: Incomplete > > 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 > > > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/zeitgeist/+bug/602211/+subscribe > -- This is me doing some advertisement for my blog http://seilo.geekyogre.com -- 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 Zeitgeist Framework: Confirmed Status in Zeitgeist Datahub: Incomplete 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 ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
Re: [Zeitgeist] [Bug 602211] Re: Monitoring Create/Move/Copy Files events
That is why i proposed solution 2 which in my opinion covers everything :) On Sun, Nov 7, 2010 at 2:36 PM, Siegfried Gevatter wrote: > 1) Modify the uris in the uris table > -1, events are immutable by definition, they aren't supposed to change > > -- > Monitoring Create/Move/Copy Files events > https://bugs.launchpad.net/bugs/602211 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in Zeitgeist Framework: Confirmed > Status in Zeitgeist Datahub: Incomplete > > 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 > > > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/zeitgeist/+bug/602211/+subscribe > -- This is me doing some advertisement for my blog http://seilo.geekyogre.com -- 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 Zeitgeist Framework: Confirmed Status in Zeitgeist Datahub: Incomplete 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 ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
