A group of librarians have been brainstorming about claimed returns in Koha. They think this would be a good list of features for a claims returned system in Koha: * Add a system preference to flag which lost status is "Claims returned". Not setting this pref would disable the feature. * Add ability to mark item as "Claims returned" * Add the ability to mark an item as claims returned from the checkouts table on the checkouts and patron details pages * This functionality would operate in the same way checkins and renewals do. * It may be better to slim down to one column of checkboxes for all three functions ( that is, one at a time with one set of checkboxes ) * The ability mark an item as "Claims returned" from the item details would be disabled when the feature is enabled. All claims returned marking would happen through the checkouts table. * Charge or don't charge for claims returned * Some libraries charge the lost fee on claimed returns, some don't. * Add system preference to ask ‘charge’, ‘don’t charge’, or ‘ask for confirmation’ when marking an item claimed returned * Some libraries want to alerted of repeat offenders. * Add a sys pref to offer an option to block a patron, or alert staff somehow, after a set number of claimed returns. * This will be a running total over the lifetime of the patron, not the current number of outstanding claimed returns. * There will need to be a table that stores basic information about the item on patron’s record so you can track how many times they’ve said ‘i returned that’ * This allows us to track claimed returns even for returned and deleted items * This data will display on a new tab on the patron record ( moremember.pl ) for "claims returned" items * Will store the status so we know if the claim is open or resolved * ex. [title 1] / checked out {date} / claimed {date} / not returned / notes * Remove item from patron's current checkouts on marking "claims returned" ( e.g. current lost behavior ) * Will stop fines from continuing to accrue for said item * show as missing in the opac and claimed returned in the staff client ( e.g. current lost behavior, no change needed ) * Be able to mark item as ‘found’ from claimed tab if item happens to be found ( using standard 'found' behavior Koha already has ) * Offer options of “returned by patron” or “found in library” in a pull down to the side of every item that has been claimed. * next to each claimed item have a ‘notes’ field. Should be in line editable for ease of use * Claimed items should be easily distinguishable on staff side (compared to other types of lost items) on patron check out under ‘Attention’ so alert ‘Patron has claimed returns’ that links to the ‘Claimed’ tab below ( in a similar fashion to the current restrictions system )
Seeking Co-sponsors: http://devs.bywatersolutions.com/projects/claimed-returned/
How are fines/fees taken into account with this action? Will associated fines be removed if claimed returned? Or will they be removed if marked as found? Will there be a preference for this?
*** Bug 4236 has been marked as a duplicate of this bug. ***
*** Bug 4241 has been marked as a duplicate of this bug. ***
(In reply to Christopher Brannon from comment #2) > How are fines/fees taken into account with this action? Will associated > fines be removed if claimed returned? Or will they be removed if marked as > found? Will there be a preference for this? I think this covers your first questions: >Add system preference to ask ‘charge’, ‘don’t charge’, or ‘ask for confirmation’ when marking an item claimed returned As to your second, I think we ought to treat it like we do lost items via the system preference RefundLostItemFeeOnReturn Perhaps a system pref: RefundClaimReturnonLocate?
(In reply to Benjamin Daeuber from comment #5) > (In reply to Christopher Brannon from comment #2) > > How are fines/fees taken into account with this action? Will associated > > fines be removed if claimed returned? Or will they be removed if marked as > > found? Will there be a preference for this? > > I think this covers your first questions: > > >Add system preference to ask ‘charge’, ‘don’t charge’, or ‘ask for confirmation’ when marking an item claimed returned This is good. Since we have started making the refund library specific, would you consider preferences under each library? > As to your second, I think we ought to treat it like we do lost items via > the system preference RefundLostItemFeeOnReturn > > Perhaps a system pref: RefundClaimReturnonLocate? As mentioned in my response above, this functionality was moved to the library configuration as individual preferences for each library. I would say it needs to be there.
I see from http://devs.bywatersolutions.com/2016/11/30/Claimed-Returned/ this is fully funded but nothing seems to have happened. Is there an update on this? It would be a great feature.
Could we please get an update on this bug?
We are also interested in an update of this enhancement. Once a request is funded what is the procedure for moving an option into development. I don't believe all the libraries in our group are interested in this feature so it would be good if each library could decide for itself.
For everyone asking about that status of this work, I just want to let you know I'm working on it!
*** Bug 20210 has been marked as a duplicate of this bug. ***
(In reply to Laura Horgan from comment #9) > We are also interested in an update of this enhancement. Once a request is > funded what is the procedure for moving an option into development. I don't > believe all the libraries in our group are interested in this feature so it > would be good if each library could decide for itself. Hi Laura, The ability to use claims returned at a branch specific level is not part of this development and is outside the scope of this development. This feature is intended to be global and turned on or off for the system through system preferences. joy
Kyle you mentioned you were working on it in Feb. Is it slated to be part of a specific future release?
This would also be appreciated at PCCLD. We all the options mentioned in http://devs.bywatersolutions.com/2016/11/30/Claimed-Returned/.
Created attachment 92407 [details] [review] Bug 14697: Update database
Created attachment 92408 [details] [review] Bug 14697: Add new schema file
Created attachment 92409 [details] [review] Bug 14697: Extend and enhance "Claims returned" lost status This adds a "Claims returned" feature that extends and enhances the claims returned lost status Test Plan: 1) Create a "Claims Returned" lost value 2) Create some RETURN_CLAIM_RESOLUTION authorized values 3) Set ClaimReturnedLostValue 4) Set ClaimReturnedChargeFee 5) Set ClaimReturnedWarningThreshold 6) Create some checkouts 7) Claim some returns 8) Verify ClaimReturnedChargeFee works with all 3 options 9) Verify ClaimReturnedWarningThreshold shows a warning once the threshold has been exceeded 10) Edit notes on a claim 11) Resolve a claim 12) Delete a claim
Created attachment 92410 [details] [review] Bug 14697: [DO NOT PUSH] Update Schema Files
There is what looks like a minor conflict in the third patch. I get an error with updatedatabase: DEV atomic update: bug_14697.perl DBD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ') VALUES ( 'RETURN_CLAIM_RESOLUTION', 'RET_BY_PATR' at line 1 [for Statement " INSERT INTO `authorised_values` ( category, authorised_value, lib, ) VALUES ( 'RETURN_CLAIM_RESOLUTION', 'RET_BY_PATRON', 'Returned by patron' ), ( 'RETURN_CLAIM_RESOLUTION', 'FOUND_IN_LIB', 'Found in library', ); And the "Update Schema Files" patch didn't apply.
Created attachment 92962 [details] [review] Bug 14697: Update database
Created attachment 92963 [details] [review] Bug 14697: Add new schema file
Created attachment 92964 [details] [review] Bug 14697: Extend and enhance "Claims returned" lost status This adds a "Claims returned" feature that extends and enhances the claims returned lost status Test Plan: 1) Create a "Claims Returned" lost value 2) Create some RETURN_CLAIM_RESOLUTION authorized values 3) Set ClaimReturnedLostValue 4) Set ClaimReturnedChargeFee 5) Set ClaimReturnedWarningThreshold 6) Create some checkouts 7) Claim some returns 8) Verify ClaimReturnedChargeFee works with all 3 options 9) Verify ClaimReturnedWarningThreshold shows a warning once the threshold has been exceeded 10) Edit notes on a claim 11) Resolve a claim 12) Delete a claim
Created attachment 92965 [details] [review] Bug 14697: [DO NOT PUSH] Update Schema Files
I still get this error: (In reply to Owen Leonard from comment #19) > I get an error > with updatedatabase: > > DEV atomic update: bug_14697.perl > DBD::mysql::db do failed: You have an error in your SQL syntax; check the > manual that corresponds to your MariaDB server version for the right syntax > to use near ') > VALUES > ( > 'RETURN_CLAIM_RESOLUTION', 'RET_BY_PATR' at line 1 [for > Statement " > INSERT INTO `authorised_values` ( category, authorised_value, lib, ) > VALUES > ( > 'RETURN_CLAIM_RESOLUTION', 'RET_BY_PATRON', 'Returned by patron' > ), > ( > 'RETURN_CLAIM_RESOLUTION', 'FOUND_IN_LIB', 'Found in library', > ); >
Created attachment 93005 [details] [review] Bug 14697: Update database
Created attachment 93006 [details] [review] Bug 14697: Add new schema file
Created attachment 93007 [details] [review] Bug 14697: Extend and enhance "Claims returned" lost status This adds a "Claims returned" feature that extends and enhances the claims returned lost status Test Plan: 1) Create a "Claims Returned" lost value 2) Create some RETURN_CLAIM_RESOLUTION authorized values 3) Set ClaimReturnedLostValue 4) Set ClaimReturnedChargeFee 5) Set ClaimReturnedWarningThreshold 6) Create some checkouts 7) Claim some returns 8) Verify ClaimReturnedChargeFee works with all 3 options 9) Verify ClaimReturnedWarningThreshold shows a warning once the threshold has been exceeded 10) Edit notes on a claim 11) Resolve a claim 12) Delete a claim
Created attachment 93008 [details] [review] Bug 14697: [DO NOT PUSH] Update Schema Files
Got these error messages when we tried opening a patron to do some checkouts. Template process failed: undef error - Can't locate object method "return_claims_borrowernumbers" via package "Koha::Schema::Result::Borrower" at /kohadevbox/koha/Koha/Patron.pm line 1083. at /kohadevbox/koha/C4/Templates.pm line 122 in C4::Templates::output at /kohadevbox/koha/C4/Templates.pm line 122 119: 120: my $data; 121: binmode( STDOUT, ":utf8" ); 122: $template->process( $self->filename, $vars, \$data ) 123: || die "Template process failed: ", $template->error(); 124: return $data; 125: } in (eval) at /kohadevbox/koha/members/moremember.pl line 214 211: relatives_borrowernumbers => \@relatives, 212: ); 213: 214: output_html_with_http_headers $input, $cookie, $template->output; in CGI::Compile::ROOT::kohadevbox_koha_members_moremember_2epl::__ANON__ at /kohadevbox/koha/members/moremember.pl line 2 1: #!/usr/bin/perl 2: 3: # Copyright 2000-2002 Katipo Communications 4: # Copyright 2010 BibLibre 5: # Copyright 2014 ByWater Solutions
Created attachment 93012 [details] [review] Bug 14697: Update database
Created attachment 93013 [details] [review] Bug 14697: Add new schema file
Created attachment 93014 [details] [review] Bug 14697: Extend and enhance "Claims returned" lost status This adds a "Claims returned" feature that extends and enhances the claims returned lost status Test Plan: 1) Create a "Claims Returned" lost value 2) Create some RETURN_CLAIM_RESOLUTION authorized values 3) Set ClaimReturnedLostValue 4) Set ClaimReturnedChargeFee 5) Set ClaimReturnedWarningThreshold 6) Create some checkouts 7) Claim some returns 8) Verify ClaimReturnedChargeFee works with all 3 options 9) Verify ClaimReturnedWarningThreshold shows a warning once the threshold has been exceeded 10) Edit notes on a claim 11) Resolve a claim 12) Delete a claim
Created attachment 93015 [details] [review] Bug 14697: [DO NOT PUSH] Update Schema Files
Created attachment 93017 [details] [review] Bug 14697: Show an item has unresolved claims on checkin
Created attachment 93038 [details] [review] Bug 14697: Update database Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com>
Created attachment 93039 [details] [review] Bug 14697: Add new schema file Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com>
Created attachment 93040 [details] [review] Bug 14697: Extend and enhance "Claims returned" lost status This adds a "Claims returned" feature that extends and enhances the claims returned lost status Test Plan: 1) Create a "Claims Returned" lost value 2) Create some RETURN_CLAIM_RESOLUTION authorized values 3) Set ClaimReturnedLostValue 4) Set ClaimReturnedChargeFee 5) Set ClaimReturnedWarningThreshold 6) Create some checkouts 7) Claim some returns 8) Verify ClaimReturnedChargeFee works with all 3 options 9) Verify ClaimReturnedWarningThreshold shows a warning once the threshold has been exceeded 10) Edit notes on a claim 11) Resolve a claim 12) Delete a claim Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com>
Created attachment 93041 [details] [review] Bug 14697: [DO NOT PUSH] Update Schema Files Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com>
Created attachment 93042 [details] [review] Bug 14697: Show an item has unresolved claims on checkin Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com>
Jessie Zario and I tested this at koha-US 2019. Lisette
Created attachment 93061 [details] [review] Bug 14697: Update database Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 93062 [details] [review] Bug 14697: Add new schema file Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 93063 [details] [review] Bug 14697: Extend and enhance "Claims returned" lost status This adds a "Claims returned" feature that extends and enhances the claims returned lost status Test Plan: 1) Create a "Claims Returned" lost value 2) Create some RETURN_CLAIM_RESOLUTION authorized values 3) Set ClaimReturnedLostValue 4) Set ClaimReturnedChargeFee 5) Set ClaimReturnedWarningThreshold 6) Create some checkouts 7) Claim some returns 8) Verify ClaimReturnedChargeFee works with all 3 options 9) Verify ClaimReturnedWarningThreshold shows a warning once the threshold has been exceeded 10) Edit notes on a claim 11) Resolve a claim 12) Delete a claim Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 93064 [details] [review] Bug 14697: [DO NOT PUSH] Update Schema Files Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 93065 [details] [review] Bug 14697: Show an item has unresolved claims on checkin Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 93040 [details] [review] [review] Bug 14697: Extend and enhance "Claims returned" lost status This adds a "Claims returned" feature that extends and enhances the claims returned lost status Test Plan: 1) Create a "Claims Returned" lost value 2) Create some RETURN_CLAIM_RESOLUTION authorized values 3) Set ClaimReturnedLostValue 4) Set ClaimReturnedChargeFee 5) Set ClaimReturnedWarningThreshold 6) Create some checkouts 7) Claim some returns 8) Verify ClaimReturnedChargeFee works with all 3 options 9) Verify ClaimReturnedWarningThreshold shows a warning once the threshold has been exceeded 10) Edit notes on a claim 11) Resolve a claim 12) Delete a claim Signed-off-by: Jessica Zairo <jzairo@bywatersolutions.com>
This route: POST /return_claims/claim/{item_id} { notes: ..., created_by: ..., charge_lost_fee: ... } should really be POST /return_claims { item_id: ..., notes: ..., created_by: ..., charge_lost_fee: ... }
Created attachment 93952 [details] [review] Bug 14697: Update database Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 93953 [details] [review] Bug 14697: Add new schema file Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 93954 [details] [review] Bug 14697: Extend and enhance "Claims returned" lost status This adds a "Claims returned" feature that extends and enhances the claims returned lost status Test Plan: 1) Create a "Claims Returned" lost value 2) Create some RETURN_CLAIM_RESOLUTION authorized values 3) Set ClaimReturnedLostValue 4) Set ClaimReturnedChargeFee 5) Set ClaimReturnedWarningThreshold 6) Create some checkouts 7) Claim some returns 8) Verify ClaimReturnedChargeFee works with all 3 options 9) Verify ClaimReturnedWarningThreshold shows a warning once the threshold has been exceeded 10) Edit notes on a claim 11) Resolve a claim 12) Delete a claim Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 93955 [details] [review] Bug 14697: Show an item has unresolved claims on checkin Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 93956 [details] [review] Bug 14697: Move /return_claims/claim to /return_claims
Created attachment 93957 [details] [review] Bug 14697: [DO NOT PUSH] Update Schema Files
Created attachment 93959 [details] [review] Bug 14697: Don't unbless claims before rendering, it's done automatically
Sponsored-by: lines needed pretty please ;)
(In reply to Martin Renvoize from comment #55) > Sponsored-by: lines needed pretty please ;) Will do, sponsor is North Central Regional Library System
Created attachment 94842 [details] [review] Bug 14697: Update database This patch introduces the new table and related sysprefs. Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com> Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 94843 [details] [review] Bug 14697: Add new schema file Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com> Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 94844 [details] [review] Bug 14697: Introduce Koha::Checkouts::ReturnClaim(s) This patch introduces the Koha::Object(s)-derived classes for handling return claims. Tests are added to cover the overloaded ->store method, and domain-specific exceptions are added as well. To test: 1. Apply this patches 2. Run: $ kshell k$ prove t/db_dependent/Koha/Checkouts/ReturnClaim.t => SUCCESS: Tests pass! Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 94845 [details] [review] Bug 14697: Add return claim handling to AddReturn This adds the ability to alert a librarian of an item claimed as returned is actually returned. Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 94846 [details] [review] Bug 14697: Add Koha::Checkout->claim_returned Adds the ability to generate a return claim from a Checkout object. Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 94847 [details] [review] Bug 14697: Add Koha::Patron->return_claims Adds the ability to get a list of a patron's return claims directly from the Patron object. Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 94848 [details] [review] Bug 14697: Add routes to handle return claims This patch adds the /return_claims route to add new return claims, and then routes to updates notes and the resolution code. To test: 1. Apply this patches 2. Run: $ kshell k$ prove t/db_dependent/api/v1/return_claims.t => SUCCESS: Tests pass! 3. Sign off :-D Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 94849 [details] [review] Bug 14697: Enhance the return claims feature [FIXME] This adds a "Claims returned" feature that extends and enhances the claims returned lost status. To use this feature, a new LOST status to represent an item claimed as returned needs to be created. The value of this LOST authorised value should be set in the new syspref ClaimReturnedLostValue. Setting this system preference turns on the feature. Once the feature is enabled, you should be able to mark checked out items as return claims from the checkout and patron details pages, and also modify them from the new claims tab on those pages. Returning a claimed item will notify the librarian that the item in question has a claim on it. Setting the ClaimReturnedWarningThreshold will add an alert to make librarians aware that this patron has many return claims on the patron's record. Test Plan: 1) Create a "Claims Returned" lost value 2) Create some RETURN_CLAIM_RESOLUTION authorized values 3) Set ClaimReturnedLostValue 4) Set ClaimReturnedChargeFee 5) Set ClaimReturnedWarningThreshold 6) Create some checkouts 7) Claim some returns 8) Verify ClaimReturnedChargeFee works with all 3 options 9) Verify ClaimReturnedWarningThreshold shows a warning once the threshold has been exceeded 10) Edit notes on a claim 11) Resolve a claim 12) Delete a claim Sponsored-by: North Central Regional Library System Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 94850 [details] [review] Bug 14697: Schema updates Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 94851 [details] [review] Bug 14697: (follow-up) Rely on the UNIQUE constraint and return 409 for issue_id This patch avoids querying the DB for an already existing Koha::Checkouts::ReturnClaim with the same issue_id, now that there's a UNIQUE constraint on it. Also, 409 should be returned instead. Tests added for this changes. To test: - Apply this patch - Run: $ kshell k$ prove t/db_dependent/api/v1/return_claims.t => SUCCESS: tests pass! Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 94852 [details] [review] Bug 14697: Make controller methods rely on the stashed user This patch adjusts the return values and HTTP status codes, as well as removing the use of C4::Context->userenv. It also makes the date calculation happen on the DB engine in the case of resolving the claim. Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 94853 [details] [review] Bug 14697: (QA follow-up) Organize tests in subtests This patch organizes the tests better, and adds some more. Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 94854 [details] [review] Bug 14697: (QA follow-up) Add missing AV category Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io> Signed-off-by: Andrew Fuerste-Henry <andrew@bywatersolutions.com> Signed-off-by: Lisette Scheer <lisetteslatah@gmail.com>
Created attachment 94857 [details] [review] Bug 14697: (QA follow-up) Restore FK on issue_id and adjust tests This patch reintroduces the FK constraint on issue_id. The tests are adjusted to reflect the UNIQUE constraint we also added. Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Created attachment 94877 [details] [review] Bug 14697: (follow-up) Add auth values to the sample data Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Good job Kyle. I would love to see the resolution types be outside of AVs, but that's really out of the scope of this bug now, as this is the way things are actually done in Koha so far.
Created attachment 94878 [details] [review] Bug 14697: (QA follow-up) Remove tab chars Signed-off-by: Josef Moravec <josef.moravec@gmail.com>
(In reply to Tomás Cohen Arazi from comment #72) > Good job Kyle. I would love to see the resolution types be outside of AVs, > but that's really out of the scope of this bug now, as this is the way > things are actually done in Koha so far. Agreed.. would be lovely to see the AV's system tidied up a little.. I think things like this are somewhat misleading to have as AV's (This feature does not allow one to specify per branch values, but the AV system still exposes that.. for example). But, that's certainly not inside the scope of this bug. Great to see such a team effort !
Nice work! Pushed to master for 19.11.00
Added sponsor details to follow-up commit
Maybe this Wiki entry could be updated, or deleted? https://wiki.koha-community.org/wiki/Claimed_Returned_RFC
Typo in checkouts.js 903 let title = `<a class="return-claim-title strong" href="/cgi-bin/koha/circ/request-rcticle.pl?biblionumber=[% rc.checkout.item.biblionumber | html %]">
Also, there are several strings in checkouts.js that is not translatable.
(In reply to Jonathan Druart from comment #79) > Typo in checkouts.js > > 903 let title = `<a class="return-claim-title > strong" href="/cgi-bin/koha/circ/request-rcticle.pl?biblionumber=[% > rc.checkout.item.biblionumber | html %]"> See bug 24727.
(In reply to Jonathan Druart from comment #80) > Also, there are several strings in checkouts.js that is not translatable. Reported on bug 24783.