A customer sent a request to add date of birth column to a person listing, because the end user wants to see what is the age of a person in a recruitment process (especially if person is just under 18, but turning 18 soon).
So the only need is to know the persons age, not the actual date of birth.
To me showing the dates seems irrelevant and annoying since you need to calculate the ages in your head, and that would probably cause human errors. (Atleast to me calculating ages by dates takes a while.)
I suggested that we would instead put age column there, and show the age as decimal, so that 17 year old who soon turns 18 would show as 17,9. And have the actual birth date as a tooltip on hover. Then the recruiter could check if the person turns 18 and can be recruited to a job that requires the person to be atleast 18.
Showing the ages as a decimal seems more user friendly, if the need is to know the ages and see if 17 year old is turning 18 soon. But is it really? Someone said that "age can not be a decimal".
Can you think of any other solutions to this?
[Leave out the age discrimination in recruitment process, for some jobs a person needs to be 18 or turn 18 this year]