From 64d46c5bc168e37a06ca60685fbc7aae54d48ba1 Mon Sep 17 00:00:00 2001
From: Frederick Muriuki Muriithi
Date: Mon, 21 Apr 2025 13:50:13 -0500
Subject: Proceed to jobs status update page.
---
uploader/phenotypes/views.py | 38 +++-----------------------------------
1 file changed, 3 insertions(+), 35 deletions(-)
(limited to 'uploader')
diff --git a/uploader/phenotypes/views.py b/uploader/phenotypes/views.py
index a18c44d..92a7c4b 100644
--- a/uploader/phenotypes/views.py
+++ b/uploader/phenotypes/views.py
@@ -1000,38 +1000,6 @@ def edit_upload_phenotype_data(# pylint: disable=[unused-argument]
worker_manager="gn_libs.jobs.launcher")
- return """
-
The following steps need to be performed:
-
- - Check that all IDs exist
- - Check for mandatory values
- - Update descriptions in the database (where changed)
- - Update publications in the database (where changed):
-
- - If PubMed_ID exists in our database, simply update the
- 'PublicationId' value in the 'PublishXRef' table.
- - If PubMed_ID does not exists in our database:
-
- - fetch the publication's details from PubMed using the new
- PubMed_ID value.
- - create a new publication in our database using the fetched data
- - Update 'PublicationId' value in 'PublishXRef' with ID of newly created
- publication
-
-
-
- - Update values in the database (where changed)
-
-
-
- Note:
-
- - If a strain that did not have a value is given a value, then we need to
- add a new cross-reference for the new DataId created.
- - If a strain that had a value has its value deleted and left blank, we
- need to remove the cross-reference for the existing DataId — or, should we
- enter the NULL value instead? Removing the cross-reference might be more
- trouble than it is worth.
-
-
- """
+ return redirect(url_for("background-jobs.job_status",
+ job_id=job_id,
+ job_type="phenotype-bulk-edit"))
--
cgit v1.2.3