CDR Tickets

Issue Number 4612
Summary [DIS] Processing Status Block
Created 2019-05-08 13:46:21
Issue Type Improvement
Submitted By Osei-Poku, William (NIH/NCI) [C]
Assigned To Kline, Bob (NIH/NCI) [C]
Status Closed
Resolved 2020-04-18 08:58:37
Resolution Fixed
Path /home/bkline/backups/jira/ocecdr/issue.243854
Description

Please modify the DIS schema to include a new optional Processing Status Block that is multiply occurring. 

The elements within this block would be:

  • ProcessingStatusValue *

  • StatusDate

  • EnteredBy

  • Comment

 

 

The list of values are :

  • Needs glossary draft review

  • Glossary draft review complete

  • DIS to expert reviewer

  • Needs DailyMed link

  • DIS OK to publish

  • DIS needs QC on cancer.gov

  • DIS QC on cancer.gov complete

Comment entered 2019-05-16 11:20:58 by Osei-Poku, William (NIH/NCI) [C]

Revised requirements document to clarify that Processing Status Date would be the Status Date from the Processing Status Block.

Comment entered 2019-05-21 12:04:36 by Osei-Poku, William (NIH/NCI) [C]

Removed attachment. It was not meant for this ticket.

Comment entered 2019-06-27 10:45:24 by Kline, Bob (NIH/NCI) [C]

Are you aware that there's already a ProcessingStatus string element in the DIS schema? Also, I think the attachment you meant to remove is still attached.

Comment entered 2019-06-27 12:55:21 by Osei-Poku, William (NIH/NCI) [C]

 Are you aware that there's already a ProcessingStatus string element in the DIS schema? 

 

The element allows for only free text. What we are asking for is a new block with the provided child elements. We may have to do a global to copy the text in the current processing status element into a comment element, as it appears users have used it primarily to capture processing comments, and delete the existing processing status element.

Comment entered 2019-06-29 09:03:28 by Kline, Bob (NIH/NCI) [C]

William will be moving this ticket into the Kepler release, along with the ticket for the report (OCECDR-4613) and a new ticket he will create for the global change needed for preserving the data in the existing element.

Comment entered 2020-04-17 14:03:44 by Osei-Poku, William (NIH/NCI) [C]

I have created the new ticket for the global OCECDR-4816.

Comment entered 2020-04-17 17:01:39 by Kline, Bob (NIH/NCI) [C]

Since you didn't specify where the new block should go, you're going to accept the location I pick, right, ?

Comment entered 2020-04-17 17:06:23 by Kline, Bob (NIH/NCI) [C]

And I assume you don't care which child elements are required, right?

Comment entered 2020-04-17 17:09:01 by Kline, Bob (NIH/NCI) [C]

I've made Comment optional, and the rest required.

Comment entered 2020-04-17 17:22:52 by Kline, Bob (NIH/NCI) [C]

Installed on DEV.

Comment entered 2020-04-17 19:14:00 by Osei-Poku, William (NIH/NCI) [C]

I couldn't find the new block on DEV. Please place it after the after the Date Last Modified element. That is where the current string element is.

Comment entered 2020-04-17 19:56:06 by Kline, Bob (NIH/NCI) [C]

Are you sure you're on DEV?

Comment entered 2020-04-17 19:57:29 by Kline, Bob (NIH/NCI) [C]

And once again, if you care enough about an aspect of how a ticket is implemented, it's always a good idea to convey that information before implementation. 🙂

Comment entered 2020-04-18 08:58:37 by Kline, Bob (NIH/NCI) [C]

If you really can't find the new block, please provide detailed descriptions of each of the steps in what you're doing.

Comment entered 2020-04-20 13:40:35 by Osei-Poku, William (NIH/NCI) [C]

Verified on DEV. The reason I wasn't seeing it was because the CSS has been modified to add the child element. I have created a ticket for that OCECDR-4818.

Comment entered 2020-06-05 15:16:48 by Osei-Poku, William (NIH/NCI) [C]

Verified on QA. Thanks!

Attachments
File Name Posted User
image-2020-04-17-19-55-54-625.png 2020-04-17 19:55:55 Kline, Bob (NIH/NCI) [C]

Elapsed: 0:00:00.001733