You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’ll use “Service Request” as shorthand for a ticket specifically asking to share Globus Connect Personal collections.
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.
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.
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.
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.
If there is just a Service Request, then we briefly describe how they can make the Globus Group Request.
The text was updated successfully, but these errors were encountered:
Preliminary internal procedure.
I’ll use “Service Request” as shorthand for a ticket specifically asking to share Globus Connect Personal collections.
The text was updated successfully, but these errors were encountered: