-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Save OrcID in an actor record #518
Projects
Comments
I have sent a request to EIT to get access to directory-service. once i get it, i'll put it into vault and work up some sample code for grabbing the orcid |
Question - what do we do when the user-entered orcid and the orcid coming from the service conflict?
|
whereismyjetpack
added a commit
that referenced
this issue
Feb 2, 2022
Closed
whereismyjetpack
added a commit
that referenced
this issue
Feb 2, 2022
whereismyjetpack
added a commit
that referenced
this issue
Feb 2, 2022
whereismyjetpack
added a commit
that referenced
this issue
Feb 3, 2022
whereismyjetpack
added a commit
that referenced
this issue
Feb 3, 2022
whereismyjetpack
added a commit
that referenced
this issue
Feb 3, 2022
whereismyjetpack
added a commit
that referenced
this issue
Feb 3, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Presently in ScholarSphere OrcID is a user editable field.
We populate a User record with metadata from AzureAD, and an Actor record with a combination of the ScholarSphere User record, and Penn State's
search-service
AzureAD, and
search-service
do not present a members OrcID. We can populate a users OrcID viadirectory-service
When saving a user record we can 'refresh' or add OrcID by calling the
directory-service
API.WDLL
get an API token with read access to directory-service.
write a service that calls
directory-service
to refresh an Actor's metadata. we can just graborc-id
as well.The text was updated successfully, but these errors were encountered: