Documentation for extended attributes is somewhat lacking, and my last patch in my previous bug report just fixed case without any extended attributes in LDAP.
Created attachment 2360 [details] [review] fix mapping of extended attribute code and ldap attributes
This approach still require additional entry in koha-conf.xml mapping like this: <JMBG is="hrEduPersonUniqueNumber_JMBG"></JMBG> It's quite easy to add code to match existing types in extended attributes to ldap attribute names directly, so that it doesn't require change in koha-conf.xml, but I can see also argumentation against it along the lines of "it's really nice to have all LDAP configuration in one place in koha-conf.xml and I like ability to rename fields".
Applied
I can't see this patch applied in current master. It would bring current LDAP implementation into fully-functional state, and still applies cleanly to master.
It is there in master already, applying the patch causes this conflict <<<<<<< HEAD my @attributes = grep{my $key=$_; any{$_ eq $key}@types;} keys %borrower; my $extended_patron_attributes; @{$extended_patron_attributes} = map { { code => $_, value => $borrower{$_} } } @attributes; ======= my @attributes = grep{my $key=$_; any{$_->{code} eq $key}@types;} keys %borrower; my $extended_patron_attributes = [ map{{code=>$_,value=>$borrower{$_}}}@attributes ]; >>>>>>> Bug 4995 - extended attributes replication from LDAP