I wouldn’t think there would be an issue. I cannot recall ever having indexed folders in iCloud but my primary database for many years was an indexed set of folders in OneDrive. There are some horror stories about indexing mishaps in this forum, though I never ran into any major issues myself. Good luck.
Yes, but you should read and understand the In & Out > Importing & Indexing section of the built-in Help and manual, if you haven’t already.
If you were trying to do quick updates between yours and their Mac, I would be less supportive since iCloud can and occasionally does stall. But if there are no time-sensitive documents you’re trying to push to them, it will likely work okay.
Only thing I would add, from my experience (and probably covered in the manual section @BLUEFROG highlighted) is to make sure the folder(s) on iCloud are set to be always on your computer. Otherwise DT will try to redownload any whisked off to iCloud only. This can cause a delay if lots have been moved into the cloud when you open the group in DT.
Follow up question for understanding (apologies if this is in the docs).
As an example, I have a file replicated across different groups in my imported database. When moving them to indexed, how does DTP know which is the master/real file to copy across (as replicants aren’t real so don’t actually get copied)?
…is there a way I can see where that real file is first so I can ensure it is in the right group before moving it to indexed?
You said it yourself – there is no “real” file with replicants, they are all the same. Or rather pointers to the same. And yes, that’s on the documentation.
The only thing that is “real” about replicants IDs their path, and that’s identical for all of them.
If you convert imported files and groups to indexed files and folders, how does DEVONthink handle replicated files in that process?
Does it:
a) make a COPY of each replication in every DT group to the new Finder folders?
b) make an alias in some places?
c) do something clever that’s neither of a or b?
d) can you chose what happens in this particular instance
I don’t work with indexed files to that extent so I can’t answer your question. But you could do a test and make a bunch of dummy groups and replicate a test document in those groups and convert it to indexed files. That’s what I would do. Test. Test. Test. Always test.
The answer is (c) - one of the replicants becomes real.
I assume it was the original one before it was replicated to begin with …but how can you tell where that original is in the imported database?
As @chrillek mentioned, There is no ‘original’ file. As far as DT is concerned they’re all exactly the same. This particular quirk of computery shenanigans doesn’t have a good analog in the real world, at least not one that holds up under scrutiny. Suffice to say that DT doesn’t consider any of the replicants as different or more important than any other. No “original”, no “created first”, no “degraded 2nd generation clone”, nuthin!
If, as you discovered by testing, that only one of them becomes real, what is in the other newly indexed locations where the replicants were?
An alias?
Nothing?
