Issue Number | 5065 |
---|---|
Summary | Remove Audience Toggle Filter Change |
Created | 2021-10-28 20:58:24 |
Issue Type | Task |
Submitted By | Englisch, Volker (NIH/NCI) [C] |
Assigned To | Englisch, Volker (NIH/NCI) [C] |
Status | Closed |
Resolved | 2021-11-24 20:02:10 |
Resolution | Fixed |
Path | /home/bkline/backups/jira/ocecdr/issue.301504 |
We want to ensure that the audience toggle between patient and HP version is removed from the SVPC documents being send to Drupal.
The rule should be that no SVPC document will link to a HP document and no HP document should link to a SVPC document.
I started to implement a new is_svpc_summary
custom
XSL/T function for this purpose, and then I realized you already have
what you need with the existing sql_query
function. You'll
need to add a query term definition for the "/Summary/@SVPC" path, then
reindex the three sample SVPC documents (not worth it to run the reindex
script for all the summaries just to get three documents indexed), and
then invoke the sql_query
function to get the value of the
attribute if it exists.
The following filter has been modified to suppress the creation of the audience toggle if one of the pairs is a SVPC or partner document:
CDR000157.xml - Vendor Filter: Summary
https://github.com/NCIOCPL/cdr-server/commit/b363de
How do I test this? I don't think I will be be able verify this with pub preview.
If the publishing output includes the element SummaryToggleURL within the SummaryMetaData block, the audience toggle will be created, even as part of the PP report. If that element does not exist, the toggle won't be created.
Verified on DEV. Thanks!
Verified on QA and PROD. Thanks!
File Name | Posted | User |
---|---|---|
Screen Shot 2021-12-06 at 16.39.04.png | 2021-12-06 16:44:17 | Englisch, Volker (NIH/NCI) [C] |
Elapsed: 0:00:00.001333