Just a comment here, not a request for or offer of help. I was reading through Joe Kissell’s excellent Take Control of DEVONthink 3 and ran across this:
“That is, if you create a replicant of a document, you can change either
the original or the replicant and both instances instantly reflect the
change… You can also delete either without affecting
the other, because each replicant acts as an original, even though
DEVONthink stores only one complete copy of the data.”
So, changing a replicant affects all other instances, with the exception of the act of deleting one of the instances, which affects only a single instance. That’s actually pretty amazing.
And indeed, replicants are a very cool technology. They’re not for all situations and they can only function within their own database, but they are useful to many people.
Personally, I rarely use them outside of support and exploring the “Hmm… could I do this?” questions that pop up in my brain. But I’m glad they’re useful and make sense to you and many others.
They are an extremely useful feature and I find myself using them all the time now. I can imagine that supporting this across databases is not at all trivial to implement - but boy oh boy. That would set things on fire
