Thanks, Helena. I really need to do the same as my task hierarch is enormous (which is part of the reason I don't use the mobile version). I have another question: what happens if you move the parent in the original file. If MLO is using the Task Id, it must also move the parent in the archive file. ie: Archive is almost like Synch - except it is one way and it is moving stuff rather than copying. Richard
On Wednesday, 21 August 2013 20:26:35 UTC+1, Helena wrote: > I make extensive use of the archive function, to keep my current > database reasonably lean, especially for usage on mobile devices. This > situation is handled as your option 2. MLO use the Task ID for > identification of which task is which, and where a new task should be but > in the hierarchy. The Task ID is kept the same when a task is moved or > copied to an archive (i.e., it is really the same task, not only a copy). > During the archiving operation, all in the archive already existing parents > to the tasks that are archived are updated. Other tasks that may exist in > both files remain unaffected. > > Keeping of the Task ID during archiving also means that internal links > that you may have placed in the notes field still work if both tasks (the > one with the link and the one with the referrer) are copied/moved to an > archive, which I find very useful. > > Helena > > On 13-08-21 14:54, Richard Collings wrote: > > Has anybody worked out how archiving handles the situation where you > change the name of a parent after some of its tasks have been archived. > > > > Ie if you have a situation like this > > > > Parent Task > > Child Task 1 > > Child Task 2 > > Child Task 3 > > > > And you then complete Child Task 1 which then gets archived (with its > parent). > > > > And then you change the name of the parent so you now have: > > > > Parent Task with new name > > Child Task 2 > > Child Task 3 > > > > And then at some subsequent point you mark Child Task 2 done and it gets > archived. > > > > What does MLO do: > > 1. Archive Child Task 2 under Parent Task and not change the parent > tasks name > > 2. Archive Child Task 2 under Parent Task and change its name to > reflect the new name > > 3. Create a new parent with a new name and archive Child Task 2 > under the new name > > > > I think my preferred option would be 2 (because it is still the same > parent and I would want the archive to track what was happening my live > database) but it would be interesting to know. > > > > Richard > > > > > -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mylifeorganized. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/61a77efa-57c7-4204-8473-9f2a969935e5%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
