My current state of Tags are a mess that’s 10+ years of randomness. I’m working on a new nested Tagging system that has some organizational logic to it.
My Question is, what is the best way to start with a clean slate? I have a half dozen separate databases (but related). I have the “unify tags” box checked.
Is my best move to click on the Tags icon in the Left Sidebar and to delete all the tags and start from scratch to implement my new logical nested Tags?
I also have a dozens of Groups with a Tag assigned to them. Is there any way remove all the Tags from the Groups without checking each individual Groups “Get Info”?
Thanks in advance
Larry
Remember, there is no global Tags group for all databases. So if you have multiple databases, each has its own independent Tags group.
All items – documents and groups – have item references in the tags applied to them.
If you truly want a square one approach, then yes you can select the Tags group for a database in the Navigate sidebar, then Command-A in the item list to select them all, then Command-Delete or Data > Move To Trash. Finally, empty the database’s Trash and proceed with other databases as needed or start building your new tag structure.
I thought that the “unify tags” option was to create a unified set of tags across all open databases???
Please explain?
Larry
It is just an option for how they are displayed in the sidebar.
(It is a setting under General > Interface, so that makes sense to me.)
I suggest looking in the manual. I typed “unify tags” in the Help menu’s search field, which gave two results:
Settings > General
Windows > Sidebar: Navigate
2 Likes
That is an incorrect assumption. See the documentation references shown by @troejgaard.
As @troejgaard says, it just lumps all the tags together. Be aware that if you have a tag “Done” in Database A and a tag “Done” in database B, you will get two “Done” tags in the unified list.
I personally don’t unify tags, but have them listed for each database. Why? Because I tend to have unique tagging rules for each database. For example; a recipe database has all the Tags as ingredients. My work database, the tags are more about type of document (proposal, plan etc.) and status (Waiting, in progress, done etc.) Unifying would have “damsons” next to “done” which, for me, makes a tag mess.
Some people create tag order by prefixing tags like work-in_progress, work-done, recipe-apples. But for me, this is too much visual clutter.
1 Like
