Tags 🏷️ - Ideas for a new tag system in Freeplane

[euu2021]

As a follow up of #1640 (comment), let's discuss ideas for a new tag system in Freeplane.

[i-plasm]

Hi all! I am happy to hear about the interest in a tag system, so useful! I drew how I think the layout in the node could be organized, in order to not waste mapview space real state, and to be visually pleasing:

[dpolivaev]

Why 30%? Maybe just configurable min/max width for the icon area?

[euu2021]

I will mention two points: tags hierarchy and the visual aspect of the tag. I will put each point on a separate comment.

Tags hierarchy (aka nested tags)
There are many knowledge management system that are based on tags, and a key factor to make it work is tag hierarchy. So, I think that this would make the tag system more capable of adapting to different users need.

The basic idea of the tag hierarchy is that, I can work with a parent tag if I want to reach multiple child tags. For example, if the user wants to filter foods nodes, he chooses to filter by the tag foods, and it will find all the nodes that have foods tags, like fruit tag and vegetable tag.

I use a lot the tag system in the Anki software. Anki relies heavily on tags, to organize knowledge that is divided in small notes (similar to nodes in FP). So, they developed a robust hierarchical tag system. It works like this:

• The syntax

The hierarchy is created by using double colons "::". For example:
objects::foods::fruits
objects::foods::vegetables

Note that "foods" and "objects" are also tags, and not just a container for other tags. So, I can assign the tag "objects" for a node.

This makes it easy for the user to create tags hierarchies on the fly. I show in this video a situation where I want to create a new tag "water", but I don't even have the category beverage, so I create it on the fly:

7Pt9H9gubx.mp4

Also, there must be no spaces inside a tag, so the multiple words tags can be like this (the user can choose the default, so the software automatically convert the new entered tags):
passion_fruit
passionFruit
passion-fruit

• Searching and adding tags
  Tagging on the fly is easy, because if I type a part of a word the results show all the tags that have this text in the tag chain. For example, searching for "civ" gives me results in any part of the tag chain:
  

In FP, the Command Search already has this transversal search, so, I think the tag operation could be well integrated into the Command Search or have a similar dedicated "action bar".

• The management
  In Anki, the user can rearrange the tags as an Outliner, by draggin and dropping. It looks like this (just an usial Outliner):
  

Perhaps, FP can do it in a mindmap way: like the current style manager, a tag manager would be a window where a mindmap is generated from the tag hierarchy; so the user can drag and drop nodes around, to easily make changes in the hierarchy, rename tags etc. This would be the "tag manager" (more about it in the comment about formatting).

For a video overview about how tags work in Anki: https://www.youtube.com/watch?v=Y13Y7tcJQdY

[euu2021]

The visual aspect
Currently, the node attributes are used as tags, but it is not rich on the visual aspect. I mean, a rich visual representation that allows the user to easily visually identify the tags in nodes.

• Positioning:

Here, one idea is having a field below the node, outside the node, where the tags fit and stack. For example:

Or, maybe, below, but inside the node, so it's more clear that those tags belong to that node, and not to the sibling node below it:

Another option is what i-plasm suggested: split the area that, now, is reserved for Icons. So, the half bottom would be for tags, and half top for icons. Notice that, currently, this space is not used:

So, the tags could fit there, as i-plasm mentioned.

• Colors and formatting:

Perhaps, an option is using the "tag manager", that I mentioned on the other comment, to control visual aspects of the tag. For example, each tag is represented by a node in the tag manager, so changing the background color of that node would change the tag background color and other properties.

Now, those last couple of days I learned that working with text in an SVG has lots of complications. So, I wonder if it's not a better, more flexible choice to simply display the tags as html text.

[euu2021]

Looking at those 3 options, I like the second one (below and inside).

• below: because it seems to fit better the horizontal nature of the tags. Putting it at the side, like the icons, would probably create a lot of real state blank spaces. Imagine a long tag trying to fit on the side.
• inside: because it is more visually intuitive that those colorful rectangles are bringing an information about that node. It feels easier to understand, on my eyes.

[euu2021]

I've being experimenting with svg tags, and I changed my mind about this topic. Now, I prefer the third option (tags on the left), because:

If the node has a small amount of text in the node core, then the tag at the bottom would unnecessarily create a second line in the node. If the tag is on the left, then the node stays as one line:

If the amount of text in the node core is a bit longer, then the situation is equal, no matter if the tags are at the left or at the bottom, and a second line needs to be created, anyway:

So, looking at my map, I see that a good percentage of the nodes are short, so I would end up saving more space if the tags are at the left, and not at the bottom.

