DT 3 and Dropbox

DEVONthink
43

Dropbox syncs well all the files. The machine I use DT3 as source for synching file seems to store files correctly in DEVONThink Packet Sync folder.

However, other machines with DT3 , and DT3 To Go does not pick up these changes anymore.

Interestingly enough the timestimp of 039821309820938.receipt file are correct but this timestamp of change is not propogated uppwards in folder hierachy to “DEVONThink Packet Sync”.

44

the timestimp of 039821309820938.receipt file

Can you show this file in the Finder?
Does it point to a different location than the one in the DEVONthink Packet Sync folder?

45

The the XXX.recept file is in the Packet Sync. The actual file that is indexed by DT3 is outside DT Packet Sync but still in Dropbox.
Altog it appears that the indexed file is also in the YYY.item

Here are two related YYY.item’s.

<?xml version="1.0" encoding="UTF-8"?> 0D0FBAEC-F239-4F77-ABB3-498B10FFC008 Added 635000809.65428197 Changed 635000820.95826101 CharCount 641107 Created 635000802 FileSize 891917 ImageCharacteristic TU0AKgAADAj4+Pj4+Pj4+Pjo6Oj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4+Pj4 ........ REMOVED ...... igAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKAP/Z title 1998, A Framework Of Information System Concepts type 12 version 30 visibleLocation 0 <?xml version="1.0" encoding="UTF-8"?> 50C2362B-64C5-4276-B264-17566CC9D384 Added 628097321.58095098 Changed 635000809.658108 Created 601126039 Modified 635000809.658108 Read 0.0 SyncAction 2 SyncParentIDs @Root Touched 628096920 UUID 50C2362B-64C5-4276-B264-17566CC9D384 creator mac index noTagging path /Volumes/ExternalMACOS/DropboxWO/Dropbox/Research Files preview 2 recordtype 1146382194 reverse sort 3 table Group title Research Files type 1 version 30 view 0
46

Is your local Dropbox folder on the external drive ?

47

Yes, and this arrangement worked for both plain Dropbox and DT3.

Maybe the break came early december 2020.

48

I’m the guy that keeps banging on about verification. Here is another example. If this guy’s files were exact and complete no sensible verification would have passed.

It’s a bit like the pandemic, without a reliable test for C19 every attempt to solve the problem would be mostly futile. You guys are struggling with sync but still have no way to answer two fundamental questions; “are these two databases in sync and can I rely on their integrity.”

Until that is solved not one customer can be absolutely sure that their sync has succeeded. Incidentally, once sync is verifiable it can be used as part of a backup strategy (sync from DTTG to a Mac, backup mac). You are quite right to discourage this approach at this juncture but in future, maybe after 3.0.3 … ?