Re: [bika-users] [bika-design] Date Analysed on AR Views

[lemoene <le...@bi...>]

  Thanks Uditha for your valuable feedback

> For many reasons, we would like to see the actual time the analysis 
> results were captured displayed in the to be 
> verified/verified/published AR Views as well as the final report. 
> Ideally this should be the actual time the analysis was performed, but 
> time captured is a close enough approximation. This time is already 
> available in audit logs as review_state: attachment_due so should not 
> be difficult to implement it.

I am adding this to the 'bug' tracker, it is indeed a small modification.

    Before you log any further issues yourself, note that we have are in
    the process of migrating our on-line development environment,
    including code repositories and the trackers, to Github from
    SourceForge. SF served us very well, is a bit slow though through
    hosting  more than 300 000 OS projects at the moment, but Git, the
    'social coding' brainchild of Linus Torvalds himself, is much more
    modern and a lot easier for coordinating distributed projects such
    as Bika.

    We'll be posting more about the migration on a separate thread soon.
    Bika lives at https://github.com/bikalabs

> "Date published" may occur much later than "Date Analysed" and usually 
> indicate some problem. Indication of both may help lab mangers to 
> identify issues in the work flow.

Where the expected turn-around times (TAT) are configured for analyses, 
the late analysis alerts will highlight the problems you mention. The 
TAT is calculated form sample receipt to results verification.

Note that the data currently in the Bika 3 demo don't illustrate late 
analysis alerts properly - there are 280... - and that's because we 
entered a lot of analysis requests but did not process the bulk of them.

Have a good weekend!
lemoene