Hi,
I’m looking to reorganize my processing of material and switch to DT and DTTG for all my needs. I hope this is a straightforward question: is there a way to create tags that remain valid in all DT databases? And how are these tags handled in DTTG?
From documentation and many valuable discussions in the forum, I understand tags are created in the “current database”. I understand Finder tags are an option, but I’m looking at the long run here and would like to keep things to the application, if possible.
Isn’t that the same question worded differently? But if you mean share as in “move”, if you move a file that is tagged from Database A to Database B, the file retains its tags. That means if the file is tagged “Book” in Database A, the same tag would appear in Database B when you moved the file.
I just tried this. I highlighted a bunch of tags and used File->Export->as Template.
In another database I double-clicked on Tags to focus on just the Tags. If you don’t do that, the import will create the tags as groups in the top level of the database.
Once I was focused on Tags, Data->New->From template imported the tags into the database.
And remember - when running with scissors always have good backups.
If your export included tagged files, not just the tags, importing the template will create empty files in your database’s inbox.
Another, easier way, is to open the database you want to get tags from in one window and the database you want to copy the tags to in another window. Highlight the tags you want to copy and option-drag them (copy) to the other window, dropping them on Tags.
A side effect of that method is any files that came over will appear as files in the Tags. The files won’t appear in the Inbox or any group, so when you de-tag them they disappear into the Trash.
In another database I double-clicked on Tags to focus on just the Tags. If you don’t do that, the import will create the tags as groups in the top level of the database.
Correct.
Once I was focused on Tags, Data->New->From template imported the tags into the database.
A perfectly valid thing to do. In fact, I set up a tag template for a firm in London using rhe same idea. They’ve been using it for years
If your export included tagged files, not just the tags, importing the template will create empty files in your database’s inbox.
I’m not seeing empty files created. I’m seeing the documents that were in the tags group pre-export to template.
Yes, my mistake. I did this with test databases. The files on the source side were empty, so that’s why I got empty files on the destination. I apparently achieved a state of writing Zen, files empty of corporeal distraction, without thinking about it. That has to be a perfect state of Zen.
Thanks for the “divine” insights and practical tips from my side too.
I have the basis for a workflow that helps ensure I keep some consistency across databases and improve my transition process.
But if you mean share as in “move”, if you move a file that is tagged from Database A to Database B, the file retains its tags. That means if the file is tagged “Book” in Database A, the same tag would appear in Database B when you moved the file.
and welcome 
and practical tips from my side too.