Internal procedure for managing requests for Shared Collections via Globus Connect Personal
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
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.
Written by the indexing model from the issue text.
Description
Preliminary internal procedure.
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 #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.
- Dominant language
- Python
- Stars
- 1
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from uabrc/devops-docs
-
LTS service accountsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
uabrc/devops-docs#94 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
uabrc/devops-docs#54 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
uabrc/devops-docs#48 ·
-
Document procedure for ticket management and closureMay be free again @iam4tune claimed this 53 days ago, and no pull request is open. Open
uabrc/devops-docs#97 · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
uabrc/devops-docs#96 ·
All issues in uabrc/devops-docs
Similar issues
-
Zero-token evaluations are treated as missing cost in selectionPossibly taken @sylvesterkaczmarek claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
google-research/rrsi#6 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
aws-samples/sample-aws-genai-db-modernizer#294 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
githubnext/gh-aw-workshop#4174 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
WingedGuardian/GENesis-AGI#2852 ·
Maintainers usually reply within 1 day
-
camlight produces degenerate target camera and light framesPossibly taken @kavyabhand claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google-deepmind/mujoco_warp#1743 ·
Maintainers usually reply within 1 day