[euu2021]

Another thing that I noticed is that the tags will be very useful to me, because they will cover a current blindspot that I have when using Freeplane:

A situation that I face frequently is that I need to create a symbology specific for one branch (for example, for a project, or even a part of a project). The current solution is to use styles or icons. But, as the simbology is very limited for a specific situation, I need to create a key for that branch, explaining the simbology. This makes the use of the map quite difficult, because I need to keep consulting the key, in order to understand the branch simbology. The tags solve this problem, because it also has a label with text, making explicit the meaning. Reading the map will become easier in that kind of situation.

And now I notice that JJSlot already mentioned a similar idea in the other post:

At times only text will do for recognition. If we want to visibly identify some nodes as relating to “IA Conf 2019” for example, we need a bespoke icon, not a generic jackrabbit or bullfrog or standard symbol.

[dpolivaev]

Preview 1.12.1 alpha 01

• Edit->Node properties->Edit tags (alt+F8)
• The font is configured in the Tags style node
• The colors are calculated automatically and depend on the content
• Tags-related filters
• Tags-related API
• Control+space in the tag editor to fill in known tags
• Smart tag sorting: abc9 < abc10 < abc10d

[euu2021]

This is very good. Thanks!

The vertical stacking of tags works well. For my map, it's the most space efficient layout.

Now, what I'm missing for a basic usage is a way to easily add the tags, with autocomplete suggestions. Is it possible to have something similar to the Icons Table (Insert->Icons->Icon from table…)?

The Icons Table have an autocomplete feature, that works well for the Icons. A difference in relation to the icons is that the user may want to create a new tag if he doesn't find the desired tag in the results.

[dpolivaev]

Control+space in the tag editor should activate autocomplete. Doesn't it?

[dpolivaev]

By the way, tag ordering also used by the filter is smart: abc9 < abc10 < abc10d

[euu2021]

Oh, I see. Thanks

[euu2021]

The colors are calculated automatically and depend on the content

I think that letting the user change the color is relevant.

I created a tag Important, and it received a green tone. But, I for sure would prefer that it was a Red color, to represent urgency and call my attention.

Then I created a tag Urgent and... it also received a green tone 🤣🤣🤣

I tried to change the colors using Refletion, but it did not work.

[dpolivaev]

Why do you need to modify the font color and the border color too?

[euu2021]

Why do you need to modify the font color and the border color too?

If the font color and the border color are automatically recalculated to combine with the background, then it's not essential. Otherwise, it can lead to poor contrast, so the user needs to adjust them manually.

[dpolivaev]

Currently, the border color and the text color are the same, black or white, depending on the background color brightness.

[euu2021]

Currently, the border color and the text color are the same, black or white, depending on the background color brightness.

I see. My point is that, when the user changes the background color, the font and border colors need to be recalculated, to assure readability.

[euu2021]

The option to change the tag color is working perfectly on 1.12.1_02. Thanks!

[Illegit]

Nice tool, but I ask for thinking to activate some topics:

1. to have the possibility to make visible/not visible all of tags of the node branch in the node itself : I think a command that can be activated with a short cut (not just a flag). This so we can now which are the flags in the branch without
2. to have the possibility to structure&sort the list of created flags (date of last use, ....)
3. because of the bug I got (see issue 1780), I cannot check if the filter is working for the tags, is it? If not, please think about it.
   Thanks

[Illegit]

Topic 1.:

to have the possibility to make visible/not visible all of tags of the node branch in the node itself : I think a command that can be activated with a short cut (not just a flag). This so we can now which are the flags in the branch without

During the navigation you have nodes with closed branches, if you have some important tags you do not know, you need to open the branches and search for them: this is what I want to avoid (waste of searching for long). So actually I use icons as tags , and to investigate the branch icons I apply the FP command "show icons hierarchically" on the node (logic is on/off) because I do not want in normal condition to see all of those icons in the node, but in that phase of the navigation yes...let me say it is like a temp signpost.

Topic 2.:

to have the possibility to structure&sort the list of created flags (date of last use, ....)

in fact just sorting on recent changes is the tip of the iceberg, the current primordial list of tags is using just the alphabetical sorting (good point) that is in any case long to select the correct one (sometimes jumping up and down in the list) but I imagine and need something much wider: eg to open the tree of tags because the meaning of tags is related with the many different uses they can be applied (is it a mind map? is it mind map mode? or?). For now this is my use of icons as tags: use the padded menu and choose with 1 click which tag icon I need see the image

I cannot say anything for topic 3.

Thanks for approaching deeper it.

