Proceed to jobs status update page.

1 files changed, 3 insertions, 35 deletions

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 """
-    <p>The following steps need to be performed:
-    <ol>
-    <li>Check that all IDs exist</li>
-    <li>Check for mandatory values</li>
-    <li>Update descriptions in the database (where changed)</li>
-    <li>Update publications in the database (where changed):
-    <ol>
-    <li>If <strong>PubMed_ID</strong> exists in our database, simply update the
-    'PublicationId' value in the 'PublishXRef' table.</li>
-    <li>If <strong>PubMed_ID</strong> does not exists in our database:
-    <ol>
-    <li>fetch the publication's details from PubMed using the new
-    <strong>PubMed_ID</strong> value.</li>
-    <li>create a new publication in our database using the fetched data</li>
-    <li>Update 'PublicationId' value in 'PublishXRef' with ID of newly created
-    publication</li>
-    </ol>
-    </ol>
-    </li>
-    <li>Update values in the database (where changed)</li>
-    </ol>
-    </p>
-
-    <p><strong>Note:</strong>
-    <ul>
-    <li>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.</li>
-    <li>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.</li>
-    </ul>
-    </p>
-    """
+    return redirect(url_for("background-jobs.job_status",
+                            job_id=job_id,
+                            job_type="phenotype-bulk-edit"))