Work To Be Done: * Add a button to the "unknown barcode" message in checkout that would bring the user to the Fast Add Framework (for consistency with the rest of Koha) o Automatically populate the barcode with the value scanned o Automatically populate the homebranch and holdingbranch with the currently logged in branch o Automatically populate the non public note to say “return the item to cataloging” * Upon save, the item will automatically be checked out the patron. How to test: * Scan a barcode that is not in your system in the check out screen * Confirm that the behavior follows the above
This is partially done, by bug 3495, which is in master So this will just extend that functionality to cover missing bits Namely o Automatically populate the barcode with the value scanned o Automatically populate the homebranch and holdingbranch with the currently logged in branch o Automatically populate the non public note to say “return the item to cataloging” * Upon save, the item will automatically be checked out the patron.
Created attachment 5073 [details] [review] Bug 6748 - Add link to fast add framework while circulating, if a barcode is not found
Created attachment 5122 [details] [review] [SIGNED-OFF] Bug 6748 - Add link to fast add framework while circulating, if a barcode is not found Signed-off-by: Nicole C. Engard <nengard@bywatersolutions.com>
This patch does not implement the portion of the requirements to add the Non-public Note indicating to return the item to cataloging. Otherwise it works very well. This particular omission is understandable, given the state of bug 4222, which can be viewed in some ways as a dependency. Marking this particular patch as Passed QA, but a followup will need to be written to implement the Note requirement, once that can be reconciled with 4222
Pushed, reset status, as needs another patch to set the non-public note, pleas test
Upon further investigation, the Fast Add framework can be added to give the non-public note a default value, which accomplishes the same end, and gives the library much more control over the nature of the message. I'm going to reset the statuses on this, and mark this as closed, since all the points of the Work To Be Done are (or can be, with a small administrative data change) met.