http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12404
--- Comment #15 from Frédéric Demians <[email protected]> --- (In reply to Jonathan Druart from comment #14) > It's easier to manipulate hashref than arrayref in this case. If you want to > access to the $b subfield, you don't need to process all subfields. Could > you give me an where this structure would be a problem for a CSV export? I agree. I have seen TT syntax you can get: fields.245, fields.245.a. And then [% FOREACH %] on hashref keys... It's elegant, but it is also a trap. In MARC21, you can have this kind of title field: 245 14 $a The phonics basic skills workbook. $n Part 1, $p Reading readiness $h [videorecording] : $b preparing for kindergarten. which should be rendered: The phonics basic skills workbook. Part 1, Reading readiness [videorecording] : preparing for kindergarten. With your field representation, you loose the subfield order: a, n, p, h, and b. There is chance a TT construction will try to put $b just after $a, which is wrong. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
