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

create workflow for new dataset requests #13

Open
graybeal opened this issue Feb 28, 2021 · 4 comments
Open

create workflow for new dataset requests #13

graybeal opened this issue Feb 28, 2021 · 4 comments
Assignees
Labels
DC team Tickets requiring attention from Google's DC team task Specific work for us to do

Comments

@graybeal
Copy link
Collaborator

Work with PHS and Google to create a workflow for new requests for datasets.

@graybeal graybeal self-assigned this Feb 28, 2021
@graybeal graybeal added the task Specific work for us to do label Feb 28, 2021
@graybeal
Copy link
Collaborator Author

For a start, new dataset requests are labelled with 'dataset request' and begin with "Add dataset" (or "Add datasets").

@graybeal graybeal modified the milestone: MVP (Phase 1) Feb 28, 2021
@graybeal graybeal added the DC team Tickets requiring attention from Google's DC team label Mar 3, 2021
@graybeal
Copy link
Collaborator Author

graybeal commented Mar 3, 2021

The workflow for dataset requests starts when people wanting new datasets create a new Dataset Request ticket (using that ticket template type) and fill out the details. (If the requestor doesn't do GitHub, the request can be emailed to/interpreted by John G or another member of the PHC-DC team.)

The new issue will be moved to Icebox by default and assigned the 'dataset request' tag. It should be moved into the Icebox in the appropriate priority position as estimated by the Stanford team members, so Google engineers can monitor the desired priority. Stanford team members will review votes (heart emojis on the ticket description, informed by other emoji votes and comments) for requests to help them assess the appropriate priority.

The request ticket will be moved to other columns when it is determined that the request has necessary importance and/or needed detailed information to be formally reviewed by the DC team. (Typically this will be a move to the Analysis column for imminent work, and the Backlog section if it is awaiting resources.) An actual decision by the Data Commons team to satisfy the dataset request will be indicated by assigning the 'DC team' label to the ticket, and it will be moved to the In Progress section when work begins.

@graybeal
Copy link
Collaborator Author

graybeal commented Mar 3, 2021

This workflow needs review by PHS and Data Commons representatives.

@drehkopf
Copy link

drehkopf commented Mar 4, 2021

I'm happy to review the requests here and help to gather consensus and then make decisions on priorities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DC team Tickets requiring attention from Google's DC team task Specific work for us to do
Projects
None yet
Development

No branches or pull requests

2 participants