| Issue Number | 5057 |
|---|---|
| Summary | Create new macros for summaries related to one SVPC summary topic |
| Created | 2021-10-21 10:27:12 |
| Issue Type | New Feature |
| Submitted By | Osei-Poku, William (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2021-10-28 12:37:49 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.300987 |
As a patient summary editor, I want to be able to launch a macro in XMetal so that I can identify all summaries that comprise a single SVPC topic like the liver cancer SVPC summary.
The current PDQ patient liver cancer treatment summaries would be split into multiple SVPC summaries that would be published as their own separate pages on Cancer.gov with their own URLs. In XMetal, these would be their own individual CDR documents. We want the ability to be able to click on a macro icon, while in the master summary document, that will show all the summaries on a given topic that have been split into their own individual summaries.
Scenario: XMetal has a new macro to open all summaries related to a SVPC summary topic in edit mode
Given I am a patient summary editor
And I have permissions to create summaries
And I have permissions to edit summaries
And I have retrieved a master partner summary document
When I click on the “Edit SVPC summaries” macro icon
Then XMetal should check out all related summaries to me for editing
Scenario: XMetal has a new macro to open all summaries related to a SVPC summary topic in read only mode
Given I am a patient summary editor
And I have permissions to create summaries
And I have permissions to edit summaries
And I have retrieved a master partner summary document
When I click on the “View SVPC summaries” macro icon
Then XMetal should retrieve all related summaries in read only mode
If this is supposed to work the way the existing macros work for opening the linked glossary term name documents then one thing that's missing from your scenarios/givens/description is that the current editing window contains the corresponding partner master document. I realize that at the outset there's only going to be one of those, but you don't really want us to implement the software to only work for that summary, do you?
Also, you need to pick the two toolbar icons to be used for the macros.
I have updated the scenarios accordingly. For the icons, please use these:
Cdr
SVPC Summaries Macro - Column5/Row3 (scenario 1)
Edit SVPC Summaries Macro - Column4/Row5 (scenario 2)
View SVPC Summaries Macro - Column1/Row5 (scenario 3)
Could you please unlock the partner master document so I can fix the structure? Also, I can see the incentive to implement the "Edit" and "View" macros, but what's the value add for a macro to find the IDs of the linked SVPC summaries when they're right there in the document you're looking at, all collected together in one place already?
From which block?
From which block?
From the Cdr block as I mentioned above.
Cdr
SVPC Summaries Macro - Column5/Row3 (scenario 1)
Edit SVPC Summaries Macro - Column4/Row5 (scenario 2)
View SVPC Summaries Macro - Column1/Row5 (scenario 3)
I can see the incentive to implement the "Edit" and "View" macros, but what's the value add for a macro to find the IDs of the linked SVPC summaries when they're right there in the document you're looking at, all collected together in one place already?
Agreed. This will be more useful when you're in one of the SVPC summaries. You can ignore that. I will include it if we ever want a macro within a SVPC summary to identify all related SVPC summaries.
I have removed first scenario about viewing the CDR IDs from the descriptions.
Implemented and installed on CDR DEV.
Verified on DEV. Thanks!
I am no longer able to see the new macros while in the partner document.
That's right. You asked me to implement these macros for the Oersted release back in October, which is when I implemented them and installed them on DEV and you tested them and marked them "Verified on DEV." Then the following month you asked me to implement a new macro (OCECDR-5068) for the Ohm release, which I subsequently implemented and installed on DEV. You tested that one as well and marked it "Verified on DEV." Since two branches of a file can't both be installed on a single tier at the same time, you can't have the macros for Oersted and the macro for Ohm simultaneously installed on DEV, and since the Ohm macro was requested, implemented, and installed after the ones for Oersted, that's the one which is on DEV. This is one of the reasons we're installing Oersted on QA, so we can isolate it from the other releases which are in flight.
OK. I will verify this on QA when Oersted is arrives on QA. Thanks!
Verified on QA and PROD. Thanks!
Elapsed: 0:00:00.001538