Querying ProfileConnection#digital_object_ids

I am wanting to allow "digital-object-ids" as part of the query
parameters for connecting an Orcid profile.

In talking with people from orcid.org it was suggested that looking up
profiles is best done via Email and DOIs.

See for available parameters:
http://support.orcid.org/knowledgebase/articles/132354-tutorial-searching-with-the-api

@TODO - It would be nice to properly label these.

@ASIDE - I updated .hound.yml to reflect how I want it parsed.
Merge pull request #14 from jeremyf/adding-digital-object-ids-to-profile-connection-query

Querying ProfileConnection#digital_object_ids
Adding error handling for "weird" search results

I don't know if these are truly weird retults, but the resulting
document from the query says there are 0 results but includes 10 nodes
that look like they could be results.

The returned JSON document is captured in the newly committed file:
    multiple-responses-without-valid-response.json

Given the potential volatility of the response document from Orcid,
I've also opted to extract the parser for the response document.
In doing so, it is easier to unit test parsing the response.

Closes #2

Relates to: ORCID/ORCID-Source#1100