CDR Tickets

Issue Number 5054
Summary Modify Publishing Document
Created 2021-10-18 19:45:52
Issue Type Task
Submitted By Englisch, Volker (NIH/NCI) [C]
Assigned To Englisch, Volker (NIH/NCI) [C]
Status Closed
Resolved 2021-11-24 10:37:08
Resolution Won't Fix
Path /home/bkline/backups/jira/ocecdr/issue.300786
Description

When we're publishing the modified Liver Cancer summaries we will have to deal with three different types of summaries to be published:

  • Legacy Summaries
    Our current, unmodified summary documents

  • SVPC Summaries
    Small summaries split up from a larger one

  • Partner Summaries
    Document combining the SVPC summaries to resemble the legacy documents

Since each of these groups will need to be handled a little bit differently (legacy documents are pushed to Cancer.gov and the FTP server, SVPC documents are only pushed to Cancer.gov, and partner documents are only pushed to the FTP server) we will need to process these sets individually.  
This requires the publishing document to be modified accordingly.

Comment entered 2021-10-19 09:24:39 by Osei-Poku, William (NIH/NCI) [C]

My understanding is that the Legacy summaries will be blocked when the SVPC summaries are published to Cancer.gov. That is at the same time, since they do not have to live on Cancer.gov at the same time. We probably need clarification on this.

Comment entered 2021-10-19 10:57:42 by Englisch, Volker (NIH/NCI) [C]

No, , your understanding is not correct.  Please refer to the latest diagram I prepared.  If the legacy document is CDR256491 and we're creating the SVPC documents CDR900001, CDR9000002, and CDR900003 from this document then we will need to publish the new SVPC documents to be published to Cancer.gov.  In addition, the legacy summary document will be converted while keeping the original CDR-ID and importing the three SVPC documents in order to create the partner output.  If we were to block the legacy summary the partner wouldn't receive a liver cancer treatment summary anymore.

If you are thinking of "blocked" as not to be published to Cancer.gov then you are correct but the document can't be "blocked" as in "Block Publication" because then it wouldn't be picked up for any type of publishing anymore.

Comment entered 2021-10-19 11:31:57 by Osei-Poku, William (NIH/NCI) [C]


If you are thinking of "blocked" as not to be published to Cancer.gov then you are correct but the document can't be "blocked" as in "Block Publication" because then it wouldn't be picked up for any type of publishing anymore.

Thanks for the clarification  This is the way we understand it when a document is "blocked" in the CDR. That is, we block the document so that it is not published to Cancer.gov or taken off Cancer.gov (which I believe is a separate step on your end). However, when we block a document from going to Cancer.gov, we have to use the "Block Publication of Any version of This Document" function in XMetal. So, it looks like we can't use that function for this document but I am sure you will find a way to "block" it the way you want it 🙂.

Comment entered 2021-10-19 11:41:44 by Englisch, Volker (NIH/NCI) [C]

That's correct!  That's what this ticket is for to modify the publishing queries so that the correct set of documents will be picked up for the different publishing paths.

Comment entered 2021-11-24 10:37:08 by Englisch, Volker (NIH/NCI) [C]

The publishing software has been modified in such a way that a change to the publishing document isn't necessary.

Closing ticket.

Elapsed: 0:00:00.001439