EBMS Tickets

Issue Number 604
Summary Add ability to generate Citation Reports using multiple review cycles by range
Created 2021-07-14 10:01:50
Issue Type Improvement
Submitted By Boggess, Cynthia (NIH/NCI) [C]
Assigned To Kline, Bob (NIH/NCI) [C]
Status Closed
Resolved 2021-07-16 15:28:29
Resolution Fixed
Path /home/bkline/backups/jira/oceebms/issue.294080
Description

Would like to have the ability to generate Citation Reports using multiple review cycles by range, specifically the 4 citation reports below:

  • Citations Published

  • Citations Rejected/Accepted for Publishing

  • Citations Imported

  • Citations Not Selected for Full Text Retrieval

Note: the Citation Summary Topic Changes citation report will not need to be searched by multiple review cycles.

Also this ticket is mentioned/related to ticket 599

Comment entered 2021-07-14 10:13:36 by Boggess, Cynthia (NIH/NCI) [C]

This request extends to the new citation reports:

ticket 579 - new citation report for full text retrieval

ticket 578 - new citation report for citation reviewed by med librarian

ticket 577 - new citation report for citations excluded by NOT journal filters

Comment entered 2021-07-16 11:27:36 by Kline, Bob (NIH/NCI) [C]

I noticed as I was testing my work as I went along for this ticket, I was able to confuse the AJAX which draws the new form fields when you switch back and forth between the different reports on the "Citations Reports" page, resulting in a report form which has the wrong fields for the selected report. I'm able to reproduce the problem on the production system, so I'm confident that this wasn't a result of the new code for this ticket. I don't think it's worth trying to fix the problem now, as we're about to rewrite the EBMS for Drupal 9, and I don't plan to use as much fragile behind-the-scenes magic to stuff multiple reports into the same form when we do that rewrite, so the problem wouldn't survive the rewrite.

Comment entered 2021-07-16 15:28:29 by Kline, Bob (NIH/NCI) [C]

Implemented on EBMS DEV.

Comment entered 2021-07-20 16:11:09 by Boggess, Cynthia (NIH/NCI) [C]

verified on DEV

Comment entered 2021-07-20 17:10:21 by Boggess, Cynthia (NIH/NCI) [C]

Regarding the "Citations Not Selected for Full Text Retrieval" report: I have realized that with the addition of the review cycle range option this report needs to have two "versions"  because we need it to serve two different purposes. Let me try to explain.

The original/current version on prod 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 version as it currently is.

By adding the ability to generate this report by review cycle range, we will be able to generate useful stats. Due to the fact that this new version will be used for stats, we 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 "versions" of data displayed based on whether the user selects to use the decision date range or the review cycle range?

Comment entered 2021-07-26 09:16:52 by Kline, Bob (NIH/NCI) [C]

That would be out of scope for this ticket. Please create a separate one for this request.

Comment entered 2021-09-10 17:42:17 by Boggess, Cynthia (NIH/NCI) [C]

Generating Citation Reports by multiple review cycles works on QA.

Note: there is an issue with the Reset button on the Citation Reports page that Bob mentioned above that he plans to address with the drupal upgrade.

Verified on QA

Comment entered 2021-10-18 14:01:36 by Osei-Poku, William (NIH/NCI) [C]

Verified on PROD. Seems to be working. It is OK to close. Thanks!

Comment entered 2021-10-21 12:26:29 by Shields, Victoria (NIH/NCI) [E]

Verified on PROD. Closing issue.

Elapsed: 0:00:00.000646