[dpolivaev]

It looks like you want to have user-specific categories for tags so that you can quickly add tags based on their categories. Is it correct? Does somebody else need it?

[euu2021]

It looks like you want to have user-specific categories for tags so that you can quickly add tags based on their categories. Is it correct? Does somebody else need it?

Yes, I need. As I mentioned above (#1652 (comment)), my tags will usually be specific to a certain branch, so it will be useful to group them together.

[dpolivaev]

@euu2021 Your request is quite different because you want the categories to be map-specific or even branch-specific, and I was suggesting having one definition per user configuration. And your request seem to be quite complicated, I am afraid that nobody would understand how it works if I implement it.

[euu2021]

Your request is quite different because you want the categories to be map-specific or even branch-specific, and I was suggesting having one definition per user configuration. And your request seem to be quite complicated, I am afraid that nobody would understand how it works if I implement it.

My request is more simple than that. I just want to be able to group the tags, so I can see them in groups, instead of one big list of tags. I think that it's the same request as Illegit.

And having one definition per user configuration is perfect to me, because I use just one map.

[Illegit]

About topic 3: I just saw the filter is already available.

[Illegit]

It looks like you want to have user-specific categories for tags so that you can quickly add tags based on their categories. Is it correct? Does somebody else need it?

Yes, it is what I'd like to.

[Illegit]

Nice. the FP 1.12.1_02 with the tags (color and so on).
I add topic 4: how to copy and paste tags from one node to another node or more nodes?
Thanks

[macmarrum]

It's great to see the tags functionality coming to Freeplane ❤️

I've been using tags in various wikis, mainly in TiddlyWiki.
I like how TiddlyWiki's Tag Manager works (https://tiddlywiki.com/#%24%3A%2FTagManager):

• it allows to change a tag's background color (and icon)
• it's decoupled from the Tag Chooser
• it acts as a search interface

TiddlyWiki's Tag Chooser has a filter that helps to narrow down the list of tags to choose from; it's missing auto-completion, though.

There is no built-in groupping functionality for tags in TiddlyWiki. I use a naming convention to group similar tags by a prefix, i.e. I have tags starting with +, =, %, @, !, etc. This helps to some extent. I think that Tag Categories might be a better approach.

I have around 300 tags in my TiddlyWiki and I imagine I might have hundreds of tags in Freeplane, therefore I think Auto-Completion and Filter functionalities are essential to have a good workflow.

For adding or removing tags to/from nodes and for search/filter nodes by tags in Freeplane, I'd like to have the option of not using the mouse, i.e. a keyboard-only workflow.

The way I imagine it for Freeplane is to have

• a Tag Chooser that allows to add/remove tags from a node/nodes, with auto-complete and filter (or 2 filters - category then tag) -- something like Edit Tags in 1.12.1_alpha1
• a Tag Manager that allows to change tag's color -- something like Edit Tags in in 1.12.1_alpha2;

Maybe in the future Tag Manager could also act as a Search/Filter interface for nodes containing selected tag(s), maybe it could allow to show/hide certain tags / categories or to rename existing tags.

[Illegit]

Hi, may somebody explain how to use the following commands?

Thanks

[Illegit]

I understood these are not reòlated with new tag system.

[dpolivaev]

Update: in the latest preview I did many improvements to the tag editor. Now it supports copy, cut and, and paste, drag and drop, starts editing when you type. On a separate branch I do some experiments with Tag Category Editor, but I need to spend more work until it becomes useful.

[euu2021]

Now it supports copy, cut and, and paste, drag and drop

This is nice to make bulk operations and distribute tags. Now, it would be even faster if I could do the drag and drop of tags directly in the node, without having to open the tag editor of each node:

This operation of copying or moving tags between close nodes is relevant in daily like.

[euu2021]

Now, it would be even faster if I could do the drag and drop of tags directly in the node, without having to open the tag editor of each node:

I will create a feature request

[Illegit]

euu2021, I'd like it.

[dpolivaev]

Sometimes you wish too much

[Illegit]

OK, got it, ... ... eventually have a look if you can add the title to the each single editor.
Dimitry I think with FP you are too helpful, anyway thank you for it.

[dpolivaev]

Update: Try preview 1.12.1_04 with tag category editor Tools->Edit tag categories.
In this preview, the tag categories are used in the menu "Insert" of the TagEditor. But would be easy to add them also to the Freeplane icon toolbar or to the Freeplane insert menu.

I can also add to TagEditor menu or to Tag Category Editor menu new actions that insert selected tags to currently selected nodes. But I do not understand well enough how they should work and which submenu and action names I could use. Your ideas and suggestions about the logic and the names could help.

[Illegit]

Nice!
It is really effective. Copy Cut Paste + Tag editor with the title + list of tags.
Now I have to utilize them for a while and enjoy this new tool. Thank you.

[dpolivaev]

I want to explain how tag categories work and where they are saved.

Look at the screenshot

Tags "Apple", Banana, Blackberry, and Basketball are attached to the node.
The categories are saved in a separate file in the user directory.
When the node tag editor is opened, the information is combined. Therefore tag "Basketball" is displayed twice in the corresponding categories.

If new categorized tag is added, not only the tag is saved at the node but the tag category file is also updated.
You can add new tags and categories in the tag editor using the double colon syntax, but you remove tags from categories or rename categories only in the tag category editor.

Preview 1.12.1_06

[macmarrum]

Thanks for the explanation.

To take it further, this is my node

and this is its XML in .mm

<node TEXT="test-tags-pre6.xii" FOLDED="false" ID="ID_452131666" STYLE="oval" TAGS="apricot&#xa;Ford">

→ food::fruit:: was discarded in the XML.

As I mentioned before, I'd like to be able to search for the node also by its tag category/subcategory, not only by the tag's last segment. The proposed approach (where only the last segment of the tag is actually saved with the node) won't allow this.

Also, if I share the mind map with someone, they won't get my intended tag food::fruit::apricot, but only apricot.

Should the functionality remain like that, I think I'll have little use for the Tag Category system.

[dpolivaev]

I have had an experience with polite messages written by ChatGPT and I have an impression that they do not always look real. So, now let me present you unfiltered Dimitry. I hope you appreciate it.

I’ve spent a significant part of my vacation working on the tag category system, only to learn that you find little use for it. I’m sorry to hear that. It appears I developed the system based on assumptions that seemed logical to me, without sufficient user use cases and examples. As we're still in the alpha phase, adjustments are certainly possible. However, for that, I need to better understand your specific needs than I currently do.

The current implementation separates the tags from their classifications, which I see as having multiple advantages. It keeps the classification flexible at any time. The underlying assumption is that the classification system is broad and not limited to a single map. Attaching it to a map would be straightforward, but would lead to each map having its own classification, which could be confusing.

I typically don't share my mind maps with other users, but if sharing is essential for you, remember the classification is saved separately and can be shared as a file with other users. Also, if you want to filter the map using tag categories, you can use a filter called "Categorized Tag" "Contains" that can combine the tags and the categories.

There are already many robust features in the system, with potential for further improvements. I’m open to exploring these possibilities. I need encouragement and appreciation, not just comments that the work isn't useful enough. If you provide your use cases and we both keep our minds open, we can find a solution capable of much more than we can even imagine otherwise.

[macmarrum]

Thanks, Dimitry.

I am looking forward to incorporating tags into my daily workflow.

I appreciate your work. At the same time, it doesn't mean that I have use for every feature you added to Freeplane. There are features that I use, there are some that I have little use for. And this is the case for the proposed Tag Category system. Having said that, I can imagine that someone can find it useful in its proposed form.

I also hope that the opinion of a single user won't dicurange you from doing what you like. I assume it brings you joy to make Freeplane better, as it brings me joy to discuss and try out the new features.

[euu2021]

My time is short, currently, so I'm not able to test and give feedback frequently. But, I recognize that the tag system improved a lot comparing with the first versions. It seems that the important features are already implemented. Just to give an idea of how relevant it is, take a look at this thread in the Joplin (which is one of the biggest note-taking apps) forum, where people are begging for years to have tags categorization: laurent22/joplin#375

The current implementation separates the tags from their classifications, which I see as having multiple advantages. It keeps the classification flexible at any time. The underlying assumption is that the classification system is broad and not limited to a single map. Attaching it to a map would be straightforward, but would lead to each map having its own classification, which could be confusing.

It still not clear to me the advantage of separating the tag from their classifications. Maybe, the solution is, again, to threat it like the styles: at first, it works only for the map; but, if the user wants, he can create a template with the classifications.

Notice that the user may not be interested in using the classification on all maps. So, the most flexible solution is giving the option: if you want to use the global classification, follow the template.

And, being able to easily share the map with the classifications sounds to be a very relevant feature, to my eyes. In Anki, for example, when the user shares his deck of cards, each card carries the full tag (tag and categories), and this is a key feature when sharing the decks.

I'd like to be able to search for the node also by its tag category/subcategory, not only by the tag's last segment. The proposed approach (where only the last segment of the tag is actually saved with the node) won't allow this.

Just to make clear: does the "Categorized Tag" "Contains" filter solves the problem, or do you need something different?

[macmarrum]

I'd like to be able to search for the node also by its tag category/subcategory, not only by the tag's last segment. The proposed approach (where only the last segment of the tag is actually saved with the node) won't allow this.
Just to make clear: does the "Categorized Tag" "Contains" filter solves the problem, or do you need something different?

I'm afraid it does not solve the problem.

1. I need to be able to use the scripting API to search, e.g.

node.find {
    def tagList = it.tags.strings
    if (tagList)
        tagList.any { it.startsWith('food::') }
}

BTW, I need to think about different API names – I'll propose something soon

2. and I need the search results to reflect what I entered in the mind map, i.e.

Given Node A with Tag weekday::Wednesday and Node B with Tag name::Wednesday
When I search for weekday::Wednesday
Then I get only Node A as the result

In the current implementation of "Categorized Tag" "Contains" filter, I get both Node A and Node B

[dpolivaev]

For me, the decisions to separate categories from tags attached to individual nodes, to save them in a configuration file versus directly within the map are distinct questions. There are no right or wrong answers; it depends on the use case. I'm in a difficult situation because I don't know your use cases, and I don't have any personal uses for the tags. I rely on the information you provide, and, in my view, you never share enough. Perhaps you don't realize how crucial it is to have a deep and empathetic understanding of your needs.

To be clear, I live not because I enjoy life, and I code not because I enjoy coding. Rather, I code because I try to make sense of the burdens of my existence in this dangerous, painful, and chaotic world. Therefore, I need your feedback to determine if what I do is still right and helpful.

Back to the point.

Saving categories at nodes individually seems the same as allowing double colons in tag names. You could perfectly have a tag named food::fruit::Banana. In this scenario, Freeplane could also offer an option to keep or remove the part of the tag before the last :: from the view. You could always search for them easily, and Freeplane could even calculate the list of categories by accumulating information from all nodes in the map. However, you would not be able to change the categories as a whole, rename them consistently, or edit them by drag and drop. You would only have a "tag editor," not a "tag category editor."

Given Node A with Tag weekday::Wednesday and Node B with Tag name::Wednesday
When I search for weekday::Wednesday
Then I get only Node A as the result

Yes, Freeplane currently has the opposite logic: the tags are compared by value, and if you have the tag Wednesday as part of categories "weekday" and "name," when you open the tag editor, you should see it listed under both categories. It's still the same tag attached to both categories. Otherwise, I don't see why you might need categories at all: you could just have tags with some internal structure. Maybe I don't understand your intention well enough, but I can't grasp it until you explain further.

Saving the tag-category tree as part of a mind map would also be easy to implement. We should discuss both questions independently.

I could also make configurable which separator is used for the tag categories and if the category tree is saved or not.

Regards.

[macmarrum]

To be clear, I live not because I enjoy life, and I code not because I enjoy coding. Rather, I code because I try to make sense of the burdens of my existence in this dangerous, painful, and chaotic world. Therefore, I need your feedback to determine if what I do is still right and helpful.

Thanks for sharing. I think it's helpful and we're getting better at understanding each other.

if you have the tag Wednesday as part of categories "weekday" and "name," when you open the tag editor, you should see it listed under both categories. It's still the same tag attached to both categories. Otherwise, I don't see why you might need categories at all: you could just have tags with some internal structure. Maybe I don't understand your intention well enough, but I can't grasp it until you explain further.

In TiddlyWiki I group tags using a prefix approach. I need to group tags because I have a lot of them, and when I want to apply a tag to a tiddler (node), I need to find it in the list. So when I start my search with a prefix (category) of a tag, it narrows down the list of tags considerably, making it easier to use my tags.

Please see also

• Tags 🏷️ - Ideas for a new tag system in Freeplane #1652 (comment)
• Tags 🏷️ - Ideas for a new tag system in Freeplane #1652 (comment)

In TiddlyWiki each of my categorized-by-prefix tags is unique, i.e. %Wednesday has a different meaning compared to ^Wednesday.

I'm in a difficult situation because I don't know your use cases, and I don't have any personal uses for the tags. I rely on the information you provide, and, in my view, you never share enough. Perhaps you don't realize how crucial it is to have a deep and empathetic understanding of your needs.

Please feel free to ask me questions if you need more information to understand my needs.

You could perfectly have a tag named food::fruit::Banana. In this scenario, Freeplane could also offer an option to keep or remove the part of the tag before the last :: from the view.

Sounds good to me.

However, you would not be able to change the categories as a whole, rename them consistently, or edit them by drag and drop. You would only have a "tag editor," not a "tag category editor."

It's fine with me.
If I want to rename a tag*, I can open .mm in a text editor and do a search and replace of a categorized tag name, like I do with style names today.

[macmarrum]

(*) If I want to rename a tag or its category

[Illegit]

However,` you would not be able to change the categories as a whole, rename them consistently, or edit them by drag and drop. You would only have a "tag editor," not a "tag category editor."

It's fine with me.
If I want to rename a tag*, I can open .mm in a text editor and do a search and replace of a categorized tag name, like I do with style names today.

Hi Sirs, normally I do not want enter into specifics about sw because I read often you have better ideas than mine, but this time I think to provide you a comment with reference to the above topic:
this for a normal user could be a problem, my personal use is not to have time to go in the text editor but to work on the fly using keyboard and mouse. I found some trouble managing the categories with the current category editor (I expect that to be solved with a future fine-tuning) but it is useful even if we cannot copy from it to the tag editor of a single node. The tag category structure is, for me, a user need as described by Dimitry,. .I think it deserves a deeper analysis because we observe some different ways of using the tags:

1. using some scripts and sw to manage them - skilled programmer
2. using mouse & keyboard navigating the map - normal user
3. others?

Macmarrum and DImitry I think that probably I have misunderstood something in your debating, may you develop it in a more structured way identifying the different user roles needs and explaining pros and cons for them about the main solutions you suggest. At the moment, as normal user, I prefer the Dimitry solution because I do not understand how to manage on the fly the full set of tags and categories.... in the other way.

I follow all of you in this thread.

PS: I proposed even to develop still 2 topics: 1) the possibility to see the tags in the branch in the node parent, 2) to have the possibility of showing or hiding them at need in the single node
I do not know if they are possible but they are needs because normally I place tags in branches with tens or hundreds of nodes, but only some get them... anyway this could an eventual future matter.

Thanks for your patience

[macmarrum]

@Illegit thanks for you post.

I found some trouble managing the categories with the current category editor (I expect that to be solved with a future fine-tuning)

Could you please elaborate about what the trouble is?

The tag category structure is, for me, a user need as described by Dimitry

Do you mean by it that you need functionality for renaming categories of existing tags and moving tags between categories?

Let's say you have the following entries in Tag Category Editor

• weekday
  • Wednesday
• name
  • Wednesday
• off-day
  • Saturday
  • Sunday

1. Do you need to be able to move Wednesday from weekday to off-day?
2. Do you need to be able to rename off-day to e.g. holiday?

I am asking because, as far as I can tell, this wil be the only difference if full tags like weekday::Wednesday are saved with their nodes, not only the last segment like Wednesday → "you would not be able to change the categories as a whole, rename them consistently, or edit them by drag and drop"

In any case, I am fine with keeping the current implementation of Tag Category Editor with only the last segment saved with nodes. I've managed with tag prefixes in TiddlyWiki and I can continue with the same aproach in Freeplane.

[macmarrum]

to have the possibility of showing or hiding them at need in the single node

I can think of a script that can show or hide combined branch tags in a node

import groovy.json.JsonGenerator
import groovy.json.JsonSlurper

def originalTagsJson = node['originalTags'].text
if (originalTagsJson) {
    hideBranchTags(node, originalTagsJson)
} else {
    showBranchTags(node)
}

def showBranchTags(node) {
    def g = new JsonGenerator.Options().disableUnicodeEscaping().build()
    def tags = g.toJson(node.tags.strings)
    node['originalTags'] = tags
    def branchTags = new HashSet<String>()
    node.findAll().each {
        it.tags.strings.each { branchTags << it }
    }
    node.tags.tags = branchTags
}

def hideBranchTags(node, originalTagsJson) {
    def originalTags = new JsonSlurper().parseText(originalTagsJson)
    node.tags.tags = originalTags
    node['originalTags'] = null
}

[Illegit]

Hi macmarrum,

trouble with tag editor:

1. it happened to me that moving one category tag with the mouse inside the editor (in this case up) to rearrange the categories, twice I inadvertently deleted the full category with its children.
2. I tried to drag a tag inside the category editor to drop in a node tag editor and I didn't succeed
3. when copy a tag from the category editor and paste it in a node editor, it creates a new tag with the full path categories and tag (eg: categoy1::category2::tag1) instead of keeping the same tag format and name.

Do you mean by it that you need functionality for renaming categories of existing tags and moving tags between categories?

My answer is yes to both of your points (1. and 2.): but let's say that I started using tags extensively some days ago, so probably I need more time to take a correct habit how to use them (today I sue about 60 tags but I'm sure they will grow much more in number). And in any case the full categories tree is necessary to be the same for all of the maps or better to choose the preferred categories tree to be used (I understood that this is not yet possible) (some sort of map customization like styles and likes) and this point if activated might avoid your prefixes?

About the script you proposed: nice working it is exactly what I need, many thanks. Already activated!

Now just missing the possibility to hide the node tags (and not to cancel them), in this case using the attribute wouldn't be correct.... because even if tags are hidden we need to account them in their node...

---

Globally this tag tool is something necessary when using maps in work environment: I apply them to complex managerial projects and these maps are really key to keep a little bit of mind sanity.... Thanks to you macmarrum and of course to Dimitry.

[dpolivaev]

Preview 1.12.1_07

[Illegit]

Hi Dimitry wow!

I have some topics:

1. with ctrl+I I cannot create parents as tag in the node, but only tag to tag
   
2. how to recollect the past tags? is there a file where to place them?
3. if you drag and drop
   
   from tag category editor to node editor you have the name + the color and not the effect of just the tag

---

@macmarrum : your previous script doesn't work any longer, any suggestion how to correct it?

[macmarrum]

@dpolivaev

Awesome!

[abc16361]

The tag's height and window margin on tag editor and category manager are too small on default Look And Feel / windows 11. The margin error only happens when the window resized to be a narrow one.

[dpolivaev]

@Illegit I do not understand what you mean in points 1 and 2. I am not a native English speaker, so I need clearer and more detailed sentences to comprehend them. Personally, I use ChatGPT whenever possible to enhance my writing. I request it to correct my texts while staying very close to my original draft.

https://chat.openai.com/share/780452dd-4852-45a3-93fc-f53821e2db81

[dpolivaev]

@Illegit I got what you mean with your point 1. In the node the tag hierarchy is indeed not shown as a tree. It is by design.

[macmarrum]

macmarrum : your previous script doesn't work any longer, any suggestion how to correct it?

@Illegit You can use the latest version - I've split it into a library and a script:

1. Save TagsUtils.groovy to <user-dir>/lib
2. Save toggleBranchTagsView.groovy to <user-dir>/scripts - as usual, you can adjust the menu location by changing ON_SINGLE_NODE="/menu_bar/Mac1/Tags"
3. Restart Freeplane

With the new script, you can toggle the branch-tags view for all selected nodes.

[Illegit]

Thank you macmarrum. Activated.

[Illegit]

Hi Dimitry, about topic 1: I'm just writing that when you use the ctrl+I command for inserting tag in the selected node, it works only if the tag is not a category, question: why not? I would prefer using it in any case, if possible.

[Illegit]

About topic 2: in the previous version I had the file tagCategories.config, but after installing the last release I cannot read my tag structure in the tag editor, it has been wholly renewed, so the question is how to utilize my past tag structure?

[Illegit]

Note that the config file was still there and not overwritten or changed.

[Illegit]

@dpolivaev : Regarding topic 2: I recreated all the tags so there is no need to use the past structure.

[dpolivaev]

I think I resolved all reported issues in preview 1.12.1_08

[Illegit]

Hi DImitry, it works well.
topic 1) 100% solved
topic 3): solved 90%, there is still a little problem, when drag & drop from the category editor to the tag editor the tags change color

Appreciated.

[euu2021]

Now, FP has a first class tag system 👏👏

For me, the name of those two options is confusing:

Map category separator
Node category separator

It's difficult for a new user to guess what it means. I will try to suggest other names 🤔

[euu2021]

I see that Map categories show up at the Edit->Node properties->Manage tag categories for map, but Node categories don't. Also, Node categories don't show up in the Insert menu:

Is there a technical reason for that? I think that I will use Node categories, because I don't see, for my situation, the advantage of Map categories. But, I would like to use the Manage tag categories for map and the categorization of the Insert menu.

[macmarrum]

Can you please share, which advantages you see for the "node categories" over the "map categories"?

When I think about map categories, where a tag is an independent single-segment keyword that can be attached to any category, the term Schrödinger's cat comes to my mind. Here Wednesday is name::Wednesday (as in Wednesday Addams) and weekday::Wednesday at the same time.

When I try to describe node categories, the term fully qualified spring to mind. Here name--Wednesday is its own multi-segment keyword and quite distinct from weekday--Wednesday.

I prefer to use fully qualified node categories. In my opinion, their benefit is that they are unambiguous.

I remembered that I also use tags in Microsoft Outlook. They are called "categories" there. Anyway, when I rename a tag in MS Outlook, the tool searches all items in my mailbox and replaces the old tag with the new tag. So when I think about a fully-qualified multi-segment tag like food--vegetable--tomato and I want to to have it's category vegetable renamed to fruit, the idea of search-and-replace springs to mind:

// Given 4 nodes, each tagged with 1 fully-quallified tag: 'food--vegetable--tomato', 'food--vegetable', 'food--vegetableX--tomato', 'fridge--food--vegetable'
// When User renames `vegetable` (in `food--vegetable`) to `fruit` (as in `food--fruit`)
// Then `food--vegetable--tomato` is replaced with `food--fruit--tomato` and `food--vegetable` becomes `food--fruit`, and the other 2 tags remain unchanged

['food--vegetable--tomato', 'food--vegetable', 'food--vegetableX--tomato', 'fridge--food--vegetable'].collect { it.replaceFirst(/^food--vegetable(?=--|$)/, 'food--fruit') }

// ===> [food--fruit--tomato, food--fruit, food--vegetableX--tomato, fridge--food--vegetable]

Therefore I can imagine a functionality (dialog window) that can rename a category, sub-category or the leaf of a tag without the need for an externally-kept category tree. In other words, I can imagine a rename functionality for any segment of a fully qualified tag. If that's possible, I wonder if there are any reasons to use Schrödinger's-cat-style map categories.

[Illegit]

The option cited by euuu2021:

by adding an option like: show every other category that has the tag

[dpolivaev]

@Illegit Currently when you start tag editor, the tag is shown multiple times if it is registered under different managed categories. Is it what you have in mind?

[Illegit]

Yes, I saw it and I think it is useful.

[Illegit]

I understood, that euu2021 proposed not to have 2 editors but only one with that cited option... or am I wrong? If the case of euu2021 when applying his proposed option, we must have the same result as we get today with the current solution.
Again I prefer the current solution with 2 editors...

[JJSlote]

Greetings - Now on this morning’s Preview 10. Thank you Dimitry!! These new capabilities are absolutely terrific and I’m already making great use of them. With a large map/database of over 11,000 nodes, the ability to sort and filter in a Listview makes the collection manageable, and these colorful Tags are the easiest way to group distant but related nodes together with visual clarity.

I never want to ask for too much, but you did mention that enhancement requests are best illustrated with a use case, so here’s mine.

Quite a few of my notes and links relate to Economics. I’ll capture an article, then use CKEditor and an AutoHotkey script to transform it into the cleanest HTML, and generate a branch node to import title and link into the main Freeplane map, where it looks something like this:

As you can see, the map is all in gray; I’ve set most everything on the PC to look this way, using Windows’ Contrast Themes, to combat eye strain. And nodes are horizontal; I’m using the layout that simulates Outline View.

To fit this node view, a few enhancements to request, mainly cosmetic.

• The display of tags along the left column best fits tightly wrapped and deeply indented nodes. Any chance for those of us using more horizontal layouts to be able to display our tags as sausage links beneath the node text? It’d make for major space saving. Hope it’s not too late to ask.
• With the objective of fighting eye strain, I’d really appreciate the ability to control text and edge colors for these tags. Even if Freeplane generates text and edge colors from the background color, could we perhaps store those colors in the map with their corresponding tagcolor so they could be tweaked with a script? Long hours in front of the screen over many years have me favoring muted, low-contrast colors. And I’d have chosen black over white text and edges for the tags shown above.
• A small UI quirk when changing colors, most likely to be noticed in left-aligned maps like mine. The Edit Tags window aligns with the node’s left edge, and if that happens to be off the screen, it’ll be forced into view, so that both have a minimum X coordinate of roughly 15. However, if we want to change a tag’s colors, the color picker control aligns with the right edge of the Edit Tags window. So, for me, the color picker always starts out partly off the screen. I’d request a similar X-minimum for it.

BTW I also use AutoHotkey to generate a rather crude Listview of my own, to navigate the map and to generate views from it. No XML library, just parsing the mindmap as a long string, which takes about ten seconds to read in and split out. Double clicking runs the NodeURI, of course.

Four Attribute fields are shown as columns, inspiring the question:

• With this round of improvements to Freeplane’s own Search & Replace Listview, any possibility of adding the map’s Attribute fields to it?

Thanks always!!

Jerome

[dpolivaev]

Preview 1.12.1_11

[dpolivaev]

The setting is saved per mind map

[Illegit]

Very nice! I appreciated even the never command!

[euu2021]

Having both options is great 👏