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

Add a mechanism for specifying the ORCID for a user requesting file transfers. #81

Closed
jeff-cohere opened this issue Aug 13, 2024 · 2 comments · Fixed by #95
Closed

Add a mechanism for specifying the ORCID for a user requesting file transfers. #81

jeff-cohere opened this issue Aug 13, 2024 · 2 comments · Fixed by #95
Assignees
Labels

Comments

@jeff-cohere
Copy link
Collaborator

jeff-cohere commented Aug 13, 2024

Right now we assume that the ORCID associated with a dev token is the same as that for a user requesting a file transfer. We should add an ORCID field to a transfer request and use that one instead to identify the requestor.

@jeff-cohere jeff-cohere self-assigned this Aug 13, 2024
@jeff-cohere jeff-cohere removed their assignment Nov 21, 2024
@jeff-cohere jeff-cohere changed the title Figure out how to handle accounts with multiple ORCIDs associated Add a mechanism for specifying the ORCID for a user requesting file transfers. Dec 11, 2024
@jeff-cohere
Copy link
Collaborator Author

When we generate a DTS manifest as part of a transfer task, we include information about the requesting user in the corresponding DataPackage Contributors field. If we are handed an ORCID, we could retrieve this information using the ORCID Public API.

@jeff-cohere
Copy link
Collaborator Author

For mapping an ORCID to a KBase user, we might be able to use this service:

https://github.com/kbase/kbase-service-orcidlink

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

Successfully merging a pull request may close this issue.

1 participant