Default hold transit slip should not include patron information

[Blake GH]

It's been brought to our attention that courier services could potentially violate patron privacy while items are in transit. We should not include patron information on the slips being put into transit.

[Blake GH (bmagic)]

Branch here:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/blake/LP1735847_Default_hold_transit_slip_should_not_include_patron_information

[Blake GH (bmagic)]

I went ahead and committed the change to the xul client as well. Same git link above.

[Michele Morgan (mmorgan)]

The fix changes the hold_transit_slip from this:

This item needs to be routed to
BR2
Example Branch 2
BR2 - Holds and ILL
234 Side St.
Anywhere, GA 30304

Barcode: G880510001549
Title: Harry Potter and the goblet of fire Author: Rowling, J. K.
Hold for patron Anderson, Leon
Barcode: 99999376864
Notify by phone: 9

Request Date: 9/12/2018 1:15 PM
Slip Date: 9/12/2018 1:16 PM
Printed by Administrator at BR1

To this:

This item needs to be routed to
BR2
Example Branch 2
BR2 - Holds and ILL
234 Side St.
Anywhere, GA 30304

Barcode: G880510001549
Title: Harry Potter and the goblet of fire Author: Rowling, J. K.
Hold for patron 99999376864

Request Date: 9/12/2018 11:37 AM
Slip Date: 9/12/2018 1:25 PM
Printed by Administrator at BR1

I'm just wondering if it's necessary to have the patron's barcode printed or if that can be removed as well.

[Dan Pearl (dpearl)]

Works as advertised.

user/dpearl/LP1735847_Default_hold_transit_slip_should_not_include_patron_information-signoff

[Jason Boyer (jboyer)]

Given that this is a step in the right direction I've gone ahead and committed these changes to 3.1 to master. Another thing to consider in the future re: Michele's comments is whether we want to have the requesting patron's information even made available to the transit template at all. That's a discussion we can have in another bug.

[Jason Boyer (jboyer)]

Forgot to mention, thanks Blake and Dan!

[Galen Charlton (gmc)]

I think making it impossible to include the requester's information might be a step too far, as there's the potential for internal paging within a corporate library or the like to need it.