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

Removing duplicated tasks on science gateways #89

Merged
merged 4 commits into from
Dec 13, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 0 additions & 31 deletions docs/source/tasks/Science_Gateway_Allocation_Request_v1.md

This file was deleted.

21 changes: 0 additions & 21 deletions docs/source/tasks/Science_Gateway_Community_Accounts_v1.md

This file was deleted.

2 changes: 1 addition & 1 deletion docs/source/tasks/Science_Gateway_Description_v1.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ accessible information about the science gateway.

## Prerequisite tasks

1. The science gateway provider must have completed [Science Gateway Resource Requests](Science_Gateway_Resource_Requests_v1.md)
1. The science gateway provider must have completed [Request Science Gateway Resources](Request_Science_Gateway_Resources_v1.md)

## Support Information

Expand Down
77 changes: 0 additions & 77 deletions docs/source/tasks/Science_Gateway_Registration_v1.md

This file was deleted.

21 changes: 0 additions & 21 deletions docs/source/tasks/Science_Gateway_Resource_Requests_v1.md

This file was deleted.

86 changes: 0 additions & 86 deletions docs/source/tasks/Ticket_Handling_v1.md

This file was deleted.

8 changes: 5 additions & 3 deletions docs/source/tasks/Ticket_Handling_v2.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,11 +35,13 @@ To request new organization/RP specific routing queues open an *ACCESS Integrati

If you are a resource provider (RP) integrating a resource, provide a short organization name or abbreviation that can be used to define your RP queue. Theis queues will be named “\<short_name\>”, like “Jetstream-2” or “Delta”.

Identify for this queue the name and ACCESS usernames of:
Identify for this queue the name and email addresses of:

1. People that can UPDATE tickets in the queue
1. People who can browse tickets (agents)

2. Person who will be assigned tickets by default (this person will be able to reassign tickets to anyone else with queue access)
2. People who will be watchers to receive email notifications (watchers)

Note: Most of the time both agents and watchers are the same. But, if some agents do not want to be spammed with emails they may opt from being a watcher.

#### For ACCESS awardee queues

Expand Down