Issue Number | 4558 |
---|---|
Summary | [Summaries] Modify QC reports to make protocol ref links work |
Created | 2018-12-18 15:43:00 |
Issue Type | Improvement |
Submitted By | Osei-Poku, William (NIH/NCI) [C] |
Assigned To | Englisch, Volker (NIH/NCI) [C] |
Status | Closed |
Resolved | 2018-12-20 14:01:13 |
Resolution | Fixed |
Path | /home/bkline/backups/jira/ocecdr/issue.237722 |
Currently the QC reports show protocol refs as links but when you click on the link, it takes you to the non-existent protocol QC report. Could you please modify the QC reports so that the link goes to the destination address?
The following filter has been modified to create a link to ClinicalTrials.gov for the ProtocolRef elements:
CDR339576: Module: InLine Markup Formatter
https://github.com/NCIOCPL/cdr-server/commit/67af7cb454
~oseipokuw, this is ready for review on DEV.
It looks like all the links are going to clinicaltrials.gov even if the trial is on Cancer.gov. Could you please implement the same logic we have in the vendor filters so that if the trial exists on Cancer.gov, the link would go there rather than clinicaltrials.gov?
Here is the sample summary CDR0000062910 I used for testing. Please look for this text "NRG-BR003" in the first protocol ref. in the General Information section.
~oseipokuw, I completely misunderstood what you were asking for. Your sentence "... even if the trial is on Cancer.gov." confused me. I think what you mean is that trials that are part of CTRP should display a Cancer.gov protocol page while those not part of CTRP should link to ClinicalTrials.gov, right?
In looking at the current data on Cancer.gov - example CDR62787, Breast Cancer Treatment (HP) and comparing MINDACT (NCT00433589) with RxPONDER (NCT01272037) - I see that the reason why the non-CTRP protocols are linked to ClinicalTrials.gov is that these are not ProtocolRef elements but ExternalRef elements. There currently isn't any magic to my knowledge that decides which ProtocolRef should link to CT.gov and which to Cancer.gov.
Do you have other samples that I should be looking at instead?
Apologies for the confusion. Please take a look at the "Childhood
Acute Lymphoblastic Leukemia Treatment " HP summary CDR0000062923. The
summary has a ProtocolRef for "COG AALL08B1" in the "Prognostic (risk)
groups under clinical evaluation" section. You can just search for COG
AALL08B1 in the summary either in the CDR or on Cancer.gov. The link to
the summary on Cancer.gov is
https://www.cancer.gov/types/leukemia/hp/child-all-treatment-pdq#section/all
If you search for "COG AALL08B1", the link will go directly to Cancer.gov. However, compared to "CCG-1961 [NCT00002812]" in the same summary as a protocolref, this link goes to clinicaltrials.gov because the CCG-1961 [NCT00002812] clinical trial is not on Cancer.gov from CTRP.
Another example is NCI-2014-00712; AALL1231
I think this Jira ticket OCECDR-3869 has information on what we did to the protocols when we stopped getting data from CTRP and started using the API.
Thanks, ~oseipokuw. The problem is that Cancer.gov is doing the redirection, so all I had to do is to point to Cancer.gov instead of pointing to CT.gov.
This has been fixed on DEV and is ready for review.
The changes have been pushed to github:
https://github.com/NCIOCPL/cdr-server/commit/ca2ea83
Verified on DEV. Thank you!
The changes have been copied to QA and are ready for review.
Verified on QA. Please Install on STAGE so I can test with OCECDR-4551.
The filter has been copied to STAGE.
Verified on STAGE. Thank you! Ready for PROD.
The following filter has been copied to PROD:
CDR339576: Module: InLine Markup Formatter
Please verify on PROD and close this ticket.
Verified on PROD. Thank you!
Elapsed: 0:00:00.001460