| Issue Number | 606 |
|---|---|
| Summary | Citations Not Selected for Full Text Retrieval - two options for report |
| Created | 2021-08-04 07:58:15 |
| Issue Type | Improvement |
| Submitted By | Boggess, Cynthia (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2021-08-19 12:45:31 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/oceebms/issue.295774 |
Spin off from ticket 604.
We would like for the "Citations Not Selected for Full Text Retrieval" report to have two options because it will serve two different purposes.
The original/current option is used to analyze individual citations not selected for full text retrieval which is why we need the ebms id, pmid, summary topic, reviewer and comments included in this report. And it is generated using a decision date range to capture more specific sets of citations than a review cycle could. We want to keep this option as it currently is.
By recently adding the ability to generate this report by review cycle range, we will be able to generate useful statistics. This new option generated using review cycle range for statistical purposes, will only need the summary topic and citation count included in the report...much like the new "Citations Selected for Full Text Retrieval" report.
Is it possible for the "Citations Not Selected for Full Text Retrieval" report to have two different options?
Option 1: the user selects the decision date range. The report generated includes: the ebms id, pmid, summary topic, reviewer and comments
Option 2: the user selects the review cycle range. The report generated includes: the summary topic and citation count
What should the software do if neither range is selected and a specific review cycle is selected instead? Should the report behave as it always has (since that case has always been supported) or should it follow option 2 (since selecting a specific review cycle is closer to specifying a review cycle range than specifying a decision date range)?
Good question, yes the report should behave as it always has when a specific review cycle is selected.
In terms of use/purpose, selecting a specific review cycle is closer to a decision date range.
Implemented on DEV.
verified on dev
verified on QA
Verified on PROD. Thanks! Closing ticket.
Elapsed: 0:00:00.000653