search

opencarecc / graph-ryder-dashboard

A dashboard for exploring and summarizing an online forum with ethnographic coding
http://opencare.cc
Apache License 2.0
3 stars 1 forks source link

Provide an export facility for beautification and batch graph analysis #6

Open albertocottica opened 7 years ago

albertocottica commented 7 years ago

Example use case: you want an attractive picture of a local subgraph. Instead of trying to cram everything into the dashboard GUI, we focus on making one clear, standard visualisation on the dashboard itself, but allow export in a suitable format (like GEFX).

jason-vallet commented 7 years ago

I think I saw something somewhat similar available among the Sigma.js plugins. I add it on the todo list.

albertocottica commented 7 years ago

closing

albertocottica commented 7 years ago

Upon importing the exported files into Tulip, I get errors:

image

If I click "Cancel" and then "Continue", it goes through, but the results make no sense:

image

albertocottica commented 7 years ago

Also tried exporting the JSON and reimporting:

image

jason-vallet commented 7 years ago

Hi Aberto, I have fixed the CSV export, there was no real bug, you only needed to change the text delimiter to ' instead of ". The default options are now the right ones. The JSON import does not work properly in Tulip but the export should give a graph compatible with Gephi (as you had initially asked for GEFX files). I have also added the export tool for Tulip files directly. The graph is always exported as a whole (unfiltered), but a subgraph is added with only the filtered elements.

guywiz commented 7 years ago

Great, I just realized we had this export functionality.

Would it be much more work to have it as well for all other views ?

jason-vallet commented 7 years ago

Done, it's now available on all the views using sigma (tag-tag full, tag-tag and doi).

albertocottica commented 7 years ago

@jason-vallet just to let you know that the export only exports the selection, as a standalone .tlp graph .

I would prefer your solution of complete graph + selection as a subgraph, if that's not hard to do.

albertocottica commented 7 years ago

Also: I noticed that the edge_force property is not exported. Would it not be simpler to export everything, at least in Tulip format? By that I mean: number of occurrences (and name as label, of course) on the nodes, and number of co-occurrences (edge_force) in the edges.

I am thinking of the trouble we had dealing with Anders's data...