kallimachos issueshttps://gitlab2.informatik.uni-wuerzburg.de/groups/kallimachos/-/issues2022-07-11T12:01:22+02:00https://gitlab2.informatik.uni-wuerzburg.de/kallimachos/wuenlp/-/issues/4When using the new decorator (add_feature_mapping) instead UIMAProperty, the ...2022-07-11T12:01:22+02:00Dirk WangsadirdjaWhen using the new decorator (add_feature_mapping) instead UIMAProperty, the setter won't work and cause problem.When I tested it (folder: lingson, file: new03.py (and new04.py)), this problem doesn't occur. The setter worked without error.
Notes:
Same as Issue#3 (Subclass from UIMAEntity can't recognize properties...)When I tested it (folder: lingson, file: new03.py (and new04.py)), this problem doesn't occur. The setter worked without error.
Notes:
Same as Issue#3 (Subclass from UIMAEntity can't recognize properties...)https://gitlab2.informatik.uni-wuerzburg.de/kallimachos/wuenlp/-/issues/3Subclass (Inheritance) from UIMAEntity can't recognize properties (UIMAProper...2022-07-03T15:15:02+02:00Dirk WangsadirdjaSubclass (Inheritance) from UIMAEntity can't recognize properties (UIMAProperty) from parents.When I tested it (folder: lingson, filename: new03.py), this problem doesn't occur. It can access the getter and setter from its and parent's properties.
Notes:
- I copied the new UIMANLPStructs.py to my folder and added the decorators ...When I tested it (folder: lingson, filename: new03.py), this problem doesn't occur. It can access the getter and setter from its and parent's properties.
Notes:
- I copied the new UIMANLPStructs.py to my folder and added the decorators in the copy
- In the code to generate the function dynamically, for further testing, I even deleted the added loop for subclass which you added before, and everything still works fine.https://gitlab2.informatik.uni-wuerzburg.de/kallimachos/wuenlp/-/issues/2PyCharm warning: Property 'speakers' cannot be read2022-06-26T12:02:37+02:00Dirk WangsadirdjaPyCharm warning: Property 'speakers' cannot be readPyCharm give this kind of warning for methods in class UIMASpeech that use the decorator UIMAProperty with both override parameters set to False.PyCharm give this kind of warning for methods in class UIMASpeech that use the decorator UIMAProperty with both override parameters set to False.https://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/57linking of selection analyzer and terminology tree2017-07-26T17:32:04+02:00Joni Krebslinking of selection analyzer and terminology treeit would be very cool if one could click on an owlid in the selection analyzer to jump to the right node in the terminology tree... possible?it would be very cool if one could click on an owlid in the selection analyzer to jump to the right node in the terminology tree... possible?Markus KrugMarkus Krughttps://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/56More than one document in view: splitscreen?2017-07-04T12:28:37+02:00Ghost UserMore than one document in view: splitscreen?Is it possible to open more than one document? This could be helpful for comparing documents annotated by different annotators.
Are you planning to introduce such a feature - maybe via splitscreens?Is it possible to open more than one document? This could be helpful for comparing documents annotated by different annotators.
Are you planning to introduce such a feature - maybe via splitscreens?https://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/55add annotations for POSSIBLEUNIT and RANGE to ontoIE View for number attributes2017-06-26T20:28:25+02:00Joni Krebsadd annotations for POSSIBLEUNIT and RANGE to ontoIE View for number attributes... name them POSSIBLEUNIT and RANGE...
after that POSSIBLEUNIT will describe a unit that can be found in documents, multiple instances allowed
the old UNIT annotation describes the target unit in which the found units have to be conve...... name them POSSIBLEUNIT and RANGE...
after that POSSIBLEUNIT will describe a unit that can be found in documents, multiple instances allowed
the old UNIT annotation describes the target unit in which the found units have to be convertet, only one instance allowed
the RANGE annotation describes a range for a number attribute measured in a given UNITMarkus KrugMarkus Krughttps://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/53double click to highlight words2017-06-22T11:35:53+02:00Ghost Userdouble click to highlight wordsIn the newest version of the tool (June 21st), it's not possible to highlight whole words by double clicking on them. Especially while annotating named entities this would be very helpful.In the newest version of the tool (June 21st), it's not possible to highlight whole words by double clicking on them. Especially while annotating named entities this would be very helpful.https://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/52Problem with Font on Mac2017-06-14T14:33:26+02:00Ghost UserProblem with Font on Mac![Bildschirmfoto_2017-06-13_um_12.26.50](/uploads/73acc8e5d95eb6cb35c137f940bb4d1c/Bildschirmfoto_2017-06-13_um_12.26.50.png)
I have experienced shifted annotation selections on Mac. I've been working with the Font *Arial 14* to avoid...![Bildschirmfoto_2017-06-13_um_12.26.50](/uploads/73acc8e5d95eb6cb35c137f940bb4d1c/Bildschirmfoto_2017-06-13_um_12.26.50.png)
I have experienced shifted annotation selections on Mac. I've been working with the Font *Arial 14* to avoid not correct selections.https://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/51Anno Browser can only display annotation-features if they are of type "uima.t...2017-06-02T13:11:17+02:00Markus KrugAnno Browser can only display annotation-features if they are of type "uima.tcas.Annotation" in the typesystemhttps://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/50Problems annotating till the end of document (in RWView)2017-06-02T09:26:00+02:00Ghost UserProblems annotating till the end of document (in RWView)Zwei neue Fehlermeldung: Erstmals ging eine Annotation bis zum letzten Zeichen des Dokuments; die Eintragung der Annotations war nicht möglich. Folgenden zwei Fehler erschienen nacheinander:
![OutOfBoundsError](/uploads/4363badb38661235...Zwei neue Fehlermeldung: Erstmals ging eine Annotation bis zum letzten Zeichen des Dokuments; die Eintragung der Annotations war nicht möglich. Folgenden zwei Fehler erschienen nacheinander:
![OutOfBoundsError](/uploads/4363badb38661235b53dcaf2b3f4da0b/OutOfBoundsError.png)
![CursorLocationError](/uploads/c9424feae0b16f5b81e1cd193b18fb79/CursorLocationError.png)https://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/49Goldstandard analyzer should be able to compare more than 2 types2017-06-01T14:13:52+02:00Markus KrugGoldstandard analyzer should be able to compare more than 2 typesThe goldstandard analyzer is currently only capable of comparing 2 types with each other.
It should be upgraded to be able to at least display n different types. This can be done by allowing the user to create and load more than 1 mappi...The goldstandard analyzer is currently only capable of comparing 2 types with each other.
It should be upgraded to be able to at least display n different types. This can be done by allowing the user to create and load more than 1 mapping. The results of those mappings are then merged and set as input into the table. The datamodel is currently a list of annotation-pairs, this needs to be extends to be able to store arbitrary length. The rest should work as intendedhttps://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/48Allow the editor to switch between CAS-Views2017-05-31T17:06:52+02:00Markus KrugAllow the editor to switch between CAS-Viewscurrently only the initla view can be displayed. This should be implemented as a menu entrycurrently only the initla view can be displayed. This should be implemented as a menu entryhttps://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/46Illegal Argument Exception2017-05-30T11:02:01+02:00Ghost UserIllegal Argument ExceptionTool caused an error by scrolling far beyond end of text:
![IllegalArgumentException__2_](/uploads/13fc1a0150d88f58a5bc3a16b82c43b8/IllegalArgumentException__2_.png)
![IllegalArgumentException__1_](/uploads/8be54b2bd9de5219a68c8f384c67...Tool caused an error by scrolling far beyond end of text:
![IllegalArgumentException__2_](/uploads/13fc1a0150d88f58a5bc3a16b82c43b8/IllegalArgumentException__2_.png)
![IllegalArgumentException__1_](/uploads/8be54b2bd9de5219a68c8f384c67e897/IllegalArgumentException__1_.png)https://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/45SWT-Exception im RW-View2017-05-30T09:28:04+02:00Ghost UserSWT-Exception im RW-ViewException trat auf direkt nach der Neuinstallation des Programms. Ich habe ein XMI-Dokument geöffnet, das bereits Annotationen enthielt, und wechselte dann zum ersten Mal in den RW-View.
![Athen1](/uploads/0466b6615df9ba47927e8ac0649d2da...Exception trat auf direkt nach der Neuinstallation des Programms. Ich habe ein XMI-Dokument geöffnet, das bereits Annotationen enthielt, und wechselte dann zum ersten Mal in den RW-View.
![Athen1](/uploads/0466b6615df9ba47927e8ac0649d2da5/Athen1.PNG)
Das Warnungsfenster tauchte immer sofort wieder auf, wenn ich es geschlossen habe, so dass ich das Programm über den Task-Manager beendet habe.
Weitere Test deuten darauf hin, dass der Fehler mit dem XMI-Dokument zusammenhängt, da er jedes Mal auftritt, wenn dieses geöffnet wird, während sich andere Dokumente problemlos öffnen lassen.
Dies ist das Dokument: [zeit_conversationsblatt_10_6_DieAuswandererEinsder_0.txt](/uploads/c28f97e5eb189790113c266a8cdc7aab/zeit_conversationsblatt_10_6_DieAuswandererEinsder_0.txt)https://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/44String Index out of Bounds Exception im RW-View2017-05-31T16:55:22+02:00Ghost UserString Index out of Bounds Exception im RW-ViewFehlermeldung siehe angehängter Screenshot.
Der Fehler trat auf, als ich bereits mehrere Annotationen angelegt hatte und eine weitere anlegen wollte, die direkt am Textanfang begann und über mehrere Zeilen ging (blaue Markierung im Scree...Fehlermeldung siehe angehängter Screenshot.
Der Fehler trat auf, als ich bereits mehrere Annotationen angelegt hatte und eine weitere anlegen wollte, die direkt am Textanfang begann und über mehrere Zeilen ging (blaue Markierung im Screenshot). Geplante Annotation war "direct writing".
Nicht ganz sicher, wann die Exception genau auftrat, aber höchstwahrscheinlich nach dem Klicken des zweiten Buttons ("writing"), also in dem Moment, wo die Annotation erzeugt werden sollte.
![Athen_Index_out_of_bounds](/uploads/1fecf12ead4500e454fd472732fa2805/Athen_Index_out_of_bounds.PNG)https://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/43EventBroker Subscription Using java 8 Consumer<Event>2017-05-17T09:28:18+02:00Markus KrugEventBroker Subscription Using java 8 Consumer<Event>This would make many parts of the code much more readable!!This would make many parts of the code much more readable!!https://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/42TEI Compatibility for ATHEN2017-05-15T16:25:06+02:00Markus KrugTEI Compatibility for ATHENUsually in digital humanities communities, the standard of encoding meta information is using TEI-XML. The format is extremely complicated in its entirety. This feature should enable ATHEn to read and write TEI documents.
## TEI to XM...Usually in digital humanities communities, the standard of encoding meta information is using TEI-XML. The format is extremely complicated in its entirety. This feature should enable ATHEn to read and write TEI documents.
## TEI to XMI Conversion
A TEI document comes as a plain.xml. Whenever available, the user may be able to provide a xml schema additionally to the input document.
The process of converting into an .xmi would follow the following model:
1. If a schema is provided, it is converted into a UIMA Typesystem (which is an xml itself), else, the typesystem is generated by analyzing all different sorts of xml elements and their attributes. Elements will be converted into types and attributes are converted into features.
2. The resulting typesystem is merged with the existing typesystem of ATHEN
3. All XML Elements alongside their attributes are removed from the text and stored as UIMA annotations with the correct span (this will fail if the xml document has no text at all.) All annotations will be of a special type ```TEI-XML-Type``` There are xml formats (such as the TueBa/DZ xml format) that store the entire text as attributes in the ```<word> tag```
4. In the first pass through the annotations, all ```TEI-XML-Type``` annotations are about to be converted into the according type of the UIMA typesystem, this mapping is logged and is saved by the application in order to guarantee reversibility.
5. A second pass through the annotations is done and all features (which might be references to other annotations, this is why 2 passes are required) are interpreted and stored
The resulting document is stored alongside the mapping of TEI elements and attributes to UIMA Types and features.
**Note to step 5**
In this step it should be tried to find links to other annotations by either analyzing the schema or by comparing the attribute value to existing element ids.
Summarized it can be depicted here:
<img src="/uploads/281715c10e87aafb0ed8450d133a9ec3/TEItoXMI.PNG" alt="MVC of the editor and the views" style="width: 640px;" style="height: 480px;"/>
## XMI to TEI Conversion
The reverse process is a little bit harder:
1. If a previously created mapping is available we can use this and revert the process (that is as long as a schema is avilable)
2. If no mapping and no schema is available => ????
## Special functionalities
1. If we happen to have multiple documents with the same text, it should be possible to aggregate the information stored within those documents once after another and save it in a single xmi. This can then afterwards get converted to get an aggregate TEI (if problems regarding the backwards conversiona re solved)
2. Convenience method to convert annotation in athen into other types. The user needs to be able to create a mapping of types and features that get converted into each other. This would e.g. enable to primitively parse TEI documents and then convert the resulting annotations into existing types (such as the ones used in DKPro or the ones used in ATHEN)Markus KrugMarkus Krughttps://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/40Fix the caret when wrap is not activated2017-05-14T22:19:46+02:00Markus KrugFix the caret when wrap is not activatedCaret is still just chilling around ant not movingCaret is still just chilling around ant not movinghttps://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/38searchbar of terminology tree should filter by displayname2017-07-16T18:35:12+02:00Joni Krebssearchbar of terminology tree should filter by displayname... it filters by owlid now. but owl id is not what humans are looking for...... it filters by owlid now. but owl id is not what humans are looking for...Markus KrugMarkus Krughttps://gitlab2.informatik.uni-wuerzburg.de/kallimachos/Athen/-/issues/37select node type in "add child" dialog2017-07-16T18:35:13+02:00Joni Krebsselect node type in "add child" dialogit would be nice to select the desired node type of a new node in the same dialog where you enter the new name. default value should still be attribute...
you wouldnt forget to set the right node type after creation...it would be nice to select the desired node type of a new node in the same dialog where you enter the new name. default value should still be attribute...
you wouldnt forget to set the right node type after creation...Markus KrugMarkus Krug