| Issue Number | 5043 |
|---|---|
| Summary | Modify the CDR Summary Schema to link multiple SVPC summaries to form one Master Partner Summary |
| Created | 2021-10-15 11:51:15 |
| Issue Type | New Feature |
| Submitted By | Osei-Poku, William (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2021-10-27 09:58:00 |
| Resolution | Won't Fix |
| Path | /home/bkline/backups/jira/ocecdr/issue.300627 |
As a CDR patient summary editor, I want to be able to associate multiple SVPC CDR summaries to constitute one Master Partner summary so that they can be assembled for our PDQ content partners.
The current PDQ patient liver cancer treatment summaries will be split into multiple summaries that would be published as their own separate pages on cancer.gov. We are currently working on being able to create the individual SVPC summaries in the CDR. These summaries would be combined to form one master Partner summary in the CDR, and it will be used by the vendor filters to form one summary for the PDQ content partners.
We want a mechanism to associate these multiple summaries as one master partner summary.
Given I am CDR patient summary editor
And I have permissions to create summary documents
And I have permissions to edit summary documents
When I create a new master partner summary
Or when I edit an existing master partner summary
Then I want to be able to associate multiple individual SVPC summaries with the master partner summary
Given I am a CDR patient summary editor
And I have permissions to create summaries
And I have permissions to edit summary documents
And I create multiple SVPC summaries
When I create a new master partner summary
Then the CDR should allow me to associate them to constitute one master partner summary.
Given I am a CDR patient summary editor
And I have permissions to create summaries
And I have permissions to edit summary documents
When I mark one or more SVPC summaries to be removed from the master partner summary
Then the CDR should allow the removal of the SVPC summaries from the master partner summary
I have looked at the Summary schema and I don't think we
need to modify it in order to be able to link to the individual SVPC
summaries. We can (as someone suggested at yesterday's status meeting)
use the SummaryModuleLink which appears to support what
will need to do. We will want to modify the schema, whether as
part of this ticket, or for a separate ticket, to add a top-level
attribute to the Summary document identifying the summary
as a master partner document, so that we'll know to skip it when we're
pushing Summaries to our own web site.
It might help to avoid any confusion by creating a new link type that is specific for SVPC summaries since the SummaryModuleLink is named specifically for module documents and the SVPC summaries are not modules. For example, we can name the new link type SVPCSummaryLink.
What distinguishes the SVPC summaries from any other summary which can be used either as a module or as a standalone summary?
I understand that they are both summaries but that is not what I am referring to. I am referring to how the SummaryModuleLink is named specifically after module documents. If creating a new link specific to SVPC summaries is a problem, then perhaps using the SummaryRef is a better alternative. I like the SummaryRef element because the name is generic enough to apply to all summaries and since this link is going to be used only for the partner contents, it should not pose any problems, hopefully.
So do we only use SummaryModuleLink for summaries that
are "module only"? I just don't understand what the problem would be
with marking the SVPC summaries as modules if they're going to be used
as modules (which is what we'll be doing when we pull them into the
document we send to the partners). I must be missing some
subtlety. 😛
I do see ~oseipokuw's point. From an editor's perspective a module is a document that's pulled into a summary but the SVPC summaries aren't pulled into any summary that's published on Cancer.gov.
On the other hand, looking from the partner output perspective every summary is a module that's pulled into the "master" summary.
The current denormalization marks every summary module as such to distinguish the content from the parent. I have to double check on this but I believe we will need to add additional criteria as part of the denormalization if we start to treat every single summary as a module, including those that include "non-SVPC modules".
We will not link any summary that has not been marked as "AvailableAsModule" Or "ModuleOnly" using the SummaryModuleLink. So, if we have not marked the SVPC summary as either "AvailableAsModule" or "ModuleOnly" , we probably should not link it using the SummaryModuleLink for consistency.
We concluded in the October 21 status meeting to go with using the summary module link (marking the split out SVPC summaries as "AvailableAsModule"), leaving the schema as it is.
Verified on QA and PROD. Thanks!
Elapsed: 0:00:00.001444