500+ contacts

[dennisjaheruddin]

I really like to visualise the network, however since I have more than 500 connections the value of the visualisation has decreased a lot.

Would it be possible to implement something that allows me to store the connections that have already been downloaded, and thus allowing me to continue the next day?

[webmaven]

Is this still an active issue?

[lacabra]

Yes, this is still an active issue, and will remain unless LinkedIn says otherwise.
LinkedIn explicitly prohibits to store connection data in their API Terms of Use, see section 1.4.4:

your Application WILL NOT store or export any data from LinkedIn other than the LinkedIn Profile Data for the LinkedIn member that requested the data. “Profile Data” means the name, photo, headline, contact information, experience, education, summary, and location of a LinkedIn member. Profile Data excludes connections, network updates, job listings, groups, companies, and any other content.

[Paul-A-Lyons]

There has to be a work around for this in analyzing ones own network. I can export my own dataset with the request an archive option under the settings. Could I then specify where in the list of my connections to begin. I have about 1200 so would running it over 3 days and then bringing it together be feasible?

[OdynOOb]

500+ connections would be nice.

What does prohibit us from storing locally our own 500+ connections (which we could get in multiple 500 steps, as this is an API limitation) ?

[craigtutterow]

It's against the API terms to export data, so all of the processing has to take place in the browser when the page is loaded.

[axsaucedo]

@craigtutterow it seems that the data is already being cached in the browser.

With this in mind, would it be possible to hit the LinkedinAPI with a new request every time the page is loaded (ie once a day), and add any new nodes/contacts and edges/connections to the cached object?

This wouldn't break the terms as it's not exporting any data, it's just superimposing it with any previously cached data.

I assume unique keys such as email address would make this possible, and this would allow people to load all their 500+ connections eventually.

Would this work?