Bug 19225 proposes a warning for users that the config is wrong. I propose instead, we should just ignore that field if automembernum is enabled (since it autocalculates and becomes mandatory
any updates on bug 19642? Carnegie Team.
Hi Brian, instead of just asking for an update, I think it would be nice if you made your requests more specific. Read through the bug, look at the history, the timeline, and phrase if you'd like the suggested solution etc. At the moment, there is a good workaround for this problem: We show a warning to change configuration and people can do that. I like Nick's suggestion because it gets rid of a lot of text and is a little more intuitive, but I think I'd categorize it more as an enh at this point.
Nick, are you proposing not showing the cardnumber field on member entry if automembernum is on? That would create a problem for libraries that want to use automembernum for online self-reg patrons but not for registrations performed by staff. Unless we split automembernum into two sysprefs, one for intranet and one for staff.
(In reply to Andrew Fuerste-Henry from comment #3) > That would create a problem for libraries that want to > use automembernum for online self-reg patrons but not for registrations > performed by staff. Agreed. > Unless we split automembernum into two sysprefs, one for > intranet and one for staff. This would certainly work for my library. Or add an option to patron category configuration? "[ ] Allow automatic card number assignment"