Issue Number | 3944 |
---|---|
Summary | [Summaries] Identifying Key References |
Created | 2015-07-17 18:00:20 |
Issue Type | New Feature |
Submitted By | Juthe, Robin (NIH/NCI) [E] |
Assigned To | Juthe, Robin (NIH/NCI) [E] |
Status | Closed |
Resolved | 2018-02-08 14:29:25 |
Resolution | Won't Fix |
Path | /home/bkline/backups/jira/ocecdr/issue.165467 |
The Adult Treatment Board is interested in identifying "key" references in their summaries - approx. 10 or so references that are crucial to understanding the treatment of each cancer. This needs more discussion before a solution is implemented, so I'm adding the issue to encourage us to do just that.
I should mention that the goal is to make this designation visible on Cancer.gov so readers can quickly see what the Board deems to be the most important references on that topic.
This would be for health professional summaries. Possibly with some way to get to the information on the web site. Maybe add an attribute to the citation links in the summaries.
This would be for health professional summaries. Possibly with some way to get to the information on the web site. We discussed the approach of adding a separate block in the summary schema for KeyCitations, with KeyCitation children. This way, the citations could be ordered by importance. The approach also avoids problems introduced if we were to implement this by adding an attribute to the existing citations (some citations appear in multiple places in the summary). Consider implementing a voting system in the EBMS, or some other mechanism for board members to flag citations they think of as key references.
KeyCitations>
<KeyCitation cdr:ref="CDR...">
<Comment>...</Comment>
<Comment>...</Comment>
<KeyCitation>
</
...KeyCitations> </
KeyCitations block added on DEV.
Had to change the KeyCitation's linking attribute from
cdr:ref
to cdr:href
- otherwise our Comments
get replaced with the document titles for the citations.
You'll need a ticket for Volker to format the display of the new elements in XMetaL (and perhaps one for the QC report).
We'd like to back out these changes from version control. We'll consider doing something with key references in the next CDR release.
Hi Bob, just a reminder that we decided to back out this change from Darwin. Thanks.
Backed out of DEV and SVN.
From status meeting: Removed from Darwin, users will reassess what's needed.
I'm moving this into Gauss, based on Robin's comment on March 3 of last year. Though perhaps that's wrong, since it was not included in Einstein. Let me know if this should be closed instead, ~juther.
Elapsed: 0:00:00.001360