Problems exporting to GraphXML

[hanzobonzo]

Hi guys,

First off thanks for putting the time into this project, it looks very promising as a flexible compiler/editor/generator of topic maps.

I am having trouble exporting a clean GraphXML file for use with Hypergraph. By clean, I mean one that exports only the layer I want (rather all the base layer schema type information), as well as exporting associations as edges (rather than as nodes). Is this an issue of how I organise my topics, or perhaps changing the export settings?

Alternatively, if there is another export format that can afterwards easily be converted to graphxml then I would be interested in giving it a shot.

[hanzobonzo]

Another question related to loading a Wandora-generated GraphXML; when I try to center a certain node using its name in the .xml file (let's say "ID2063089-topic190") the java applet returns an error. Do you have any idea how to correctly call a center node? Or is it more of a hypergraph issue (and perhaps even my java ineptidude in which case some links to properly calling an applet would be most welcome)!

thx
H

[akivela]

Hello

Thank you for using Wandora. For your first question about exporting clean GraphXML. You can export any topic map layer in Wandora separately choosing Export layer > Export GraphXML... in popup menu that opens when you right click the layer you want to export. As a common rule, starting actions in layer's popup menu, modify/process only topics and associations in that layer. If you are unfamiliar with the layer stack concept of Wandora, please see Wandora documentation at [1] and especially the Layers chapter.

Another, perhaps a bit clumsy, method to export just one layer is to toggle all other layers, including the Base layer, invisible, and then use menu options at File > Export.

Unfortunately I can't answer the question related to node centering in hypergraph applet [2]. Can you share the exact java exception, hypergraph applet generates?

If you just want to create graphs with your topic maps instead of a graph application, I suggest you take a look at yED Graph Editor application [3] also. It reads GML files and Wandora can export topic map as a GML file (GraphML) [4].

Kind Regards,
Aki / Wandora Team

[1] http://www.wandora.org/wandora/wiki/ind ... umentation
[2] http://hypergraph.sourceforge.net/download.html
[3] http://www.yworks.com/en/products_yed_about.html
[4] http://www.wandora.org/wandora/wiki/ind ... hML_export

[hanzobonzo]

Thanks akivela for the quick reply!

It was indeed a layer issue.. I tried making a clean root topic on a separate layer and it works. I am still figuring out how the layers work, particularly how to get a new topic class within wandora class to be on its own layer, which is not so clear from the documentation. Whenever I have tried this it exports the xml with all the wandora class/ schema type info that I don't want included! Is there are simple way to use schema types (so as to keep association types as edge labels in graphxml) without all the clutter in the xml file?

As for the applet generates, here you are:

<applet code="hypergraph.applications.hexplorer.HExplorerApplet" align="baseline" archive="/files/hypergraph/hyperapplet.jar" width="780" height="660">
<param name="file" value="/files/hypergraph/test3.xml">
</applet>

I am not sure from the hypergraph documentation how to add the "center" bit; they write that it should be: center="node name" but when I try this nothing happens! They are missing a lot of info on the site unfortunately.

As for using other graph applications, I am open to them, however my end product is for a navigable, animated online topic map; do you recommend any?

Thanks a lot!
H

[akivela]

Hello Again

Actually, you can't attach your topic to Wandora Class as an instance unless you (or Wandora) create a stub of Wandora Class to the layer where your topic locates. This is a restriction of Wandora. If you are addressing a topic in layer, the topic must be in the layer. However, it can be minimal (containing only one subject identifier). You can always create a merging topic with more details in another layer.

If you want to attach your topic to Wandora's topic tree I suggest you create another topic tree for your self. See documentation at [1]. Keep your topic tree separate from Wandora's schema topics such as Wandora Class, and you should be able to keep your layer clean i.e. the layer doesn't contain Wandora's schema topics.

Unfortunately I not familiar enough with Hypergraph to help you with the centering feature.

Yep, I though you are doing some kind of dynamic graph browser instead of a static graph. Some time ago I found this [2] which lists some graph visualization tools. If you fancy Flash application development, I would also suggest you to take a look at Wandora's GraphBrowser Flash extra. It is included in Wandora's source code distribution package, under folder extras/flash_apps. However, a disclaimer, I assume some work (ActionScript programming) is required to get the GraphBrowser working properly with current Wandora application and documentation is minimal as usual

Kind Regards,
Aki / Wandora Team

[1] http://www.wandora.org/wandora/wiki/ind ... opic_trees
[2] http://www.visualcomplexity.com/vc/community/tools.cfm

[hanzobonzo]

Ok, thanks a lot!

Another question, if I have already created a topic with instances, how can I move the entire tree to another layer?
Whenever I do this it only seems to let me copy one topic, without instances, and it loses the association information.

thx
H

[hanzobonzo]

Is there documentation on how to make association types without those types themselves becoming an exported topic?
I've worked on separate layer + separate tab and yet when I export, it drags along the wandora class association types (which are not even on the same layer) as nodes.

[akivela]

To copy your topics between layers you have several different options.

First option is to
* Select the layer where you want to copy your topics.
* Select topics that you want to copy. In your case open the class topic, select it's instances in topic panel's Instances table.
* Right click to open context menu options and select Topics > Copy > Copy to layer or Topics > Copy > Copy with associations to layer.
* Check you moved all relevant topics. Also check that you moved complete topics, not just topic stubs (=topics with single subject identifier).
* When you think you have moved all relevant topic, toggle the layer invisible and
* Remove all original topics in old layer.

This option is good when you have to move rather small number of topics that are nicely related to each other (with instance relation for example).

Second option to move topics between layers is to
* Export the original layer as XTM file.
* Restart Wandora and
* Import exported layer to Wandora as a new layer.
* Remove all unnecessary topics in the imported layer.

This option is good when you have to move a lot of topics compared to non-moved topics and moved topics are loosely associated.

Third option to move topics between layer is to copy topics to new layer via system clipboard. This option is little complicated as Wandora contains no single copy option to move all topic structures but you have to make separate copy/paste to topic's subject identifiers, names, associations.

In general, you can also drag and drop topics to the new layer but Wandora copies only topic's subject identifier to the layer at the moment.

You probably find topic's layer distribution [1] useful information while moving topics between layers.

Also, if you figure out Wandora is missing some features that might help the topic movement between layers, feel free to suggest new features.

Cheers,
Aki / Wandora Team

[1] http://www.wandora.org/wandora/wiki/ind ... stribution

[akivela]

About your other question about exporting association types. Topics that are association types must locate in the layer where they are used. Thus, if you have an association in a layer, association type topic must also be in the layer.

However, association type topic don't need to be an instance (nor subclass) of Wandora's schema topic named Association type. Neither do association role topic need to be an instance (nor subclass) of schema topic named Role. If you have made your association type topic an instance of schema topic Association type then your layer contains a stub topic of Association type and it is also in the exported graph.

If your association types are not instances (nor subclasses) of Wandora's schema topic named Association type and you are just wondering if you could drop association type topics out of graph as they appear simply disconnected nodes, then I have to disappoint you. Graph exports in current Wandora version doesn't allow you to filter out topics that are only association types (or roles). I must admin such a filter could be a good feature as association types and roles really end up to be disconnected nodes in graph. Have to think a feature enhancement

Kind Regards,
Aki / Wandora Team