Multiple projects per position

[redbeard]

The idea is to allow per-project details at the same company. Similar to the new(ish) feature in LinkedIn profiles.

Structure follows same fields as position schema, but without company name, website, etc.

{
  "work": [{
    ...
    "projects": [{
        "startDate": "string", // resume.json uses the ISO 8601 date standard e.g. 2014-06-29
        "endDate": "string", // e.g. 2012-06-29
        "summary": "string", // Give an overview of your responsibilities in the project
        "highlights": [] // As in position schema
      }]
    }]
}

[ocram]

I think this blows up not only the specification but also your resulting CV.

[redbeard]

I disagree, evidenced by the use of it on LinkedIn.

It is extremely helpful for consultants who often have multiple
long-term assignments with clients of the same employer.

-T

On Thursday, July 10, 2014, Marco notifications@github.com wrote:

I think this blows up not only the specification but also your resulting
CV.

—
Reply to this email directly or view it on GitHub
#65 (comment)
.

[DonDebonair]

I agree this is needed.

Also, as @rolandnsharp mentioned in #24 it sometimes makes sense to specify who you worked for, in addition to who employed you. This is not only needed in the context of contracter work, but also when you work for multiple clients and want to specify those.

My suggestion is two kill two birds with one stone and introduce "projects" for each "work" entry. Not only can you specify for each project for/at which client you did that project, you can also specify - beyond what separate "highlights" offers - what the project consisted of.

[lannybroo]

Similar but related request: I'd like to organize my resume by multiple roles I've held at my organization. With the current schema, I've had to list the same employer multiple times to accomplish this, but I'd rather have another layer of hierarchy under each employer.

[mchelen]

I'd like this feature as a way to show multiple consulting clients without using separate Work entries.

[nikolay]

👍 This is needed, plus, it's should be optional, it's backward-compatible, and not all themes have to implement it.

[DonDebonair]

Can @thomasdavis and @opensourcegrrrl weigh in on this?

[osg]

+1

[stp-ip]

There is a definite need for this as was already mentioned consultancy clients or fast moving companies use their employees for more than one project. One could use highlights, but that is not the perfect place and not as accurate and clean.

[stp-ip]

Definitely could be combined with #11

[olivif]

Moving over the discussion to the new issue. I believe all topics covered here are included in the proposition.

[nikolay]

@olivif I don't think you understand the exact idea behind this issue! While working for an agency, which is one employment, I could be working for different clients on different projects and being on different positions on each project. Also, even on a single job, I could have multiple titles (if you gets promoted/demoted, etc.)

Okay, these are edge cases, but if the schema does not allow you to handle 10-20% of the cases, then it's not universal, and many people will fork the tools, and themes to get around this, which is sad.