3

Closed

"Ontologies" add-in randomly deactivated

description

Sometimes, the "Ontologies" tab disappears after Word is closed and reopened. It appears to be inactivated in the Add-in Options menu. I tried reactivating it, but that didn't work. This issue seems to be unique to the latest release. Reinstall fixes it.

file attachments

Closed May 7, 2010 at 11:56 PM by erteam
Fixed in Beta 2

comments

shypras wrote Jul 16, 2009 at 8:52 PM

Same Issue - Repro on multiple machines running Office 2007.

jlfink wrote Mar 4, 2010 at 12:30 AM

Can we close this? I haven't experienced this behaviour in the latest version, but I'm not sure about others.

sjegen wrote Mar 22, 2010 at 2:49 PM

A may have experienced the same disappearing "Ontologies" bug. As said above, a reinstall of the Add-in seems to (temporarily?) fix the problem.

While experimenting with the Word add-in I experienced some problems which could be related:

After importing some of our ontologies using the rather handy local ontology load option in the configuration menu, the behavior of
the text tagging became inconsistent to a certain extent. Some tags in a text used for testing purposes continued to be shown even after removing the ontologies which contained them. Other tags were not applied at all or needed a restart of Word to be shown properly in the text.
I admit that these findings are rather difficult to replicate, but other users may have had similar problems occurring and could provide further data which may prove useful to locate the problem.

Another inconsistency was found with the "Ontology Term Viewer". Even after loading a local .obo-ontology without any problems the viewer does not show the names of all the root nodes present while browsing the ontology (see screen shot; interestingly the child nodes do not seem to be affected). I tried to find differences between the nodes which could account for the displaying problems but found nothing. Neither a restart nor a reinstall makes the nodes appear.

Some system specs:

MS Office Word 2007
Windows XP Professional SP2
1GB Ram
32Bit 3.4 single core CPU

Any ideas on what could cause these results?