Well, you're supposed to run open-ils.circ.title_hold.is_possible before doing open-ils.circ.holds.create, but that said using open-ils.circ.holds.test_and_create.batch is better.
I would be for deprecating open-ils.circ.holds.create in 2.10, and removing it in the next release.
A non-batch version of open-ils.circ.holds.test_and_create.batch might be good to add when you only want to do 1 hold at a time. The batch on the end may throw some developers who don't realize that a list with one entry is still a batch.
I think open-ils.circ.title_hold.is_possible should definitely stay. There are times I've used that method to find out if holds can be placed or not without actually creating the hold.
Well, you're supposed to run open-ils. circ.title_ hold.is_ possible before doing open-ils. circ.holds. create, but that said using open-ils. circ.holds. test_and_ create. batch is better.
I would be for deprecating open-ils. circ.holds. create in 2.10, and removing it in the next release.
A non-batch version of open-ils. circ.holds. test_and_ create. batch might be good to add when you only want to do 1 hold at a time. The batch on the end may throw some developers who don't realize that a list with one entry is still a batch.
I think open-ils. circ.title_ hold.is_ possible should definitely stay. There are times I've used that method to find out if holds can be placed or not without actually creating the hold.