[Koha-bugs] [Bug 17005] REST API: add routes to list checkouts history

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17005

Jiri Kozlovsky <mail at jkozlovsky.cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #53851|0                           |1
        is obsolete|                            |

--- Comment #4 from Jiri Kozlovsky <mail at jkozlovsky.cz> ---
Created attachment 53852
  -->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=53852&action=edit
Bug 17005: REST API: add routes to list checkouts history

GET /checkouts/history                                 (get all old_issues'
issue_id)
GET /checkouts/history?borrowernumber={borrowernumber} (get all borrower's
old_issues' issue_id)
GET /checkouts/history/{checkout_id}                   (get old_issue)

+ unit tests in t/db_dependent/api/v1/checkoutshistory.t

Test plan:
1. Open a browser tab on Koha staff and log in (to create CGISESSID
   cookie). You should have permission circulate_remaining_permissions.
2. Go to http://yourlibrary/api/v1/checkouts/history?borrowernumber=XXX
   (replace XXX with a borrowernumber that has some checkouts history)
   and check you receive all the issues from patron's history
3. Go to http://yourlibrary/api/v1/checkouts/history/YYY (replace YYY
   with an existing checkout id) and check you receive correct data
4. Run unit tests in t/db_dependent/api/v1/checkoutshistory.t

Now the endpoint with borrowernumber does not return all the details
from within the old issues, but only their issue_id. This is made in
order to enhance API performance. E.g. VuFind can retrieve all the
issue_ids & use AJAX to query details about those, so user sees how the
details come up one by one & does not have to wait for all of them at
once (could be very long with really old users)

In order to get issue details, use the endpoint with the checkout_id.

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.