Replicants across databases

DEVONthink
1

I tried to replicate a “glossary” folder to a new database. This appears to have copied instead. I use wikilinks to point to the glossary terms within my database documents. I was hoping not to maintain two copies. Is there another way to meet my needs? Would indexing the glossary folder into the two databases work?

2

You can’t create replicants across databases. When I need to refer to items or groups in another database, I just create an rtf or md file, go back to the first database, select the group where the items, copy the Devonthink link, and paste it into this new rtf or md.

3

@uimike gives good advice. When I find the urge to “replicate” into another database and then remember it’s not possible, for me it’s a clue to consolidate my databases a bit to enable replication.

2 Likes
4

As others mentioned; you can only replicate within a database
Is there a reason for a new database?
I use a single database

5

As @uimike pointed out, this is not possible (and also often mentioned ad documented).

Possible, yes. Advocated, no as it almost always leads to confusion when managing files in the indexed location. In fact, there are many instances where people have claimed indexing wasn’t working correctly and the cause was exactly what you’re proposing.

Based on your use of the word “maintain”, I would recommend against indexing into two databases.

6

I have all my major databases open all the time. If I don’t remember where something is, I search across databases, which is super fast. Over the years I’ve managed to invent fewer and fewer reasons to replicate (or duplicate) items at all.

3 Likes
7

Thanks for the reply. Having the glossary in the database means that every occurrence of any word in the glossary immediately links from any other text file. Most of the terms I am referring to are in sanskrit. The alias feature of the individual items is crucial given all the different renderings into Latin text (diacritics, no diacritics, erroneous diacritics :slight_smile: ). I have a “draft” database and would like my “production” database to also have this feature. It is not about linking items, in the traditional sense for me. I have landed on moving the idea of production and draft into groups inside one database. Appreciate the input everyone.