Remove unnecessary Capture Holds interface

[Terran McCanna]

The Capture Holds interface appears to essentially duplicate the Check In interface. A quick comparison only reveals that the only obvious differences are:

1) The Suppress Holds and Transits checkin modifier is not displayed on the Capture Holds interface.
2) The Auto-print Hold and Transit Slips checkin modifier is set by default on the Capture Holds interface.

Unless there is something I am missing, I don't think that these differences are enough to warrant maintaining a separate interface. I propose:

1) Set the Auto-print Hold and Transit Slips checkin modifier by default on the Checkin interface.
2) Remove the Capture Holds interface.

Adding needsdiscussion tag for feedback.

[Jennifer Pringle (jpringle-u)]

I agree that we don't need a separate Capture Holds interface.

I think our libraries that want to auto-print slips already have that set up on check in anyways for when holds and transits are captured through regular check in.

[Diane Disbro (ddisbro)]

I agree with J. Pringle that Auto-print doesn't need to be the checkin default. Those who want to use it, already know to select it. Those who don't want to use it, leave it unchecked.

[Gina Monti (gmonti90)]

+1 for consolidating. Not to compare us to proprietary systems, but in iii, for example, I just used the Check-In option for all of these and I think that training has turned me away from the using Capture Holds.

[Terran McCanna (tmccanna)]

Adding that I have literally never used the Capture Holds interface except during testing, and when we do circ training sessions for library staff, we have them use the Check In interface for everything.

[Benjamin Kalish (bkalish)]

I also have never used this interface. Can anyone speak to the history of this interface and why it was created?