summary refs log tree commit diff
path: root/issues/gnqna
diff options
context:
space:
mode:
Diffstat (limited to 'issues/gnqna')
-rw-r--r--issues/gnqna/query-bug-DatabaseError.gmi37
-rw-r--r--issues/gnqna/rating-system-has-no-indication-for-login-requirement.gmi30
2 files changed, 37 insertions, 30 deletions
diff --git a/issues/gnqna/query-bug-DatabaseError.gmi b/issues/gnqna/query-bug-DatabaseError.gmi
new file mode 100644
index 0000000..b8c1cfc
--- /dev/null
+++ b/issues/gnqna/query-bug-DatabaseError.gmi
@@ -0,0 +1,37 @@
+# Query Bug: DatabaseError
+
+## Tags
+
+* assigned: fredm, bonfacem
+* priority: high
+* status: open
+* type: bug
+* keywords: gnqna
+
+## Descriptions
+
+* Go to https://genenetwork.org/gnqna
+* Type in a query
+* Press "Enter"
+* Observe the error "DatabaseError" with a status code of 500.
+
+Expected: Query returns a result.
+
+
+## Troubleshooting: 2025-10-27
+
+* GNQNA's deployment is not part of the gn-machine's definitions!
+
+## Troubleshooting: 2025-12-31
+
+If a user **IS NOT** logged in, the system responds with:
+
+```
+Search_Query:
+Status_Code: 500
+Error/Reason: Login/Verification required to make this request
+```
+
+On the other hand, if a user is logged in, a query returns a result.
+
+We, therefore, probably need to notify the user that they need to be logged in to use this service.
diff --git a/issues/gnqna/rating-system-has-no-indication-for-login-requirement.gmi b/issues/gnqna/rating-system-has-no-indication-for-login-requirement.gmi
deleted file mode 100644
index 7ed713a..0000000
--- a/issues/gnqna/rating-system-has-no-indication-for-login-requirement.gmi
+++ /dev/null
@@ -1,30 +0,0 @@
-# Rating System: No Indication for Login Requirement
-
-## Tags
-
-* type: bug
-* status: open
-* priority: medium
-* assigned: alex, shelby
-* keywords: gnqna, user experience, UX
-
-## Description
-
-=> https://cd.genenetwork.org/gnqna The GNQNA system on CD
-requires the user to be logged in for them to be able to rate the answers.
-
-There is, however, no indication that that is expected; instead, the user receives an alert with the following cryptic error when they attempt to rate an answer when not logged in:
-
-```
-HTTP Error:HTTP Response Code: 500-reason-Generic Exception
-```
-
-This is not a friendly response to the user, since it does not tell the user what they did wrong.
-
-I propose a message that lets the user know they need to be logged in to rate the answer, something like:
-
-```
-You attempted to rate your answer, but you are not logged in. We do not allow rating unless you are logged in.
-
-This is in place to reduce the chances of spam ratings. Do, please, log in and attempt rating again.
-```