Smart Tag to enumerate all files

Hi, I’m currently trying to get all my official documents organized using TagSpaces, right now I’m only using png.s but I’d like to keep the connection to the real world paper. What I was thinking is adding a Smart Tag, that’s just an incrementing counter. That way, I could just tag every document I “upload” with it, write the number it generates on the paper and put it in a physical file. That way when I need it, I could just look up the number and easily find the physical document with it.
I’ve already thought about just tagging everything with a generic Tag and editing that afterwards but that’s way more hassle, also keeping track of the current number. I’ve also thought about using the date Smart Tag, but that’s more to write on the paper and less easy to find.
I’d be really happy if this, in my imagination relatively easy, thing could be implemented.
Thank you very much!

Hi, and thanks for this suggestion. I can understand your need but the problem I see is that TagSpaces can easily loose the counter for this id. This can happen if you install the application on another computer or you work collaboratively with some body on a network/shared drive. Both installation will have different counters, so collisions will happen. Despite of that we can think about adding the ability for creating “smart” ID tags, where you can define the start value of the counter manually and maybe some optional namespace like a shortcut for a project e.g. XY-23, XY-24 …

1 Like

Hi, thank you very much for your fast answer!
Maybe the keeping track part of the problem could be solved by having a variable saved on the location level which gets incremented and basically saves the state of the counter. And yes, the idea to be able to create smart tags sounds very promising! For this problem the abilty to set the counter to any number manually would be great and could even out problems with keeping track of the counter. Even greater of course would be the ability to create custom smart Tags that have a simple code snippet on the backend that defines what the Tag will look like, although I could see why this is much more complicated.
I’m excited to maybe see some of these features in a future update!