| Issue Number | 688 |
|---|---|
| Summary | Articles by Tag Report - comment search not working |
| Created | 2023-01-10 10:09:49 |
| Issue Type | Bug |
| Submitted By | Boggess, Cynthia (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2023-01-10 19:02:00 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/oceebms/issue.336007 |
In the Articles by Tag Report there is an option to limit the report by comment. This does not seem to be working. The following citation has one tag comment in erc and two in ebms4 and is not retrieved in either when a comment is used to generate the report.
from ebms4
Abramson JS, Solomon SR, Arnason JE, et al.
Lisocabtagene
maraleucel as second-line therapy for large B-cell lymphoma: primary
analysis of phase 3 TRANSFORM study.
Blood, 2022
PMID: 36542826
Current state: Passed full text review
Tag assigned 2023-01-05
Comment: Published because of import from core journals
Comment: testing tag
I have tried using %test%, %testing%, %published% in combination with
board and topic and date tag assigned.
Whew! This report is a doozey. I think it's working correctly now, but the logic is pretty twisty, especially in the wake of OCEEBMS-575, so I tried testing as many paths as I could think of (as I'm sure you will).
You did well to narrow further (by topic and dates). At least one of those is needed when searching for %published% because the system automatically generates untold numbers of comments matching that pattern, and if you only narrow by board the report is likely to just curl up into a ball and expire.
Thanks for catching and reporting this.
I tried all sorts of combinations. As you said the comment will work as long as either date tag assigned or summary topic is included. If either or both are excluded the report fails.
Unfortunately, there seems to be a new bug on the page. When I search just board and tag (which was working yesterday) the report fails for some tags but not all. For example, it works for import special search, high priority, and comment for librarian, but fails for core journals, import fast track and not reviewed.
Yes, I see. I'm pretty sure that's probably the server not dealing well with the fact that we've never had paging for this report, and some queries generate more results than can be swallowed in one gulp. I think we have two paths we could take.
We use filters that avoid huge results sets. Downside: can be annoying at times.
We add paging. Downside: I won't be able to display the fancier count information I've added to the report, showing how many articles (I'll just be able to display how many rows the query count gives me).
We can discuss the pros and cons (perhaps in a wider forum) and come to a decision about which path to take. If we ultimately decide on path #2, that will be a separate ticket. TBD.
Agreed this will require more thought and discussion.
I primarily use the Article Search for any of my tag related info needs so I do not have a preference at this time.
The BMs definitely use this report more than I do so let's wait for their input.
This is preforming better on ebms4 than it was on erc. I have tried a variety of combinations and they are all working, even with larger retrieval where topic or date is not set as a report criteria. I think we need to keep an eye on this report, but for now it seems to be working well in ebms4.
Elapsed: 0:00:00.000686