Another question is where to put individual resources to a Markdown document: Images for example. I see multiple solutions:
Putting the images on the same level as the Markdown document. This is simple and clear, but clutters the group. Plus: How do you handle it when you move the document into another group? This breaks the links!
Putting the images in a common subfolder/group. Less clutter, but same problem with moving.
Putting doc and images in its own document-specific group. This group is named like the document. Moving is a breeze (you move the whole group), but you will end up with lots and lots of small groups.
On the same line: Using Textbundles. (See http://textbundle.org/) Does anybody have experience with this?
Another option is to use cross-links (see Edit > Copy Item Link). Creating such links is a little bit more work but the advantage is that you can file your stuff the way your prefer and that moving doesn’t break anything.
That’s a great idea! Works only for documents solely used inside DEVONthink, but really solves the moving issue. Cross-links seem to be the way to go.
Tell me what happens when the other database isn’t open?
And it’s not going to be obvious what database or file is missing from the reference URL, yeah?
Not saying, it can’t happen. I’m asking you to really think about whether you should do it.
Happens for me in both cases, whether the referenced DB is open or not.
It’s not a big thing really; just I have decide to create a separate database “archived” which collects oudated items (like old flight schedules etc), I normally do not want to search for. Because group excluson in search doesn’t work, I though moving outdated items into another database would get around this - but it does break the image links in Markdown.
