Required Fields Based on Hold Notification Preferences Too Strict

I am confirming the problem with the Default Phone Number. If Phone is checked as the default hold notification preference and there is no Default Phone Number entered, it should still save as long as there is a Daytime Phone. It shouldn't be necessary for staff to have to enter the phone number twice if they are the same number (which they *usually* are).

Although I see the point about the email address, I don't necessarily agree. I think if Email is selected as a hold notification preference default, it should require the email address to be stored. We use the email address for a lot of different types of notifications other than hold notices, but if a patron really doesn't want it to be stored in their record and receive those other notices, they still have the option of checking the email box and entering their email address at the time of hold placement.

I would swear I have a distinct memory of testing this in its early days, documenting this issue, and having the behavior updated to look at the day time phone number, but something must have changed between my testing and when it was committed to Evergreen.

The Phone Notify checkbox really should pay attention to the daytime phone number. Its current behavior will most likely become annoying very quickly when we go up on 3.5+. We have many patrons with phone notify set and just a daytime phone number.

I do not have a strong opinion on the email behavior one way or another, though I lean towards Terran's reasoning.

This makes me think that the notification settings need to be less default and more intentional.

So instead of phone and email methods being selected by default, they are only selected if certain fields are filled in during the registration process.

Example:
Daytime phone being filled in prompts the copying of information to the default phone number field and selection of the phone notification box.
Email field prompts the selection of the email notification box.
Filling the SMS info prompts the selection of the SMS notification box. (Way to test SMS notice at this point would be great, few patrons really know the carrier and make guesses.)

We have a Library Setting to use the last 4 digits of the daytime phone for the PIN. This setting could a starting point to creating a setting that takes the daytime phone and inserts it into the default phone number field?

It seems to still be an issue in 3.7 and in our test 3.9 instance.

Just to add a note to Jennifer's "less default" comment. We set the Registration Default of the opac.hold_notify user setting type to "".

After this is set none of the check boxes for hold notify are checked in the registration screen.

Something one of our libraries has noticed with this bug is when invalidating a patron's email address, we are forced to uncheck the Holds Notice box for email to get it to save. This loses the preference, and staff are adding an alert to remind themselves to add the preference back. We have noticed that if we don't hit save, the invalid email function saves on its own.

Would this be something that could be set at the org unit level via a library setting? I know some of our libraries would like to require the default hold notification methods, while others would not.