CDR Tickets

Issue Number 5132
Summary Use new EVS property name
Created 2022-08-18 15:16:31
Issue Type Improvement
Submitted By Kline, Bob (NIH/NCI) [C]
Assigned To Kline, Bob (NIH/NCI) [C]
Status Closed
Resolved 2022-08-18 15:46:13
Resolution Fixed
Path /home/bkline/backups/jira/ocecdr/issue.325518
Description

Without any advance warning the EVS team has broken our software by renaming the termGroup property to {}termType{}. We need to modify all of our software which depends on this property.

Comment entered 2022-08-18 15:46:13 by Kline, Bob (NIH/NCI) [C]
Comment entered 2022-08-18 16:51:00 by Kline, Bob (NIH/NCI) [C]

Fixed on DEV.

Comment entered 2022-08-29 15:10:36 by Kline, Bob (NIH/NCI) [C]

Additional background information for testing: the breaking change resulted in the CDR software being unable to identify the types of the various names for a term. If you look at the Synonym Details tab on the NCIt page for a concept, the third column has the values in question which the EVS change prevented us from finding.

Comment entered 2022-08-29 15:12:52 by Kline, Bob (NIH/NCI) [C]

Looks like Jira dropped the ball on the image move. Let me know if the text comment isn't sufficient.

Comment entered 2022-09-06 13:41:02 by Osei-Poku, William (NIH/NCI) [C]

Hi What is a good way to test of verify this fix? Thanks!

Comment entered 2022-09-06 14:05:58 by Kline, Bob (NIH/NCI) [C]

Same advice as I gave for testing on DEV.

*

Use new EVS property name (best way to test this is for the staff with expertise in the drug terminology to use the new drug term review tools to import fresh data from the EVS and determine by inspecting the concept information in the NCI Thesaurus whether the expect values are stored in the resulting CDR Term documents; see the Jira ticket for additional background information on the problem)

Comment entered 2022-09-06 14:56:20 by Osei-Poku, William (NIH/NCI) [C]

Verified on QA. Thanks!

Elapsed: 0:00:00.001929