1. For handling in-transit items, we can go with an org setting to automatically (or not) abort the transits or we can go with a new dialog that lets staff decide. Or something else... I prefer the org setting.
2. I confirmed the precat copy issue in 2.12. If the precat is still checked out, it processes OK. But, if the API has to re-check out the item it fails because it does not handle the precat checkout steps, where it makes the secondary call w/ the dummy title, etc.
In addition to this, there's a bug in the browser client that causes an early failure when processing precats. I've included a fix for that in my in-progress branch:
1. For handling in-transit items, we can go with an org setting to automatically (or not) abort the transits or we can go with a new dialog that lets staff decide. Or something else... I prefer the org setting.
2. I confirmed the precat copy issue in 2.12. If the precat is still checked out, it processes OK. But, if the API has to re-check out the item it fails because it does not handle the precat checkout steps, where it makes the secondary call w/ the dummy title, etc.
In addition to this, there's a bug in the browser client that causes an early failure when processing precats. I've included a fix for that in my in-progress branch:
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ berick/ lp1257910- missing- pieces- repairs