https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23292
--- Comment #10 from Sally <sally.hea...@cheshiresharedservices.gov.uk> --- (In reply to Andreas Hedström Mace from comment #7) > I still see Johannas approach as the more valid one, especially concerning > issues of data privacy. For Sallys use case, I would suggest changing the > approach: adding holds information to the transfer slips using the IF > statement in the TT syntax, rather than keeping todays behaviour. Thanks Katrin - making it optional would be a good solution. Andreas - as long as our workflow can remain the same (it is vital that staff packing and unpacking items in transit can differentiate on the printed slip between low and high priority transfers - i.e. ordinary returns vs items on hold), I don't mind how we approach this. ...but I can't see how to implement your suggestion of using TransferSlip instead of HoldSlip? The two notices don't share the same object variables - hold and borrower aren't available in TransferSlip, so how would we identify something as being on hold? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list Koha-bugs@lists.koha-community.org https://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/