Issue Number | 540 |
---|---|
Summary | [Reports] New Citations by Tag Report |
Created | 2020-02-06 10:38:21 |
Issue Type | Improvement |
Submitted By | Juthe, Robin (NIH/NCI) [E] |
Assigned To | Kline, Bob (NIH/NCI) [C] |
Status | Closed |
Resolved | 2020-03-02 13:24:18 |
Resolution | Fixed |
Path | /home/bkline/backups/jira/oceebms/issue.256268 |
We would like to create a new report called the Citations by Tag report. This will help us keep track of high priority citations and core journal citations, for example.
I will attach specs for the new report.
Bob will look into the feasibility of excluding system-generated comments from the column of the report (e.g., those that begin with "state inactivated by..." and probably others).
As we just discussed, we'd like to limit the selected tags in this report to those that are applied at the topic level (as opposed to the citation level).
Please keep this report on the menus for medical librarians as well.
For articles that are at the Assigned for Review state, if a Board Manager Comment exists, please add the words BOARD MANAGER COMMENT in red beneath the status description.
There is no Assigned for Review state. Did you mean the Passed full text review state?
I went ahead and implemented the report that way. Here are the
sub-strings I'm using to suppress machine-generated comments. Any
comment which starts with one of these sub-strings (ignoring case) will
be dropped from the report. Let me know if you need would like me to
make any changes to the list.
// Beginning of comments we want to avoid reporting.
= array(
$machine_comments 'status entered by conversion because the topic/article combination',
'published state added as a result of setting the state for this',
'tir 2506 (',
'published as part of import from core journals',
'core journals search',
'delete this journal',
'state inactivated by setting "published" at',
);
Sorry, I was thinking Assigned for Review was a state. What I meant by that value is articles have been included in a packet for a Board member to review but haven't made it past that point (similar to the results that we see on the Articles Without Responses report). Is it possible to treat that as a state?
It's possible but somewhat complicated. Would there be any downside to having the report indicate the presence of manager comments for article/topic combinations which are in the Passed full text review state without figuring out whether the reviews have been assigned yet and whether any of the reviews have been submitted?
Let's discuss this today. I'm not sure if I understand your question.
I don't think we discussed this explicitly in the meeting last week, but if I understand correctly, I don't think there would be any downsides to seeing the presence of a board manager comment regardless of whether it had been included in a packet. The primary purpose of those comments is to tell our Board members something at the time of their review. Sometimes we might add the comment when we first see the paper and other times we might add the comment at the time we are adding the paper to a packet.
While it's preferable to show "Assigned for Review" as a "state", I think we could postpone that to the next release to keep to our schedule.
However, would it be possible to sort the results of this report by summary topic?
And could you please filter out comments that begin with "state inactivated by setting" (a more general version of the comments you are already filtering out)? There are several other possible permutations of that comment that could be removed so this shorter string should catch the others. Thank you.
Additional requirements implemented.
Verified on DEV. Thanks!
Verified on QA.
Verified on PROD.
File Name | Posted | User |
---|---|---|
Citations by Tag Report Specs for JIRA.docx | 2020-02-06 10:54:39 | Juthe, Robin (NIH/NCI) [E] |
Elapsed: 0:00:00.000343