TiddlyWiki for project management: How to deal with Tasks from different projects requiring the same title?

[Ed Edson]

Hello!

I hope this is an appropriate question for this forum. I am starting to use TiddlyWiki as a simple project management tool and am looking for some advice from someone with more experience than me.

I am adding a Tiddler for each new project, and then adding tasks tagged with the name of the project they belong to. I generate tasks lists for each project in a way similar to this. I also have a table of contents to aid navigation.

What is a good way to deal with projects that contain tasks with the same name?

For example, many of my projects involve doing a bit of research first, so I will create a task called "Research". The problem is that TiddlyWiki requires unique titles. In this case I cannot reuse the "Research" Tiddler as the content will be different for each project.

Does anyone have a good system that avoids this problem?

Thanks for your help!

[TonyM]

Ed,

The easiest way would be to set up a new tiddler button that adds the number at the end research 1, research 2 etc...

However

When faced with this I create a new tiddler button, that names new tiddlers with a project suffix eg "projectshortname new tiddler" or "projectshortname new task" which I would then name to "projectshortname research" however I do not have much of a problem coming up with unique names such as "Research CCS for forms", and if I wanted to collect research tiddlers together I may tag it research, even make a new tiddler button to create research tiddler tasks.

But even with the above I tend to avoid tags for defining recurring items, I often then store a value in a field. for example project name is stored in a field, and I could have a task-type field = research.

Further, stored in fields I have domain (Work Personal etc...), the aforementioned project name, client name (if applicable), contact name (person if applicable) - I call this the context.

When I create a new tiddler I do so from any tiddler already with a context, and the new tiddler is created using the current context.

Eg in a project click to create a domain/project name task, in a client click to create a clientname task

The truth is you not only need unique titles to confidently find something again but it is a good design strategy. If you want you could use a data tiddler for each project and store these similarly named tasks in a different way.

Regards

Tony

[PMario]

Hi Ed,

You could have a closer look to existing editions.

 - https://tid.li/tw5/tdn.html  ... ToDo Now

 - https://reidgould.github.io/tiddlywiki-dropboard/ ... Dropboard

have fun!

mario

[PMario]

Hi Ed,

On Saturday, May 25, 2019 at 2:30:16 AM UTC+2, Ed Edson wrote:

...

I hope this is an appropriate question for this forum.

:) it is!

 

What is a good way to deal with projects that contain tasks with the same name?

For example, many of my projects involve doing a bit of research first, so I will create a task called "Research". The problem is that TiddlyWiki requires unique titles. In this case I cannot reuse the "Research" Tiddler as the content will be different for each project.

Does anyone have a good system that avoids this problem?

TW allows you to use very powerful filters.

So 1 possibility (just an idea) would be to add a prefix. eg: pr/01/Research

We call this format with / ... "namespace". ... So pr/01/Research is a tiddler in the namespace: pr/01/

If you create a tiddler title: pr/01/Research

Add a field named: caption value: Research

If you create a tiddler title: pr/02/Research

Add a field named: caption value: Research

Create a new tiddler title: pr/01

caption: <you name it>

content for pr/01

<<list-links filter:"[prefix[pr/01/]]">>

<<list-links filter:"[prefix<currentTiddler>]-[all[current]]">>


<$macrocall $name=tree prefix="pr/"/>

 - The first line creates a list of all tiddlers prefixed with pr/01/ where the name pr/01 is hardcoded.

 - The second line creates the same list, but uses the tiddler titles as prefix value.

 - The third macro call, calls the tree macro, which is part of the core. ... Which gives a nice overview basically for free.

As mentioned. This is only 1 possibility to deal with unique tiddler titles. ... We use the caption field here.

Also have a closer look at: TaskManagementDraggable.

have fun!

mario

PS: more info about fields.

[Ed Edson]

Thank you for your reply.

Say I have a project tiddler called ProjName and a task tiddler called ProjName/Research.

I tried using the removeprefix operator to list tasks in the project tiddler without displaying their prefix. This way I could avoid adding a caption field every time I add a new task.

At first I tried:

<$list filter="[tag[task]removeprefix{!!title}removeprefix[/]]">
<div>
<$checkbox tag="done"> ~~<$link to={{!!title}}><$view field="title"/></$link>~~</$checkbox>
</div>
</$list>

This displays the name I want but obviously doesn't link to the original tiddler title, it links to the title with the prefix removed.

What is the correct way to use removeprefix in this context?

Thanks again for your help.

[Mark S.]

The way I deal with this problem is with "caption" and "description" fields. Any output macros you use can just use the "caption" field. So if your have Project1/Research and Project2/Research, they can both have the caption "Research". In your outputs and selection lists, you use the caption field. The TOC macros, which are often the beginner's go-to tools, already use the caption field when available.

Good luck!