-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Single Phone Numbers may be too strong a constraint #285
Comments
Also some people don't like to be call before or after a specific hour. |
Proposal:
|
This is a resume - who lists their work number? Or anymore, who gives their home number? Availability time is interesting. Useful for discriminating between 'before and after dayjob' people, and 'I have daytime availability' people. Still probably hard to use this field without a calendar integration. |
One example for listing their work number would be internal job applications in huge corporations. But it might just be local and international numbers and that alone would warant the suggestion for a list of numbers I would say. Haven't looked at discriminatory aspects of adding call hours. Question is. Is it better to be called off guard and not specify hours or specify them and not get called at all. Might be the same result and if your new employer doesn't respect boundaries it might not be the right one in the case one can choose. |
I'm flip-flopping when reading this. Good idea, but wait it's true why include more than one number? |
Considering the discussion, as per Trying to support all for data integrity is essentially incompatible with simply rendering a resume with a number the person can be called upon in context. |
It's pretty common now for folks to have either a Cell and Home number or Cell and Work, or all three. I suspect basics.phone should be a list.
The text was updated successfully, but these errors were encountered: