Thanks for all of you input.
To clarify, so far I’m only syncing one database, and I’m using as a way to clip and save articles (in a PDF format) so that I can read and quickly annotate them.
In the past, I’ve clipped files by saving them as PDFs, and storing them in my DropBox, divided by subject folders. Because of DTTP’s recent improvements, and because DTP is the final repository for my files & documents, this is my new workflow:
(1) Clip documents on Mac & on iOS: Save documents, as PDFs, and save on synced DB while…
(2) …I attach subject tag – in lieu of my old DropBox subject folder
(3) Then I read and do a cursory annotation on files in synced DB (reading/annotating with in DTTP if in iOS) and then…
(4) …move to files from synced DB to “WORK” database in DTP → [subject group] and then…
(5) …use the following script do a more comprehensive annotation, notes, and tagging:
By the way, per @korm 's suggestion, I’m experimenting with Marginnote as an alternative way to accomplish the clipping, reading and annotating – within a synced DB. I’m told that Marginnote might soon integrate with DTP, and might even be able to port over their annotations into DTP tags.
Why not just make my old DropBox folders into DTP databases and sync them? In short, I’ve been advised to consolidate as much similar work-related subjects into a single DB rather than splintering them into over a dozen DBs. The other thing is that these DB contain a LOT of files, and might require a cost prohibitive DropBox account (or some such cloud service).
(I still haven’t figure out how to create an annotation & filing system that will provide a tag-like approach for grouping annotations for files for specific projects, as well annotations that crossover my projects and contain globally annotation - themes. But that’s a different topic.)
I’m happy to consider another approach, and welcome your suggestions. Just thought I’d clarify why I’m using the the tags for my synced DB, and how it fits into my current workflow.
Thanks for your help.