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

Update job transitioning projects from "data pending" to "under embargo" #91

Closed
allaway opened this issue Nov 5, 2024 · 2 comments · Fixed by #94
Closed

Update job transitioning projects from "data pending" to "under embargo" #91

allaway opened this issue Nov 5, 2024 · 2 comments · Fixed by #94
Assignees
Labels
good first issue Good for newcomers

Comments

@allaway
Copy link
Contributor

allaway commented Nov 5, 2024

This project annotation/study annotation is often out of date, because we don't know when people upload data. it would be great to to have a job that transitions datastatus from Data Pending to Under Embargo. High level outline: runs once a week, retrieve study view for dataStatus = 'Data Pending' and then for each of those rows, check the project "Raw Data" folder for file entities, and if they are present, transition to "Under Embargo"

This job should not touch 'terminal' statuses like Data Not Expected or Available.

Update:
This is currently running but not sending Slack notifications. James will be learning how to test the job, build image, add Slack notifications, and update with new image in Service Catalog.

@allaway
Copy link
Contributor Author

allaway commented Nov 5, 2024

Also, I might have filed this issue elsewhere...it sounds familiar to me. apologies of that's the case :)

@anngvu anngvu changed the title idea: job to transition projects from "data pending" to "under embargo Update job transitioning projects from "data pending" to "under embargo" Nov 21, 2024
@anngvu anngvu moved this to In Progress in NF-OSI Sprints Nov 21, 2024
@anngvu anngvu added the good first issue Good for newcomers label Nov 26, 2024
@changtotheintothemoon
Copy link
Contributor

New PR branch created #94

This may need further testing just to confirm it would work with other runs. Currently, docker image can be created and slack notifications is being sent to slack via dry run.

@anngvu anngvu closed this as completed in #94 Jan 3, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in NF-OSI Sprints Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants