http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12851
Paola Rossi <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Paola Rossi <[email protected]> --- (In reply to Jonathan Druart from comment #1) The tag <order> is used in the email's body of ACQCLAIM and ACQCLAIM-ISSUE notices at default. But the <order> tag has not been yet defined as a markup tag for the email's body of any notice (see <http://manual.koha-community.org/3.16/en/noticesappendix.html#noticesfieldguide>). So (1) the tag <order> might be defined, and not removed from C4/Letters.pm. Otherwise, (2) the tag <order> might be removed from the email message body of two default notices above (sample_notices.sql). On /cgi-bin/koha/serials/claims.pl, a row is created for any issue-number in late, even for issue-numbers of the same biblio-serial. So "multiple" rows for the same biblio-serial might be shown in the table at the bottom of the page. Without <order> in the pattern, for all the rows koha writes a corresponding line in the message body of the email notice for serial claims. If the notice would use a pattern like f.i. the following simple one: ------------------ the following issues are in late: -Issue <<serial.serialseq>> for serial: <<biblio.title>> / <<biblio.author>> ------------------ all the issues in late could appear clearly in the mail, even in the "multiple" case. <<biblio.serial>> should be always 1 for a serial in subscription: it would be simply repeated in the mail, and its meaning would not be clear to the recipient. -- 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/
