Add two fields to table 'Relation to foreign signs'

[ocrasborn]

1. Foreign translation equivalents (field: other_lang_transl), where we can put in any string
2. Link (field: other_lang_link), where we'd paste in a URL to anywhere

...and add those to the table in the detail view and to the search panel Relations to foreign signs. To make some space in the table, "Gloss in related language" can be cut to "Gloss" (translation)"

[vanlummelhuizen]

@ocrasborn is this issue still relevant?

[ocrasborn]

yes, it is @vanlummelhuizen

[susanodd]

See (2) in Issue description.
@Woseseltops what about the link url field wrt to the database?

[susanodd]

Here is a mockup showing the two extra fields (columns) to be added. (To see what this would look like.)

[susanodd]

The revised Relations View is awaiting review.

[susanodd]

Some time ago, the two new fields were added to the Relations View for a Gloss.
But they are not yet added to the model.

Bullet (1) of the issue is Translation Equivalents. This is perhaps relevant for Senses.
https://signbank.cls.ru.nl/dictionary/gloss_relations/4619

[vanlummelhuizen]

@susanodd What should we do with this issue?

[susanodd]

I'm not sure. It's easy to just add the fields. It probably just needs to mention senses.

I didn't implement it except in the template because at the time it would have involved a migration.
We'll assign it to @ocrasborn .

[ocrasborn]

Haha, yes, let him decide! ;-) @susanodd , no complex senses needed here for 'foreign language translations' here. Adding a URL would still be helpful. But let's make this lower priority, focusing on the senses first.