The phrasing of LOST_RETURN is confusing, the item is not always immediately returned, sometimes it is renewed for example.. I think it would be clearer to reword this to use 'FOUND' to more clearly reflect the states.. I intend to do this in the accounts handling as well as rename the _FixAccountForLostAndReturned method in C4::Circulation.
Created attachment 98457 [details] [review] Bug 24592: Reword LOST_RETURN to LOST_FOUND This patch updates the wording in the 'lost and found' process to more closely reflect what the process is achieving by replacing 'RETURNED' with 'FOUND'
Created attachment 98458 [details] [review] Bug 24592: Database Update
Created attachment 98481 [details] [review] Bug 24592: Reword LOST_RETURN to LOST_FOUND This patch updates the wording in the 'lost and found' process to more closely reflect what the process is achieving by replacing 'RETURNED' with 'FOUND' Test plan: 1) Grep codebase for _FixAccountForLostAndReturned and note there are no longer any instanced of it. 2) Run t/db_dependent/Circulation.t and note it passes 3) Test returning/renewing an item that has been marked as lost and note the updated values in the accountlines now use LOST_FOUND as credit_type_code and 'FOUND' as the status for the 'LOST' fee (debit_type_code 'LOST')
Created attachment 98482 [details] [review] Bug 24592: Database Update
Created attachment 98643 [details] [review] Bug 24592: Database Update
Created attachment 98644 [details] [review] Bug 24592: Reword LOST_RETURN to LOST_FOUND This patch updates the wording in the 'lost and found' process to more closely reflect what the process is achieving by replacing 'RETURNED' with 'FOUND' Test plan: 1) Grep codebase for _FixAccountForLostAndReturned and note there are no longer any instanced of it. 2) Run t/db_dependent/Circulation.t and note it passes 3) Test returning/renewing an item that has been marked as lost and note the updated values in the accountlines now use LOST_FOUND as credit_type_code and 'FOUND' as the status for the 'LOST' fee (debit_type_code 'LOST')
Created attachment 98680 [details] [review] Bug 24592: Database Update Signed-off-by: David Nind <david@davidnind.com>
Created attachment 98681 [details] [review] Bug 24592: Reword LOST_RETURN to LOST_FOUND This patch updates the wording in the 'lost and found' process to more closely reflect what the process is achieving by replacing 'RETURNED' with 'FOUND' Test plan: 1) Grep codebase for _FixAccountForLostAndReturned and note there are no longer any instanced of it. 2) Run t/db_dependent/Circulation.t and note it passes 3) Test returning/renewing an item that has been marked as lost and note the updated values in the accountlines now use LOST_FOUND as credit_type_code and 'FOUND' as the status for the 'LOST' fee (debit_type_code 'LOST') Signed-off-by: David Nind <david@davidnind.com>
Here is an updated test plan (I had to work out how to do some of the things, so I hope it is useful to others and what was intended to check): 1) Apply the patch and run the database update (perl installer/data/mysql/updatedatabase.pl) 2) Grep th codebase for _FixAccountForLostAndReturned and note there are no longer any instanced of it (grep -r1 "_FixAccountForLostAndReturned" koha) 3) Run t/db_dependent/Circulation.t and note it passes 4) For a patron: - Check out an item (Circulation > Check out) - Create a manual invoice for the item using the 'Lost item' type (Patrons > [Account for patron] > Accounting > Create manual invoice > Enter the barcode and amount) - Edit the record for the item and change the 'Lost status' to 'Lost' (From the list of transactions click on the barcode, and change the 'Lost status' to 'Lost' and then 'clcik 'Set status') - Check in the lost item (Circulation > Check in) - A message should pop up saying 'Item was lost, now found.....' - Check the transactions for the patron: there should now be a transaction with a refund, the account type will say 'Lost item fee refund', and in the description it will say 'Item found...' 5) Check the database to see the changes: - koha-mysql kohadev - Use the query 'select * from accountlines' - For the original manual invoice the debit_type_code will show as 'LOST' and the status will show as 'FOUND' - For the transactions to reverse the lost item fee the credit_type_code will show as "LOST_FOUND'
Thanks for testing David :)
*** Bug 6383 has been marked as a duplicate of this bug. ***
Created attachment 98852 [details] [review] Bug 24592: Database Update Signed-off-by: David Nind <david@davidnind.com> Signed-off-by: Joonas Kylmälä <joonas.kylmala@helsinki.fi>
Created attachment 98853 [details] [review] Bug 24592: Reword LOST_RETURN to LOST_FOUND This patch updates the wording in the 'lost and found' process to more closely reflect what the process is achieving by replacing 'RETURNED' with 'FOUND' Test plan: 1) Grep codebase for _FixAccountForLostAndReturned and note there are no longer any instanced of it. 2) Run t/db_dependent/Circulation.t and note it passes 3) Test returning/renewing an item that has been marked as lost and note the updated values in the accountlines now use LOST_FOUND as credit_type_code and 'FOUND' as the status for the 'LOST' fee (debit_type_code 'LOST') Signed-off-by: David Nind <david@davidnind.com> Signed-off-by: Joonas Kylmälä <joonas.kylmala@helsinki.fi>
Nice work everyone! Pushed to master for 20.05
enhancement not backported to 19.11.x