[Koha-bugs] [Bug 20307] Language overlay for authorized values

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20307

--- Comment #44 from Jonathan Druart <jonathan.druart at bugs.koha-community.org> ---
(In reply to Katrin Fischer from comment #40)
> I have problems with adding end editing of translations:
> 
> 1) Adding translations the same time as adding a new authorised value
> doesn't work. The first time you try, it seems to save, but doesn't display
> the values later. And the second time you try, it claims values already
> exist. 
> I think the easiest way for now would be to not display the translate links
> when adding, only on editing.

Indeed, I removed the links on adding a new AV or itemtype.

> 2) The entity shown in the table of translations is "avs" - not sure if this
> is a code or should be translatable? It might not be understood well in
> other context.

It's an internal code, I have renamed it anyway.

> 3) After adding some values and translations to TERM I have switched to
> DEPARTMENT. Adding an OPAC description translation worked, but now I get an
> error when I try to add a staff translation:
> 
> DBD::mysql::st execute failed: Duplicate entry 'avs-Department1-de-DE' for
> key 'entity_code_lang' [for Statement "INSERT INTO `localization` ( `code`,
> `entity`, `interface`, `lang`, `translation`) VALUES ( ?, ?, ?, ?, ? )" with
> ParamValues: 0="Department1", 1="avs", 2="intranet", 3="de-DE", 4="depds"]
> at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1836.
> Duplicate ID at /usr/share/perl5/Exception/Class/Base.pm line 88
> 	Exception::Class::Base::throw('Koha::Exceptions::Object::DuplicateID',
> 'error', 'Duplicate ID', 'duplicate_id', 'entity_code_lang') called at
> /home/vagrant/kohaclone/Koha/Object.pm line 160
> 
> I am not yet sure why this happens, my table looks like this:
> 
> +-----------------+-----------+-----------+-------------+-------+------------
> -+
> | localization_id | entity    | interface | code        | lang  |
> translation |
> +-----------------+-----------+-----------+-------------+-------+------------
> -+
> |               1 | avs       | opac      |             | de-DE | 2019d     
> |
> |               2 | avs       | opac      |             | en    | test      
> |
> |               3 | avs       | intranet  | 2019        | de-DE | 2019d     
> |
> |               5 | avs       | intranet  | 2019        | en    | t         
> |
> |               6 | itemtypes | NULL      | BK          | de-DE | Bücher    
> |
> |               8 | avs       | opac      | Department1 | de-DE | dep_do    
> |
> +-----------------+-----------+-----------+-------------+-------+------------
> -+
> 
> 4) Looking at the db structure: We know the code and that it is an
> authorised value, but we don't know the category! I think this is a mistake.
> Not always the tanslation for the same code is the same. Think about the
> numeric ones like Damaged, Lost...

Indeed, big design issue. Thanks Katrin!
It should be fixed now.

-- 
You are receiving this mail because:
You are watching all bug changes.