Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publication Specification doesn't work #77

Open
siyamalan opened this issue Jun 4, 2019 · 5 comments
Open

Publication Specification doesn't work #77

siyamalan opened this issue Jun 4, 2019 · 5 comments
Labels

Comments

@siyamalan
Copy link

Description

A single analysis specification can be assigned while creating analysis request.
The problem is that a single product tested by lab can have multiple specifications.

Being able to change "Publication Specification", hence having desired specifications in published report would absolutely solve this problem.

Reproduction guide

  1. Created a new sample request

  2. Assigned analysis specification

  3. Entered the results

  4. Published the report

  5. Changed the "publication specification" again

  6. Published the report again

Observed behaviour

After saving publication specification, the "specification" changed but the "Range" did not change
image

Expected behaviour

The Range should be different in published report

Versions

  • OS: Ubuntu Server 18.04.2 LTS

  • senaite.core: 1.3.1

  • senaite.impress: 1.2.0

  • senaite.core.listing: master

  • senaite.core.supermodel: master

@xispa xispa transferred this issue from senaite/senaite.core Jun 12, 2019
@xispa
Copy link
Member

xispa commented Jun 12, 2019

@siyamalan
Copy link
Author

Thanks for the reply @xispa
I have tried default+multi-default templates. My problem is "The range is unaffected by publication specification".

As shown in below picture, "Specification changes when I change publication specification but not the range. The publication specification I assign should also change the range

image

@siyamalan
Copy link
Author

siyamalan commented Jun 25, 2019

@xispa

default.pt or any other template is pulling only the analysis spec. They are not pulling publication spec

<td class="specs"> <span tal:condition="analysis/Uncertainty" tal:content="structure python:model.get_formatted_uncertainty(analysis)"></span> <span tal:content="python:'(RT)' if model.is_retest(analysis) else ''"></span> <span tal:content="python:model.get_formatted_specs(analysis)">50 - 60</span>

@xispa xispa added the Bug label Jun 26, 2019
siyamalan added a commit to siyamalan/senaite.core that referenced this issue Jul 14, 2019
Getting the specs from publication specification instead of analysis Specification solves this issue (senaite/senaite.impress#77)
@siyamalan
Copy link
Author

siyamalan commented Jul 14, 2019

@xispa Getting the specs from publication specification instead of analysis Specification solved the above issue for me.

I made below changes and disabled the analysis specification completely,
siyamalan/senaite.core@e027647

Below is how things are working for me :)

  1. I can use Publication specification instead of Analysis specification to set specification while creating an analysis request
  2. Once results are entered and verified, specification (specs) in "View" does not change (regardless of publication specification)
  3. After verification, after publication, I can come back to any analysis request and publish report with any specification I require

@xispa
Copy link
Member

xispa commented Jul 16, 2019

Funny. So with this change you've done , the analyses keep their own specs (e.g. defined on Sample creation), but the publication specs are displayed in the report.

Nevertheless, keep in mind that if you add a new analysis in that Sample, that new analysis will acquire the publication specifications, rather than the defaults. Also, when you do any of these:

  • Reject/Invalidate the Sample
  • Copy to new
  • Create partitions
  • Create a secondary

the specification of the resulting sample will be the primary's publication specification.

siyamalan referenced this issue in siyamalan/senaite.core Jul 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants