Hello everyone!
I think the Windows version has an OPML bug. If you tick the “Create folder for OPML” box, it creates a folder, but it also places a group of documents inside. I can explain more with screenshots.
I’m not understanding how the effect is undesired or unexpected. The option is meant to group the imported outline nodes into a master group/folder automatically. That is why it puts the imported outline inside of the folder.
I think it would be strange to have an option that creates a group when importing an OPML outline, and then not use it, to I suppose import everything to the top level anyway, leaving the created folder empty.
2 Likes
I would suspect then that the OPML outline already has a “root node” (in outliner jargon), by the same name as the file name used when importing it. I don’t get that result if I for example export my entire binder to OPML and then drop it straight back in. I get all of the top level binder items at level 2, just beneath the “filename” folder that was created to import them into.
Of note, some outliners will export a root node into the OPML, as that concept is considered a traditional ingredient of a “proper” outline: that all nodes must descend from one singular root node. A lot of outliners hide that node in the UI, since it is kind of superfluous and not terribly useful to us as users. I have seen some outliners that let you show it, and others that have options to omit it on export.
Mind-mapping tools, on the other hand, tend to always show this root node, because it is central to the design of how they work: it’s the one in the middle.
2 Likes
I have a Python pipeline that takes a TXT file, tags it for structure, converts to Excel and then takes the Excel and creates a ZIP file with all sheets as OPML files. Maybe something is wrong with my AI code… 
Well, you’re in control then! I’d suggest exporting a few top level items from Scrivener together, to OPML, and examine the XML for an idea of how you can have something that imports top level items directly into the container folder.
Of course, you could also just turn off that checkbox, since they already are in a group. 
I never had this problem on Mac, BTW. I had OmniOutliner.
Windows is trickier. To get folders, I just convert groups, but it’s annoying when you have a lot.
Oh, you mean how it uses a straight outline on import, instead of indulging in the oddity that is “folder” vs “file”. 
I think technically it’s supposed to do otherwise.
I’ve always turned off the features that make any distinction between the two,[1] as it never made sense to me have a “folder” in an outliner, where everything that is within an outline is premised upon the concept of branching off of some central thing, and any thing can be branched off upon likewise.
Anyway, that’s one aspect of Scrivener that always left me bemused. I choose to largely ignore it, as to me it makes life so much easier.
Behaviors: Folders & Files: Treat all documents with subdocuments as folders. ↩︎
1 Like
Being neurodivergent I’m very literal about things so that always confused me.
1 Like
BTW @AmberV, is importing a bunch of OPML files and then right-clicking to “Convert to Folder” much of a big deal depending on how many files you have?
The difference between a folder and a file is this:
<BinderItem
UUID="66154BF7-0034-454E-99CC-173FCD8C3966"
Type="Folder"
Created="2020-02-17 12:16:15 +0100"
Modified="2021-08-18 13:19:27 +0100">
<BinderItem
UUID="66154BF7-0034-454E-99CC-173FCD8C3966"
Type="Text"
Created="2020-02-17 12:16:15 +0100"
Modified="2021-08-18 13:19:27 +0100">
To make your life easier, set up your Section Types to treat file groups differently, then add the section type column to your outliner, sort by it, shift-click and convert the whole range at once.
2 Likes
Treat file groups differently as in creating a different section type for them?
You could make a special one just for this purpose, or just set them to act like folders when you compile anyway, so that you don’t have to be too careful about it in the future. All you really need is for them to be distinct from file items that have no child items.
2 Likes
I really wish there was a better icon for document groups by default.
Hmm, well part of what I like about how they are is how they are just as easy to work with as file types, with regards to the way an icon will change depending on its content and snapshots. Folders have this tiny little badge you have to squint at to get that same info.
But something that might help, visually, is the option in Appearance: Binder: Fonts, where you can set both groups and folders to use boldface. It helps them stand out from non-grouped items.
2 Likes
This is a very good tip, even though I’ll probably CLTR+A everything and Convert to Folder xD