I’ll see if I can clarify this, or at least give some ideas for further questions/discussion. Some of the following is pretty basic to DEVONthink, but including it helps me organize my thoughts and may be helpful to those newer to DEVONthink.
DEVONthink databases can contain tag groups (blue tags) that reside under the master Tags group in the database, and DEVONthink can have group tags (gray tags) if group tagging is enabled in the database properties. I’ll use the terms tag group and group tag below to distinguish between the two types of tags.
For all practical purposes, tag information is populated in all databases the same way, and the Global Inbox is a database. Tags can be added to a document in multiple ways before, or at, the time of import. Some of the more common means of doing this includes:
- a document is tagged by the user when the document is added to a database (Sorter, Safari clipper, etc.)
- a document already has tag information when added to the database (OS X Mavericks or later, OpenMeta tags)
- DEVONthink adds tag information when the document is added to the database (convert categories to tags in RSS feeds, etc.)
Let’s assume that in all scenarios below, I have added a document to the inbox of a database. How I have added it is irrelevant, but there is a a single OS X tag associated document. Once a document with tag information is added to a database, DEVONthink checks the document tags with the tags already in the database, and the ensuing process looks like this:
Are Group Tags turned ON for the database?
[list]-if yes, is there a group tag matching the document tag
[list]- if yes, then replicate the document to that group (document is in the inbox with a replicant in the group tag)
- if no, then a tag group is created under Tags (document is in the inbox and is tagged in the tag group)[/list:u][/list:u]
Are Group Tags turned OFF for the database?
[list]-if yes, is there a tag group matching the document tag
[list]-if yes, then increment the tag count of that tag group +1 (document is in the inbox and is tagged in the tag group)
- if no, then a tag group is created under Tags (document is in the inbox and is tagged in the tag group)[/list:u][/list:u]
Now if we are to move the documents in the future, the main difference between tag groups (blue tags) and group tags (gray tags) in the database becomes apparent. Tags in the tag groups (blue) are associated with the document and are fixed in the database, while tags in the group tags (gray) are only associated with its group.
If a move a document with blue (tag group) tags from group to group in a database, those tags remain associated with the document. If I move that document from the source database to a target database, DEVONthink again applies the process described above, creating new tags in the target database as needed. The blue tag remains in the source database, even if there are no other documents in that database with that tag. This is why you are seeing the ghost tags in your Global Inbox. At some point, documents with the three old legislation tags touched the Global Inbox. Perhaps they were imported there, perhaps you used the Global Inbox as a temporary holding location (moving documents from databaseA to the Global Inbox, then moving them to databaseB), whatever, at some point they were in the Global Inbox. When they were moved out, or even deleted from the Global Inbox, the blue tags remain under the Tags group.
Now if a document with gray (group tag) tags is moved from group to group in the database, those tags do not remain associated with the document. Likewise, if that document is moved to another database, then the gray tags do not ‘tag’ along and no new gray tags are created in the target database, nor is the document automatically replicated to a group tag should there be one already in the target database. However, if the document contains blue tags in addition to gray tags, the blue tags will be evaluated as described above.
There is one more scenario that should be mentioned at this point, since I have already rambled on this far on tag behavior. It is possible to assign blue (tag group) tags to the groups in a database, regardless of if tagging is, or is not, enabled for the group itself. If I were to add a document to this group ‘Test’, it would inherit the gray tag ‘Test’ as well as the blue tags ‘DEVONthink’ and ‘DEVONagent’. However, the blue tags in this scenario are conditional-if I move the document out of Test, the document is no longer associated with the gray tag ‘Test’ nor is it associated with the blue tags ‘DEVONthink’ and ‘DEVONagent’.
Hope this helps, and wasn’t TMI for what you were wanting to know.