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

Internal procedure for managing requests for Shared Collections via Globus Connect Personal #53

Open
wwarriner opened this issue Jul 8, 2024 · 0 comments

Comments

@wwarriner
Copy link
Contributor

wwarriner commented Jul 8, 2024

Preliminary internal procedure.

I’ll use “Service Request” as shorthand for a ticket specifically asking to share Globus Connect Personal collections.

  1. If there is both a Service Request and a Globus Group Request, with matching email, then add them to the Globus Group and close the ticket.
  2. If there is just the Globus Group Request, and the email is @uab.edu, then email them and ask to create a Service Request (or create one on their behalf) asking why they’re requesting, then circle back to Deploy pointing to README #1.
    1. If the email is not @uab.edu, then we may not add it to the group under any circumstances, as this would violate the terms of our subscription.
    2. If it is a UAB-related entity, like @uabmc.edu or O'Neal Cancer Center, then contact the researcher and request they use their UAB identity instead. Also ask how they got to that point, because I don't think that should be possible.
  3. If there is just a Service Request, then we briefly describe how they can make the Globus Group Request.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant