Duplicated tags

DEVONthink To Go
21

It will just prevent it from happening again but you’d need to merge them manually we’re afraid.

22

Sorry, cannot tell, I do not use a Mac.

23

I’m sorry :cry:
:wink:

24

OK, this took some time, but i think i understand how things work now, and wanted to ask if i have the right of it:

  1. every tag is specific to the db in which it’s created: if i create a tag—tag1—in dbA and then create tag1 in dbB, when i check Tags in global, i will see two tag1 entries, but checking the info panel will show that one is in dbA and one in dbB. These are not duplicates; tags are db-specific. do not merge these.

  2. there was a bug at some point that duplicated tags. mine all seem to be in the global inbox. the duplicates were created at the same time and modified on different dates but the same time for each one (i have screenshots if anyone wants to see) :stuck_out_tongue_winking_eye:

there is no autofix for duplicate tags.

how to fix duplicate tags

  1. first, select each tag and check the properties. make sure the tags are in the same db.
  2. select each duplicate tag in the same db.
  3. then click Tools > Merge x Tags (where x = the number of selected tags.

NB: currently, this can only be done on the mac, though this feature may come to DTTG at some point.

i hope i have that correct, and i’m about to start fixing my duplicate tags. :wave:

25

i also noticed this: i just created two PDFs from email. i saved them to my DT inbox. I added two tags.

then i went to DT and dragged them from the Today smart group into the appropriate db. because of all the above, i checked global Tags, and sure enough, there are now two seemingly identical tags, but checking properties i see that one is in the global inbox (showing 0 documents) and one in the db.

i kinda wish there were just one global universal tag, but i also think i really like this because i can see where i might want the nuance of two (or more) tags based on the db in question.

anyway, just an FYI to the above.

26

What I do is have a smart rule that deletes all tags with zero documents to keep things tidy. It runs if there is a sync. It was suggested somewhere in the forum as I too found having duplicate tags where one had zero documents annoying.

FYI - I don’t ‘unfiy’ my tags (have option off) as I generally have different tag schema for different database. E.g. My cook book DB tags are all ingredients. My work DB tags are things like ‘agenda’ ‘minutes’ etc. The tags show at the top of each DB and I am generally only working in one at a time.