Skip to content
This repository has been archived by the owner on Aug 23, 2018. It is now read-only.

splitting orcid service into tier-1 and tier-2 pieces? #3

Open
arthurpsmith opened this issue Jun 18, 2012 · 1 comment
Open

splitting orcid service into tier-1 and tier-2 pieces? #3

arthurpsmith opened this issue Jun 18, 2012 · 1 comment

Comments

@arthurpsmith
Copy link
Contributor

I've been figuring out the search bits but stumbling on the OAuth2 redirect issue (you can't redirect to anything but registered URL's so computed ones that come from a search don't work as far as I can tell). At some point that needs to be addressed but I'd like to get the simpler query stuff working as a client. It might be clearer to split the orcid service in the example client into tier-1 and tier-2 pieces - well, actually the client right now is only doing tier-2 stuff, so I guess what I'm proposing is to create a second implementation of the OrcidService interface that does tier-1.

If you see this and have any concerns about this direction please let me know, I'll probably get this going and post it as another pull request in about a week. Thanks!

@arthurpsmith
Copy link
Contributor Author

By the way, working on this I accidentally triggered some 500 server errors on api.devsandbox - I think it happened when I sent a request to the Search URL with no query parameter - just straight http://api.devsandbox.orcid.org/search/orcid-bio

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant