Is there anyway to import a markdown document with with wiki links and have the wiki links to Scrivener links please? I am working on an Obsidian —> Scrivener, and Scrivener —> Obsidian workflows.
Any help on how I can keep the links working between the two applications would be greatly appreciated. Thank you.
Definitely not with anything Scrivener would be doing, but to my awareness I don’t know of anything else that could be of assistance either. It’s not something I’ve ever looked into, but “wiki links” aren’t something Markdown or any of the major variants make use of. The closest analogue are internal cross-references in MultiMarkdown and Pandoc, with the [Name of Heading] construct. I don’t think Obsidian supports that form of linking though, and it wouldn’t work for links to external files either.
That’s part of the reason for why I disabled the Use [[WikiLinks]] option in Obsidian, so that it uses standard Markdown syntax. That setting seems better for self-contained stuff that isn’t going to leave the vault without exporting.
Even so, using standard syntax doesn’t generate RTF hyperlinks when importing or syncing plain-text files either. So all you’re doing is making sure your links ultimately work beyond Scrivener, rather than being something you can also click on with the mouse.
Thank you for the reply. My issue with Obsidian is getting even Markdown links outside of Obsidian working properly. I do love it as a note taking tool.
From my experiments with it, it feels like a tool best used in an inward facing fashion, despite the premise of using .md files on the disk. It does it’s own thing when it comes to extended markup, despite there being good established alternatives elsewhere. The alternative is to sacrifice the use of features that depend upon that syntax and keep the full promise of having a cluster of .md files on the disk alive.
As for how to combine Scrivener and Obsidian (I use the sync folder approach), my philosophy is to consider Scrivener’s role the metadata and Obsidian’s the content—that is, for the area that is synced. If I were trying to use the two together to write then I suppose I would need a different strategy. But for how I use them together, for notes entirely, I am content to let Obsidian handle the text and Scrivener everything else. The notes can go anywhere I want in the binder, they don’t need to all be stuck in one folder. They can benefit from all of the stuff in the inspector, which is an whole area of usage that Obsidian does not touch, and thus there is nothing to integrate or worry about finding ways to sync. There is no summary/synopsis, no bookmark list, no sidebar notes, no snapshots, etc. Keywords/tags—yeah, but since Obsidian’s are all forced to be in the content itself you aren’t really losing them in Scrivener. They become search anchors rather than listed tags.
With that approach and way of thinking about the two, I do feel more free to use Obsidian nomenclature for a few things—to use it, as described, in an inward facing fashion where the .md file aspect of it is thought of more as a fail-safe backup than a feature. Where you use its custom syntax without thinking of the notes being pure Markdown or needing to function like them, or integrate with other software.
I’ll admit, that approach is not entirely my jam. I still have a somewhat uneasy relationship between what I feel is best practices (pure Markdown) and wanting to take advantage of neat internal features like back-links and graph view. Most such features remain for me interesting in theory, but until they allow for standards compatible approaches, to me a few convenience features are not worth a Markdown fork in thousands of notes, that I later have to account for in 15 years or whatever.
Thank you once again. So I should be able to sync my obsidian folder with Scrivener then? One thing I have considered is using Obsidian like a mobile Scapple and duplicating the info in Scrivener using Scrivener links instead for compiling out the info. The only downside I can see is the possibility of missing out info accidentally because the info is separate rather than shared.