Skip to content
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

Closed
2 tasks
Tracked by #1198
whereismyjetpack opened this issue Sep 8, 2020 · 2 comments · Fixed by #1218
Closed
2 tasks
Tracked by #1198

Save OrcID in an actor record #518

whereismyjetpack opened this issue Sep 8, 2020 · 2 comments · Fixed by #1218
Assignees

Comments

@whereismyjetpack
Copy link
Member

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 via directory-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 grab orc-id as well.

@whereismyjetpack
Copy link
Member Author

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

@awead awead added this to the Backlog milestone Sep 21, 2020
@awead awead removed this from the Backlog milestone Nov 19, 2020
@awead awead added this to Blocked in Scholarsphere Apr 28, 2021
@srerickson
Copy link
Contributor

srerickson commented Jan 25, 2022

Question - what do we do when the user-entered orcid and the orcid coming from the service conflict?

Answer: We shouldn't have user-entered ORCIDs.

@srerickson srerickson moved this from Blocked to Next Sprint in Scholarsphere Jan 27, 2022
@nicktiberi nicktiberi moved this from Next Sprint to In Progress in Scholarsphere Jan 27, 2022
Scholarsphere automation moved this from In Progress to Ready for Retro Feb 4, 2022
@nicktiberi nicktiberi linked a pull request Feb 4, 2022 that will close this issue
@nicktiberi nicktiberi moved this from Ready for Retro to Prod Deploy in Scholarsphere Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Scholarsphere
Prod Deploy
3 participants