EBMS Tickets

1. Would this request add review cycle range fields in addition to the existing single review cycle field, or would the range fields replace the existing review cycle field?

2. Is the request asking for review cycle fields for the Citation Summary Topic Changes report (currently only the other four citation management reports have fields for selecting a review cycle)?

1. In addition to the existing single review cycle field

2. The Citation Summary Topic Changes Report should remain as is. No changes needed.

I just realized that I mis-read the original description, thinking you were asking for modification of the citation reports, rather than all of the citation management reports. Here are the citation management reports which have a Cycle field.

1. Import Report

2. Citations Published

3. Citations Rejected/Accepted for Publishing

4. Citations Imported

5. Citations Not Selected for Full Text Retrieval

6. Citations By Status — Abstract Decision

7. Citations By Status — Full Text Retrieved

8. Citations By Status — Full-Text Decision

9. Citations By Status — Assigned For Review

10. Citations By Status — Board Manager Action

11. Citations By Status — On Agenda

12. Citations By Status — Editorial Board Decision

13. Literature Reviews

Let's restrict the scope of this ticket to the search page (since that's what the ticket's title implies), and open separate tickets for each report which needs to be modified. For items #6-12 on the list above, I would assume that the incentive to add separate cycle range fields is weak, since multi-selection is already support for the cycle picklist, and it's easy to select one end of a range and the shift+click to select the other end. Dropping the LOE estimation for this ticket.

You did not mis-read this request. I was requesting to add this feature to the search the database and the citation reports only, specifically the 4 below:

• Citations Published

• Citations Rejected/Accepted for Publishing

• Citations Imported

• Citations Not Selected for Full Text Retrieval

As previously discussed above, the Citation Summary Topic Changes will not need to be searched by multiple review cycles.

But all five of these citation reports are generated from the same page so do we want a ticket for each report individually or just one for the citation reports page itself which is where we would select the review cycles?

Ah, I see. As you can see from this screenshot, "Citation Management" reports includes many more than just those five reports, so I guess we both were confused.

Each of the four reports you would like to have modified has its own requirements and is implemented separately, so ideally each modification would have its own ticket. Let's compromise and split the report modifications out into a single ticket.

Yes it can be confusing because from my librarian version, I don't see most of the reports in that screen shot above. 

Ok I'll add in a new single ticket for the modifications to the 4 citation reports. Then we will keep this one just for the modifications to the search the database. Correct?

Correct.

But all five of these citation reports are generated from the same page ...

Yes, the same page is used to run all five reports, but that's because the original requirements insisted that we create enough magic behind the curtain to make that page into a Swiss army knife. You'll notice that when you switch between reports the fields get re-drawn as you watch, and each report has different logic. So the impression that this page is just one report is just an illusion, intentionally demanded by the requirements for some impressive sleight of hand. 😉

Implemented on DEV.

verified on dev

I have tested this on QA and everything looks good.

Verified on QA.

Verified on PROD. Seems to working. It is OK to close ticket.

Verified on PROD. Closing ticket.