| Summary: | Making previous patron cardnumbers searchable | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Fiona Borthwick <fiona.borthwick> |
| Component: | Patrons | Assignee: | Jake Deery <jake.deery> |
| Status: | ASSIGNED --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | gmcharlt, janet.mcgowan, kebliss, kyle, martin.renvoize, susan.murphy |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39452 | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Attachments: | Bug 27364: Add historic_cardnumbers to Patron object & API | ||
|
Description
Fiona Borthwick
2021-01-08 11:04:49 UTC
We really don't want them searchable or usable BUT do want staff to be able to see them without giving staff access to the modification logs. Mostly for troubleshooting the eResources where patrons used their old card to set up their accounts and now they have a new card that doesn't recognize them. Hoopla is our biggest issue. Created attachment 193836 [details] [review] Bug 27364: Add historic_cardnumbers to Patron object & API This patch adds an historic_cardnumbers field to the patron object, staff client, and API call (which will return an array of objects containing information about the cardnumber and when it was changed). TO TEST: == APPLY PATCH == a) Ensure 'CardnumberLog' is on in the sysprefs b) Change the koha user's cardnumber from 42 to 67 c) Reverse step b) d) Go to the koha user's details page *) note how there is a historic cardnumbers box *) note how each change is marked, next to the date and time performed *) note how the time is accurate to minutes e) Go to /api/v1/patrons/51 *) notice how the historic_cardnumbers array is populated with two objects *) each object is per cardnumber change *) each object contains the new and old cardnumber, as well as the timestamp of the transaction == RESET_ALL == f) repeat steps d-e *) notice how the historic cardnumbers section is missing if no cardnumber change has occured, on the patron details page *) notice how the historic_cardnumbers array is empty in the api call, if no cardnumber change has occured == SIGN OFF == |