Interoperability w/linkedin, facebook, seek.com, monster.com, careerone, etc

[knoxg]

There should be a page comparing this schema with the information requirements of other resume-distribution services (e.g. linkedin, facebook, seek.com, monster.com, careerone, etc), together with code samples to maintain resumes across multiple sites.

it would also be good to maintain compatibility with hResume ( http://microformats.org/wiki/hresume ), or to move the project under that banner.

[thomasdavis]

So for hResume, we are going to make our default templates try to adhere to the Microformat, we have a bit of a problem though because themes will be created by the community and theme owners might not implement it, not sure what to do on that front.

We were going to build sync tools into the CLI, so resume sync linkedin will sync your work history etc

This issue will be a good place to start. I imagine LinkedIn might be a good first service to start with too

[stp-ip]

Any progress on linkedin sync?

[aloisdg]

I don't know but after a quick search on GitHub with "jsonresume linkedin" :

• linkedin-to-json-resume by @JMPerez
• resume-linkedin by @mblarsen
• linkedin-jsonresume by @lirsacc

[stp-ip]

Seems like they all use your linkedin profile to generate a jsonresume not the other way around unfortunately.

[JMPerez]

@aloisdg LinkedIn's API is very limited to say the least. I had to change the LinkedIn to JSON Resume project after they made changes in their API, making it impossible to get any valuable data. It now relies on a exported zip file the user has to request.

I don't expect them to make any effort in their API, at least when it comes to availability for 3rd party developers.

[aloisdg]

@JMPerez Thank you for the comment!

[JMPerez]

@aloisdg No problem! Let me know if there is any way I can help.

[olivif]

I see @mblarsen is using https://www.npmjs.com/package/node-linkedin to get data out. The data manipulation seems pretty straightforward but not exactly sure how the auth flow works there.

[JMPerez]

@olivif thanks for the link. As far as I know a regular user can't create an app that asks for the full profile scope anymore, and that's the scope that returns most of the info that we need to complete a JSON Resume.

[stp-ip]

We could start reaching out to various players and get their input and ask for their opinion in supporting import/export for their platform. Ideas:

• [ ] linkedin.com
• [ ] crunchbase.com
• [ ] facebook.com
• [ ] seek.com
• [ ] monster.com
• [ ] xing.com
• [ ] careerone

Or we finish a draft v1.0.0 and push for adoption via user usage.

[chrisdotcode]

Ideally, export code will (and should, IMO) be baked into resume-server.

[aloisdg]

Also:

• [ ] careers.stackoverflow.com
• [ ] viadeo.com

I think it should be better to finish a clean version aka v1.0.0 and ask for theur help after for a v1.x.x

[aloisdg]

In another hand, it would be nice to support this too:

• [ ] https://www.cakeresume.com/
• [ ] https://www.visualcv.com/

[chrisdotcode]

So after some thought, I'm actually against this, ideologically.

We, JSON Resume are the standard. All of the above-listed organizations should be using our standard format, not the other way around. That's the whole point.

Practically speaking, we could have will-be-deprecated exporters for the time being, and once we publish v1.0.0 and start getting some traction, we remove them.

[olivif]

@chrisdotcode, I agree completely! The exporters would be a good way to get people into JSON resume. It's important for us to have a good OOBE and the exporters would help us do that. If we ask people to fill in 2000 odd lines of JSON to begin with, we might have a harder time.

[aloisdg]

@chrisdotcode yes of course. We want to use JsonResume everywhere. One resume to rules them all.

[thomasdavis]

Closing in favor of discussion here -> https://github.com/jsonresume/resume-cli/issues/356