Hiding columns in exported web pages
Matthew Taylor
In a typical network node table or edge, there are a lot of columns, some of which can't be deleted and some of which you don't want to delete.
In the program itself, you can chose what is displayed, but then when I export to a web page, every column is there, meaning that the actual relevant information for someone browsing the network is hidden away right at the end when they scroll across, with a load of info that is irrelevant to most users showed at the start.
Is there any easy way to control what columns are displayed in these tables in a web export, whether by altering the CSS, or some other means?
Any suggestions would be welcomed.
Matthew
Alex Pico
You're not missing anything. The table display options do not affect what is exported. Table export always delivers all columns.
- Alex
Matthew Taylor
Thanks for this info.
So - with the non-deletable columns, there is no easy way to stop them displaying in the web exports then? Unless I can somehow do it with CSS or something - which I guss is a cytoscape.js and not a Cytoscape query.
Thanks again for the quick reply.
Matthew
Alexander Pico
I think that’s correct. I’m cc’ing one of the developers of the Export-to-Web feature to confirm.
--
You received this message because you are subscribed to the Google Groups "cytoscape-helpdesk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cytoscape-helpd...@googlegroups.com.
To post to this group, send email to cytoscape...@googlegroups.com.
Visit this group at https://groups.google.com/group/cytoscape-helpdesk.
To view this discussion on the web visit https://groups.google.com/d/msgid/cytoscape-helpdesk/2830049f-45df-47aa-9fda-8746c3864fdb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Barry Demchak
I’ll pinch hit for Kei, who is out on vacation.
The output for Export-to-Web does include all of the column values associated with each node. That’s by design.
The column values themselves are simply fields in the “data” element associated with a node (see below). Cytoscape.js doesn’t do anything with them at all … it cares only about “id”, and the rest is up to the application in which cytoscape.js is embedded. So, there wouldn’t be any CSS to eliminate them … they were never included in the cytsocape.js rendering in the first place.
The only down side to this is that the networks.js file carries more columns than the consuming application may be interested in.
Does this explain things??
"nodes" : [ {
"data" : {
"id" : "391",
"degree_layout" : 1,
"gal80Rexp" : 0.292,
"gal1RGsig" : 9.1177E-4,
"Eccentricity" : 26,
"gal4RGsig" : 3.5692E-6,
"shared_name" : "YKR026C",
"TopologicalCoefficient" : 0.0,
"SUID" : 391,
"SelfLoops" : 0,
"NumberOfDirectedEdges" : 1,
"AverageShortestPathLength" : 15.37096774,
"selected" : false,
"gal80Rsig" : 0.011229,
"ClosenessCentrality" : 0.06505771,
"Degree" : 1,
"isExcludedFromPaths" : false,
"PartnerOfMultiEdgedNodePairs" : 0,
"ClusteringCoefficient" : 0.0,
"Radiality" : 0.46774194,
"Stress" : 0,
"BetweennessCentrality" : 0.0,
"NumberOfUndirectedEdges" : 0,
"gal1RGexp" : -0.154,
"name" : "YKR026C",
"COMMON" : "GCN3",
"gal4RGexp" : -0.501,
"IsSingleNode" : false,
"NeighborhoodConnectivity" : 3.0
},
"position" : {
"x" : 8652.080790935715,
"y" : -2459.858853805801
},
"selected" : false
}, {
…
To view this discussion on the web visit https://groups.google.com/d/msgid/cytoscape-helpdesk/D45A6982-B472-415E-92C9-393B68A1DEB1%40gladstone.ucsf.edu.