Skip to content
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

Closed
claudeduguay opened this issue Jun 21, 2017 · 6 comments
Closed

Single Phone Numbers may be too strong a constraint #285

claudeduguay opened this issue Jun 21, 2017 · 6 comments

Comments

@claudeduguay
Copy link

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.

@aloisdg
Copy link
Contributor

aloisdg commented Jun 22, 2017

Also some people don't like to be call before or after a specific hour.

@stp-ip
Copy link
Member

stp-ip commented Aug 30, 2017

Proposal:

  • phone as list/array
  • add call hours (stored with timezone)

@NewAlexandria
Copy link

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.

@stp-ip
Copy link
Member

stp-ip commented Aug 30, 2017

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.

@wayneamurphy
Copy link

I'm flip-flopping when reading this. Good idea, but wait it's true why include more than one number?
Overall this project seems to be for various people, not just people in the tech sector.
So even a kid whose parents split up and they live at different houses different days of the week - they'd have multiple phone numbers, but hopefully if one house gets called somebody would pass along the message to the other house.
So I'd say it is a good suggestion, but not essential.
If anything, the idea of preferred contact method, and a timezone for phone calling seems best.

@thomasdavis
Copy link
Member

thomasdavis commented Nov 18, 2020

Considering the discussion, as per basics.name, a persons phone is highly contingent on location, cultural and personal preference.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants