https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42734 Bug ID: 42734 Summary: autoMemberNumValue syspref has no UI â add it to patrons preferences with a caution note Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs@lists.koha-community.org Reporter: martin.renvoize@openfifth.co.uk QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, kyle@bywatersolutions.com Bug 34000 introduced autoMemberNumValue as an internal monotonic counter to prevent cardnumber re-issuance. However there is currently no way for staff to view or correct this value if it becomes inflated â for example, if a book barcode is accidentally scanned when creating a patron and that patron is subsequently deleted or has their cardnumber corrected. This patch adds autoMemberNumValue to the Patrons system preferences page (near autoMemberNum) so that superlibrarians can correct a runaway counter without contacting vendor support. The entry includes a caution note explaining: - that the value is managed automatically and should not normally be changed - that Koha always generates from max(counter, live_db_max), so lowering the counter only has effect once the patron responsible for the inflated number has been deleted or had their cardnumber corrected - the risk of setting it too low (potential cardnumber re-issuance) Test plan: 1. Apply patch 2. Go to Administration > System preferences > Patrons 3. Confirm autoMemberNumValue is visible immediately below the autoMemberNum preference 4. Confirm the caution note is displayed 5. With autoMemberNum enabled, create a patron without specifying a cardnumber and confirm the generated number is consistent with the counter value 6. Adjust autoMemberNumValue to a lower number (after ensuring no active patron holds a cardnumber in that range), create another patron, and confirm the next auto-generated number reflects the corrected counter -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.