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

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 #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.

Start by reviewing the issue text and the existing devops-docs documentation structure, since no target file or test is named. Confirm where this internal Globus procedure belongs and whether the three cases and identity restrictions are complete; done means the procedure is placed in the appropriate documentation and reflects an agreed workflow.