What CSV format would produce this?


I’m not sure if you can help with this.

I’m having problems figuring out how to work with the .csv files. Unfortunately, there’s only one example in the manual. I generally go through a lot of trial and error, with mutiple examples, in order to master a langague or a tool.

There is another diagram tool out there, that exports their maps into a .csv file, which can then be imported into Flying. They explain the FL CSV Import settings, and the CSV column interpretations.

Unfortunately, it’s implemented only on a Mac. So, if possible, I could use another example to learn from.

Is it possible for you to return the contents of a .csv file, which would reproduce this?

I think this example would be sufficient. I’m not looking for a general method or csv structure ; as you mentioned in another post, you have to write custom scripts & .csv in general.

I just need a csv that applies to the concept/argument diagrams that I tend to work with. Or specifically, just this one.

A_CSV_file_that_represents_this_Map.xlogic (38.2 KB)

Here is a CSV file that, if imported into a document already containing the entity classes you want to use, will reconstruct the same document you provided:

1,"I believe A...","Position",,
2,"That's ridiculous, because...","But",1,
3,"...is only true...","Rebuttal",2,
4,"Nya Nya...Irrelevant extraneous...","Rebuttal",2,
5,"But it's not true generally...","However",4,
6,"Circumstance A","Example",4,
7,"Circumstance B","Example",4,
8,"So you're saying...","But",4,
9,"That's a typical...","But",5,
10,"Yes, I'm saying that.","Agreed",8,
11,"So? ...","Rebuttal",9,
12,"More importantly...","Furthermore",11,

Just as important are the settings you set in the first and second dialogs that appear. The first one asks you for general information about the file you’re importing. I set it for UTF-8, because that is what Macs (and most computers these days) use. Also notice that I am not using a header row, and I am importing into an existing document.


The importer then reads the file to see what columns are in it and presents the second dialog:


Make sure you set every menu to be the same as shown.

The result is, if imported into your original document, a parallel tree:

Notice that the “However” element is not the same color, because you have two different entity classes both called “However” and the importer just picked the first one it found whose name matched.

1 Like