| Issue Number | 57 |
|---|---|
| Summary | Fast Track |
| Created | 2013-09-17 13:58:21 |
| Issue Type | Improvement |
| Submitted By | trivedim |
| Assigned To | |
| Status | Closed |
| Resolved | 2014-05-28 17:42:00 |
| Resolution | Won't Fix |
| Path | /home/bkline/backups/jira/oceebms/issue.113369 |
TIR #2424 entered 2013-03-04 by Minaxi Trivedi (Future Release status)
If a citation that is currently already in my que is fast tracked, that citation gets fast tracked but remains in my queue. Where as it should be removed from the queue. This may also apply to board manager’s que as well.
Kline, Bob (NIH/NCI) [C]No presence information (3/8/2013 2:08 PM):
The import software applies fast-track processing to new articles which
are entering the system for the first time, as well as to articles which
are already in the system, but for a different topic than the topic used
for the current import request. Because it is unclear whether overriding
the status for an article which is already in the system for the same
topic being applied for the current import job (and for which the
existing status could well be already far downstream from the status
selected for the fast-track job) would be the appropriate behavior, Alan
told me to avoid applying fast-track processing to these duplicate
articles-topic combinations. Analysis to determine whether this behavior
should be changed, and if so, in what way, has been deferred to a
subsequent release.
Trivedi, Minaxi (NON NIH) [C]No presence information (3/7/2013 10:31
AM):
Trivedi, Minaxi (NON NIH) [C]No presence information (3/4/2013 3:51 PM):
Robin tested these citations and they are removed from her queue. So
this is the problem in Medical Librarian's queue only.
Trivedi, Minaxi (NON NIH) [C]No presence information (3/4/2013 9:40
AM):
Robin:
We need you to weigh in with a decision about whether the software should override the status for an article which is already in the system for the same topic for which fast-tracking is being requested (and for which the existing current status could well be already far downstream from the status selected for the fast-track job).
Thanks.
Cynthia and Minaxi reviewed this issue and Cynthia provided the following comment:
This issue was reported before the release. After using the system for some time, Minaxi and I both agree that this is most likely no longer a problem. This issue is not exactly something we can easily test, so I think we should just keep it in mind and if we notice it in the future we will report it. But for now I think we can close this issue.
Elapsed: 0:00:00.000576