CDR Tickets

This appears to be a bug introduced by the kepler release.  

The program fails when it's trying to extract the non-existing CDR-ID to display on the report (GlossaryConceptFull.py).

The problem is that the report is trying to follow RelatedSummaryRef links by using the cdr:href attribute (which doesn't exist, and never has, as far back as I combed through the versions of the schema, going back to before the transition to CBIIT hosting, early in the previous decade) instead of the cdr:ref attribute. The program has been making this mistake since long before Kepler (at least as far back as July 2013, which is as far back as we have tagged versions of the code in GitHub; I could possibly dig further back, but I don't see that it would be worth the trouble).

Here's a patch, which I have checked into the leibniz branch and installed and tested on DEV.

diff --git a/Inetpub/wwwroot/cgi-bin/cdr/GlossaryConceptFull.py b/Inetpub/wwwroot/cgi-bin/cdr/GlossaryConceptFull.py
index af9c21b8..ba88fcee 100644
--- a/Inetpub/wwwroot/cgi-bin/cdr/GlossaryConceptFull.py
+++ b/Inetpub/wwwroot/cgi-bin/cdr/GlossaryConceptFull.py
@@ -617,7 +617,7 @@ class Concept:
         TYPES = dict(
             drug=(DRUG_SUMMARY_LINK, "Rel Drug Summary Link", "ref", True),
             xref=(EXTERNAL_REF, "Rel External Ref", "xref", True),
-            sref=(SUMMARY_REF, "Rel Summary Ref", "href", True),
+            sref=(SUMMARY_REF, "Rel Summary Ref", "ref", True),
             term=(TERM_NAME_LINK, "Rel Glossary Term", "ref", True),
             pdqt=(PDQ_TERM, "PDQ Term", "ref", False),
         )

Verified on DEV. Thanks!

Verified on QA. Thanks!

Still testing?