Sure, here’s a more detailed breakdown. I have four DEVONthink databases. I’ve landed on these as a compromise between content category, file size (syncing), and unique words. You’ll have to forgive some of my cryptic naming. “Maps” is essentially my word for the “Resources” branch of PARA.
- Artwork (art and media—primarily PDF music scores, tables/markdown, liner notes, supplementary info)
- Feeds (informal “streams”—YouTube, etc.)
- Products (documentation and product information)
- Publications (formal/structured works)
The root level groups in each DEVONthink database each have a corresponding “subcollection” (nested databases) in Collections. Records within a subcollection often point to a DEVONthink subgroup below these root level items. The group URL field contains the UID link to the Collections record. As you’ll see in the “Applications” example below, everything gets a record in Collections, but it only gets a parallel group in DEVONthink if there are files that need storing (in this case, just Carbon Copy Cloner).
Collections also has some exclusive databases (i.e. no parallel DEVONthink groups). Things like People, Groups (bands, companies, organizations), Topics, etc. These are relational fields that help to aggregate resources and build meaningful connections. This way I can browse by people or topics and quickly see all relevant resources (which are often spread across multiple DEVONthink databases). A single person could be associated with items located in multiple places.
I’ve basically tried to atomize these data types into their most basic forms (articles, books, people, topics, etc.) so I can dynamically patch them like a switchboard operator.