Hi, I would like to import weblog posts into scrivener via MMD - or any other option? - including tags, categories … whereby the import of each post should follow the logic
tags ==> to be imported into ==> “keywords”
categories ==> to be imported into ==> “custom meta data”, a new item to be created for each category
attachemend ==> link/ref to be imported into ==> “Document References”
…
Do you know how this could be done in Scrivener?
I can create any input file based on the weblog mysql database.
No that’s not going to be possible. It wouldn’t make sense in most cases, too. The way the MultiMarkdown exporter works is: anything in the meta-data block is inserted into a “Meta-Data” file at the top, and then all of the sections as split apart by headers are created as binder outline structure. That’s all it does. At the most it would be somewhat sensible to inject meta-data into the Compile settings, but even then that isn’t really necessary because a top “Meta-Data” file will do that during compile anyway. The reason why it goes against the grain of this importer is that its primary purpose is to take a long document and generate potentially dozens or hundreds of documents out of it, in outline order. So where would those keywords and other meta-data go, from the top block? That’s project level stuff for most usages.
Beyond the theoretical, there are other technical problems as well. There is no standard formatting for keywords in MMD. It’s really just a free-form text field. Generating custom meta-data columns off of MMD meta-data fields would probably also be cumbersome. I’m sure you wouldn’t want a custom meta-data column for “Format” or “LaTeX XSLT”; so Scrivener would have to blacklist some fields, and that would involve keeping things up to date with MMD’s movement and so on—and that is still assuming this would be useful for the average import. I don’t think it would be since the average import populates a project not a document. It would be a huge pane to remove a bunch of keywords from a hundred sub-documents.
What you might just want to do is wait for AppleScript. It’s not even on a timeline yet, though. It’s a plan.