View Single Post
Quote:
Originally Posted by Jgparker View Post

1. an email arrives requesting whether i would be willing to be a peer reviewer for a manuscript submitted to the Journal of Big Ideas. I am. I bump the email into the inbox for processing later. It's is due on a specific date and there is really no need to for sub actions. My annual report considers this Service/National. I'm inclined to have a folder called Service with a subfolder called National and a further subfolder called Peer Reviews. At a glance i could see the peer reviews i have outstanding and at the end of the year i'd have a record of all the reviews i did.

But I cannot file this review in Service/National/Peer Reviews because the inbox will only add actions to projects. Seems silly to make a single item a project (or is it). How could I handle this?
It is no accident that the icon for the single action list type is a shoe box or file box. Make one for each folder to hold all the miscellaneous things that aren't projects.
Quote:
2. Another type of Service/National I might do is organize a national meeting on Grasshopper politics. My annual report considers this Administrative national service. Should I make another Service/National subfolder called Administrative and place a project in it called Grasshopper Conference? This makes sense because there are many actions such as selecting deciding the theme and keynote speakers. Many of these actions have sub actions, such as corresponding with, sending contracts to, and scheduling Speaker A, Speaker B, and Speaker C. If I make each speaker a project, they can't be nested within the project of Selecting a Keynote. I could just define each speaker as a project and skip the Selecting a Keynote superodinate project, but single actions can't appear alongside projects so the theme action would have to be embedded somewhere. or I could make each speaker an action and each element of the negotiation with the speaker a subsection, but then I could't put a speaker on Hold. how to handle this?
Sometimes you have to decide which aspect of the representation is most important. If you need to be able to use all of the project tools, such as reviewing or putting things on hold, you need to go with projects. In other cases, the sequencing may be more important, in which case you make action groups in a big project or single action list container. You could also take a hybrid approach, using placeholders in one project to remind you of actions in other projects. You might have the overall project with a section listing the speakers you want to recruit, with separate projects for the tasks involved in actually recruiting each one.
Quote:
3. I'm teaching a course on the History of the Toaster. This is Teaching/Courses in my annual report. I need a textbook, I have to make syllabus that has several related actions, each week I have to collect a written assignment, and I have to set up a field trip to the local toaster factory that has several steps such as calling the owner, arranging transportation, taking Attendance, and submitting for reimbursement. If the field trip doesn't happen I want to be able to mark it as dropped. Plus, I meet each week with the teaching assistant and I always have a bunch of tasks for him to do before next weeks class. And if i receive an email from a specific student asking about her grade I want to be able to remember to respond to it and have a record that I did. how could I set this up?
Sounds like a folder for the course, with projects for the various chunks that need independence, and maybe a single action list or two to keep the assorted random bits, correspondence, etc.