Back to bug 37640
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| aleisha | 2024-08-13 23:20:00 UTC | Status | NEW | ASSIGNED |
| Sponsorship status | --- | Sponsored | ||
| Assignee | koha-bugs | aleisha | ||
| aleisha | 2024-08-14 04:15:38 UTC | Status | ASSIGNED | Needs Signoff |
| aleisha | 2024-08-14 04:19:49 UTC | Text to go in the release notes | , Koha will identify the patron using a provided cardnumber and not match on borrowernumber at all. This is useful in cases where organisations may want to use the API endpoints to do patron actions, but don't have the borrowernumber This enhancement adds a new system preference RESTPatronIDField. It is set to borrowernumber by default | |
| Patch complexity | --- | Small patch | ||
| Text to go in the release notes | , as this is a unique ID generated within Koha. Note: it's possible that giving a borrowernumber when the API endpoint is expecting a cardnumber will still return results, to support the standard behaviour of providing a borrowernumber to the Koha REST API endpoints to identify a patron. When the syspref is set to cardnumber, and vice versa - if your cardnumber is an integer and happens to also be a borrowernumber. It's important in this case that only one or the other is used to ensure expected results. |
|||
| dcook | 2024-08-14 05:54:39 UTC | CC | dcook | |
| martin.renvoize | 2024-08-14 07:34:59 UTC | CC | martin.renvoize | |
| martin.renvoize | 2024-08-14 07:36:53 UTC | Status | Needs Signoff | Failed QA |
| aleisha | 2024-08-14 21:13:26 UTC | Status | Failed QA | RESOLVED |
| Resolution | --- | INVALID | ||
| katrin.fischer | 2025-06-02 20:46:24 UTC | Status | RESOLVED | CLOSED |
Back to bug 37640