Redundant etymology texts

[judithek]

Information on the etymology of a lexical entry is currently stored in Sense.Definition.Statement.TextRepresentation.

This means that if we have 10 senses for a lexical entry and each of them would have
two definitions (e.g., in two languages), then the etymology text would be stored 20
times in the database.

IMHO, etymology is a property on the level of the LexicalEntry.

Original issue reported on code.google.com by chmeyer.de on 2014-10-09 09:14:36

[judithek]

(No text was entered with this change)

Original issue reported on code.google.com by chmeyer.de on 2014-10-09 09:15:58

[judithek]

I agree. 

see also ISOcat:    http://www.isocat.org/datcat/DC-221
Information on the origin of a word and the development of its meaning.

Adding etymology as attribute of lexicalEntry would be symmetric to separableParticle,
which is similar: this is also related to the meaning in the sense that it differentiates
homonyms.

Example: http://de.wiktionary.org/wiki/durchsetzen
durch#setzen Unsere Mannschaft setzte sich sogar gegen die Titelverteidiger durch.
vs
durchsetzen Wir durchsetzen in Zukunft die Betriebe unserer Konkurrenten mit Spitzeln.

This requires changing the model which involves:
1) DTD
2) java class
3) hibernate mapping

Original issue reported on code.google.com by eckle.kohler on 2014-10-09 18:08:45

• Labels added: Type-Enhancement
• Labels removed: Type-Defect