Mapping to toodledo tags

Hi,

I'm trialling the product to see if it can achieve the utopia of aligning outlook messages with toodledo and so far I'm pretty impressed.

One thing that I cannot figure out is the relationship between Ceptara and the tags in Toodledo.  In toodledo, I use tags to identify a specific client (regardless of the project folder/code feature I can see in ceptara).  Reason for this is so I can group on tag in toodledo, so that I can see everything related to key clients

Therefore, my question is this - what is the field that is mapped from outlook or ceptara to toodledo?  Sometimes it appears to be the folder name - others not.  Is there a way of forcing the tag name?

Thanks in advance - if this is fixable, you have a very neat product here!!

 

Paul

Tags And Categories

Paul -

Thanks for your question.

The tag field on ToodleDo is mapped to the Outlook Categories field on a task.  The Organizer tool places the project name in the Categories field in Outlook and then when sync'd to ToodleDo also shows the project name in the tag field.  Additionally, if any tags (that are not folders or contexts) are recorded in ToodleDo, they should also show up on Outlook in the Categories field.

Hopefully that helps to make sense out of what you're seeing.

Tags and projects

Hi Chris,

Thanks for the reply.  On reviewing, I wondered if the same were true.

This leads to another question then (sorry).  I used to use the tag feature in toodledoo to organise all tasks for a key client.  To follow this same methodology in Ceptara, I would need to create a project to represent each key client - which is not a problem.  Therefore my question is this; can you have sub-projects in Ceptara, which are "real projects" and keep the project/category (outlook)/tag (toodledo) field for key client name?

I hope this makes sense?!

Projects And Categories

Paul -

I think I would do this:

  1. Let projects be projects, i.e. a body of work with a specific scope and a set of deliverables.
  2. Establish a coding scheme so all projects that go to a specific client are in the same coding block, e.g. Client A has projects 1, 2 and 3, therefore my projects would be "000401 - Project 1", "000402 - Project 2", and "000403 - Project 3".  In that way all projects for a specific client would be in the 400 block of my projects.
  3. Optional: if I wanted the client's name to show up on each of my objects, I would set up a Category for each client, e.g. "Client A", in my Master Category list, and then assign each task to a Project and a Category (i.e. Client) and potentially a Focus (if needed).  In this way, the Categories field will sync with ToodleDo and you would have your client name in the Tag field.  As well as know which project the task belonged to.

In the future we will have a more robust folder hierarchy so you can group projects into folders.  And we're looking at adding 'Workspaces' so that projects and groups of projects can be viewed in context of a workspace (e.g. "My Company", "Personal", "My Voluteer Work", etc.).  It maps to our 'Community' concept as described in the Personal Excellence Workshop.