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
Updating travis badge to new repo location
Merge pull request #15 from projecthydra-labs/issue-2

Adding error handling for "weird" search results
Capturing predictable exceptions from Orcid

When requesting the creation of an orcid profile, the remote service
could say the request is invalid.

More information at:
http://support.orcid.org/knowledgebase/articles/252102-api-error-codes

Closes ndlib/sufia_orcid#3
Tweaking Travis badge to projecthydra-labs

[skip ci]
Tidying up ORCID internationalization

[skip ci]
Merge pull request #16 from projecthydra-labs/issue-3

Capturing predictable exceptions from Orcid
Creating Orcid::ProfileStatus

This is an attempt to consolidate that knowledge.

There are several places in which we want to have access to a user's
Orcid Profile status, and methods related to those states.

The Orcid Profile Status makes use of callbacks because we do not
have a uniform object that represents each state for a user and their
orcid profile.

@TODO - review the controllers that have encapsulated this state and
have it lean on the Orcid::ProfileStatus handler.
Merge pull request #17 from projecthydra-labs/adding-profile-status

Creating Orcid::ProfileStatus
Adding helper method for Orcid URI
Merge pull request #18 from projecthydra-labs/adding-url-helper

Adding helper method for Orcid URI
Appeasing the hound

I believe this is incorrectly firing.

[skip ci]
Conditional rendering for orcid profile connecter

The orcid profile connector should account for the identified states
of a user's orcid profile.

I have introduced a first pass at each of those options.

Closes to ndlib/sufia_orcid#4
Merge pull request #19 from projecthydra-labs/issue-4

Conditional rendering for orcid profile connecter
Adding CONTRIBUTING guidelines

I want to let others know how they can participate in this project.
This is my first pass.

Note, this is a stripped down version of the CONTRIBUTING document
from projecthydra-labs/curate
Adding explicit pathing to partial rendering

In a reference implementation, we were encountering an error in which
the partials were not found. This is because the partial was
referenced as a file (i.e. filename) and not via a path (i.e.
path/to/filename). Rails has different lookup handling if given a
filename vs. a path.

http://guides.rubyonrails.org/layouts_and_rendering.html#using-partials
Merge pull request #21 from projecthydra-labs/resolving-partial-lookup-path-issues

Adding explicit pathing to partial rendering
Capturing Orcid Profile Request error

@Note - The error is effectively being swallowed.

@TODO - Instead of the two-step save for the information, consider
how to do this within the request cycle.

This is a bandage solution to ndlib/sufia_orcid#4