resume-schema: Missing personnel master data

At least in Germany, it’s standard practice to include a short section of personnel master data at the top of the CV.

Example:

Name = John Doe
Birth = 6th December 1980 in Berlin
Citizenship = German
Family status = married
Children = two (6 and 12 years)

Although that might not be common in other countries, could this be added as an optional section?

Example:

master_data: {
    name: string,
    birth: {
        date: integer,
        place: string
    },
    citizenship: string,
    family_status: string,
    children: [{
        gender: string,
        birth_date: int
    }]
}

About this issue

Original URL
State: closed
Created 10 years ago
Reactions: 1
Comments: 31 (16 by maintainers)

Most upvoted comments

I haven’t seen any +1s for almost 2 months now, which gives me the feeling that there’s not so much need for this after all? Can we close this @thomasdavis?

DonDebonair on Jan 8, 2015

We could make them optional and make it very clear in the description that in some countries it’s illegal for an employer to ask about this.

I’m from Germany too. Your Birthday is required on a resume here. For everyone who feels like he is getting discriminated because of this age can just leave the birthday field empty…

TimDaub on Nov 10, 2014

+1, its pretty much mandatory in the Netherlands. Just google “nederlands cv”, first 13 image hits contain this data.

ernstkui on May 30, 2015

I also feel that these properties do not belong on a resume

That’s highly subjective. In Germany, it’s common to provide these pieces of information and accepted to ask for them.

These are criteria typically used to discriminate – in the bad sense of the word. (Age discrimination, gender, descent based, less overtime because of obligations to family, etc. etc.)

Unfortunately, that’s what they may be used for. But should it be this open-source project’s task to fight social issues – or should this project concentrate on providing users what they need to get their resumes done? Ultimately, it’s up to the user to decide which data to provide. But a specification should not prevent use cases that are absolutely valid.

This opens up the question of which enum to put in the family_status field.

We can just as well make this a plain string. That seems to be the way this project goes for i18n issues, and it makes sense.

Can we circumvent this by adding a notes property to the bio field where you may describe gender, kids and marital status in free-form if needed. Or would the german resume be unusable?

Actually, yes. These pieces from free-form data will always appear different than the other records in your resume. For example, a template designer may consider adding bullet points to each record, causing your huge free-form “notes” section to have only one bullet point and thus appearing completely different, resulting in an unprofessional CV.

The specification currently lacks these fields preventing it from being used for a proper German CV:

"citizenship": {
    "type": "string",
    "description": "optionally provide information about your nationality, e.g. Canadian"
},
"maritalStatus": {
    "type": "string",
    "description": "optionally provide information about your civil status, e.g. married, single, divorced or widowed"
},
"birth": {
    "type": "object",
    "description": "optionally provide information about the date and place of your birth",
    "properties": {
        "date": {
            "type": "string",
            "description": "e.g. 1970-12-31"
        },
        "place": {
            "type": "string",
            "description": "e.g. London"
        }
    }
},
"children": {
    "type": "string",
    "description": "optionally provide information about your children, e.g. number of children and their age"
}

ocram on Jul 13, 2014