bika-users — bika end users

[bika-users] Useful (from monologue continued:) at users.bikalims.org

[Bika, S. a. O. S. L. d. <bik...@li...>]

Customisations under way of some already. Please provide  feedback. Others
to be sponsored offer collaboration opportunities, and then realisation

*2017 ISO 17025. Statement of Conformity*
<https://users.bikalims.org/index.php?p=/discussion/14/2017-iso-17025-statement-of-conformity#latest>
*Bookmark*
<https://users.bikalims.org/index.php?p=/discussion/bookmark/11/Yab53Tjlh98skIli>*Subcontracting
Lite. Stub*
<https://users.bikalims.org/index.php?p=/discussion/11/subcontracting-lite-stub#latest>
*2017 ISO 17025. Statement of Conformity
<https://users.bikalims.org/index.php?p=/discussion/14/2017-iso-17025-statement-of-conformity#latest>21
CFR Part 11's Electronic Signatures
<https://users.bikalims.org/index.php?p=/discussion/12/21-cfr-part-11s-electronic-signatures#latest>Proprietary
vs Open Source LIMS pricing
<https://users.bikalims.org/index.php?p=/discussion/10/proprietary-lims-pricing#latest>
<https://users.bikalims.org/index.php?p=/discussion/10/proprietary-lims-pricing#latest>
<https://users.bikalims.org/index.php?p=/discussion/10/proprietary-lims-pricing#latest>Bulk
Sample import to Batch. Bika Vet. Patient server
<https://users.bikalims.org/index.php?p=/discussion/13/bulk-sample-import-to-batch-bika-vet-patient-server#latest>*


Finally a news bulletin again, *Actually. That took a bit longer*
<https://www.bikalims.org/news/actually-that-took-a-bit-longer>,
carries Shaun's
Bika Dairy <http://greenhilllabs.co.za/> at GreenHill lab's information.
Bests, l

[bika-users] Back... Part 11 Electronic Signatures

[Lemoene S. <le...@bi...>]

Please review, comment at  21 CFR Part 11's Electronic Signatures
<https://users.bikalims.org/index.php?p=/discussion/12/21-cfr-part-11s-electronic-signatures>
.

Bests, L

[bika-users] Good bye and thank you for the fish. Subcontracting Lite

[Lemoene S. <le...@bi...>]

Hi All

Am trying out this post at users.bikalims.org, will be saying sad goodbye
to Intarweb legends Sourceforge and GNU Mailman soon

 *Subcontracting Lite
<https://users.bikalims.org/index.php?p=/discussion/11/subcontracting-lite-stub>*

Just to let you know that the 2017 ISO 17025 COAs are spawning embryonic
Analysis Subcontracting (please pick up and expand:)

The COA only has to differentiate between local and subcontracted results.
Identification of different sub contractors is not required (yet). Easy to
do and and with enough information to use elsewhere too, a stub for
eventual Subcontracting workflow:

Each *Analysis Service* gets a *Contracted to field, *defaulted to Internal and
else be populated with a look-up on *Suppliers, *where the Contractors
should be captured already

Thoughts?


<https://users.bikalims.org/index.php?p=/discussion/11/subcontracting-lite-stub>

[bika-users] The plot thickens... re ISO 2017 17025 COA design

[Lemoene S. <le...@bi...>]

Hi All

More gaps are plugged in the 2017 ISO 17025 single sample COA in design
<http://article.media/coa3> (updated), some rather deep going

   - Field Analyses are back, and integrated into Analysis

*Location *
   - Subcontractors Lite - simple first steps towards full Subcontracting
   functionality. More information in Improvement Request
   <https://jira.bikalabs.com/browse/LIMS-3125>

   - In Bika/Senaite workflow, where clients can look-up results online
   after *Verification*, the *Verifier *user is actually the ISO required
   Publisher

   - Compliance. Specifications and Uncertainties
   <https://jira.bikalabs.com/browse/LIMS-3126>. The algorithm Bika uses
   Analysis/Product Specifications only to determine whether a result is in
   Range or not, is not entirely correct....

   - Republication of COAs will have to be revisited, the fresher copy must
   reference previous COAs and indicate that they are being replaced

Is becoming a hefty piece of customisation, all contributions welcome

Bests, Lemoene

New forum currently being configured at https://users.bikalims.org/vanilla,
feel free to have a go already





<http://article.media/coa3>

<http://article.media/coa1>

On Thu, 30 Jan 2020 at 19:36, Lemoene Smit <le...@bi...> wrote:

> Hi All
>
> No *Vanillaforum* yet:(  here's to *Mailman *again
>
> Please comment on the ISO 17025 *2017 *single sample COA in design
> <https://docs.google.com/spreadsheets/d/1rojfv1jcc9wM4PI_DA65V_giIEpscWEqxMnEqxDZDNI/edit?usp=sharing>
> at the moment:
>
> Requirements not addressed yet:
>
> *Sampling schedule and version - *Bika Sampling Round and its Version
>
> *Sampling procedures - *Require Sampling Procedures in the setup, with
> name, description, version, and SOP attachment say
>
> *Analyses Sub Contracted* - Subcontracting yet to be sponsored. Part
> workaround is to add a Sub contracted flag on the ASs that are always
> outsourced. Maybe also  the name of the lab subcontracted if there are more
> than one. These results be iconised as subcontracted on the COA
>
> *Related QC Results - *Though shown on the mock-up, and included earlier,
> not required in this region
>
> Looking forward to nail it, all feedback welcome
> Bests
> lemoene
>
>
>

[bika-users] Manual Worksheets sans Templates

[Lemoene S. <le...@bi...>]

Anyone else needs the *Worksheet Create, Analysis Search functions* back,
please PM or comment at *Manual Worksheets sans Templates*,
https://jira.bikalabs.com/browse/LIMS-3115. Appreciated

[bika-users] No Vanilla... ISO 17025 2017 COA design

[Lemoene S. <le...@bi...>]

Hi All

No *Vanillaforum* yet:(  here's to *Mailman *again

Please comment on the ISO 17025 *2017 *single sample COA in design
<https://docs.google.com/spreadsheets/d/1rojfv1jcc9wM4PI_DA65V_giIEpscWEqxMnEqxDZDNI/edit?usp=sharing>
at the moment:

Requirements not addressed yet:

*Sampling schedule and version - *Bika Sampling Round and its Version

*Sampling procedures - *Require Sampling Procedures in the setup, with
name, description, version, and SOP attachment say

*Analyses Sub Contracted* - Subcontracting yet to be sponsored. Part
workaround is to add a Sub contracted flag on the ASs that are always
outsourced. Maybe also  the name of the lab subcontracted if there are more
than one. These results be iconised as subcontracted on the COA

*Related QC Results - *Though shown on the mock-up, and included earlier,
not required in this region

Looking forward to nail it, all feedback welcome
Bests
lemoene

[bika-users] Bulk Sample import to Batch. Bika Vet. Patient server

[Lemoene S. <le...@bi...>]

Bests for 2020 all, started busily already

Shaun at Greenhill <http://greenhilllabs.co.za/> is sponsoring the
resurrection of Bulk Sample imports to Batches, It Is a popular topic,
please see whether his Bika Dairy version would work for you and how it
could be taken further. It is a prototype, we are doing a few workarounds.
It only does one Analysis Profile per Sample at the moment, to be expanded
as requirements dictate.

Import bulk Samples to Batch from Vet Sampling reports
<https://jira.bikalabs.com/browse/LIMS-3095>.

Google sheet Example
<https://docs.google.com/spreadsheets/d/117RxZIwpXhJhVBA_uqXxLXr8emiqtF1iIQUE9BseTsw>

We use Bika/Senaite LIMS to start with, and in a next phase when Shaun
start taking diagnostic analyses and more patient information is required,
use Health as a Patient and Doctor/Vet server. In Dairy, Vets are
registered on the system as Verifiers, a regulatory requirement, linked to
their Clients with access to their animal data only.

Health does not have regular Batch processing necessary in Vet labs - does
it do Samples without patients - and only limited Patient attributes are
needed. Where necessary for epidemiology purposes, the rest of Health stays
available.

Such a central Patient and Caregiver server will be well suited in district
roll-outs of Bika/Senaite Health elsewhere too

All feedback welcome
Bests, Lemoene

oh and Santa brought us a Vanilla forum, to be configured
there i said it now, must be done ...

Re: [bika-users] Manufacturing labs Re: Bika demo

[lemoene <lem...@gm...>]

Thanks for the feedback Luciano

> I defined a  Sample Type: Carbamazepina 100 mg x 30 comprimidos. (I 
> thought sample type was use to identify the kind of sample, for 
> example, tablets, ampoules, vials, semisolid, etc.)

Ah. You could potentially define those as */Sample Matrices/*, a higher 
tier sample type classification. It is normally used say with /*Sample 
Types*/ of /Drinking Water, Irrigation Water, Ground Water, Sea Water/ 
etc. sorting in a /*Matrix* Water/.

> Analysis Specification: Carbamazepina 100 mg x 30 comprimidos (I 
> understand this is used for defining the product properties and it´s 
> limits)
Correct
>
> Analysis Profile: Carbamazepina 100 mg x 30 comprimidos. (I 
> understand this for designing a template with all the properties that 
> will be analysed)
Jip

When you get to the Sample registration form, use this profile. Next 
step is to create a *Batch* for a new production lot, then start 
creating Samples in there. Once the Samples are in /Received /state, you 
can start capturing results. Best practice is using Worksheets, and to 
improve TAT and accuracy, export them to your instruments, them 
importing the results and start QC.

Which Instruments do you use and do they do CSV exchanges? They are easy 
to code and might be included already, Bika / Senaite interfaces. 
<https://www.bikalims.org/features_benefits/currently-available-bika-senaite-instrument-interfaces#lims>
> Is there any way in which BIKA can determine that, once I have 
> selected Sample Type Carbamazepina 100 mg x 30 comprimidos, it MUST 
> use Analysis Profile and Specification with the same name for testing 
> the sample?

As it will have no knock-on effect on forms, views or reports, this will 
be a relatively small customisation. Logged as improvement 
requestLIMS-3089 Production LIMS. Default Product Profile and 
Specification. <https://jira.bikalabs.com/browse/LIMS-3089>

The extra IDs will make for those modifications, LIMS-3088 Production 
LIMS. Product identification. <https://jira.bikalabs.com/browse/LIMS-3088>

I think you want the Products configure like this?



Am very much interested in the rest of your workflow - do you need 
alerts on the production lines when products drift out of range, OOR? Do 
you include reference material in your tests for further QC? Please keep 
us posted


Looking forward to hear from you
Bests
Lemoene


> With best regards, Luciano Tombazzi.
>
>
> El dom., 10 nov. 2019 a las 18:12, lemoene (<lem...@gm... 
> <mailto:lem...@gm...>>) escribió:
>
>     Hi L
>
>>     Dear Lemoene, Thank you very much. I have been making some test
>>     on BIKA. Please don'ttake as a critic, I am amazingly surprised
>>     by BIKA.It's hard to believe it's free and open source.
>
>     Always good to hear that!-) All criticism welcome, /'Users do not
>     realise how much well documented bug reports are appreciated by
>     devs who want to perfect their work soonest. OS matures quickly/
>
>     Yours are frequently asked and I hope you don't mind me replying
>     via the user group for everybody's benefit.
>
>>     *Batch*
>>
>>     When trying to add the following batch, the following message
>>     appears:
>>
>>     image.png
>>
>>
>>     But if I do it from the Client module, it works. I fill in
>>     exactly the same information that the one I filled in batch
>>     module and it works fine. I wonder if it´s a bug or if I am doing
>>     something wrong.
>>
>     It works for me, please try again. Client users may now create
>     batches too
>
>>     I was expecting to find a field which indicates the code number
>>     or description of the product.
>>
>     That happens on the Sample create form. Remember that for your
>     lab, Sample Type will be translated to Product
>
>
>
>>     This is defined in the following step (Sampling).
>>
>
>     If you do not need to capture data about sampling, it can be
>     disabled for simplified workflow
>
>>     we identify the product ONLY by the batch number.
>>
>
>     Bika identifies Products by their Titles, eg /Sleepwell 2020/ in
>     above example. Your inhouse use of the Batch term differs from
>     Bika's. In production environments, Bika Batches normally contain
>     all the samples for a specific production /*Lot*/ or */Production
>     Run/*,*//*and contain all its samples and results for the duration
>     of the run, from raw material testing to the final packaged product.
>
>         /Bika uses Sample Batching to group Samples together where
>         this makes logical sense, to manage them to publication in
>         context, sans the system noise generated by other analysts and
>         managers
>
>         In manufacturing labs, Batches are often configured as Work
>         Orders, Production Runs or Lots. For research labs, Batches as
>         configured as Experiments or Projects/
>
>>     [...] identified by both the GTIN (GS1) and the Batch Number.
>>
>
>     Ah. We do not have specific attributes on Sample Types for Product
>     IDs. Bika handles multiple IDs, in this case any of in-house ID,
>     catalogue number, GTIN/UPC/EAN, Part #, etc. Will log an
>     improvement requests shortly.
>
>>     _Sampling_
>>
>>     When sampling I applied the following logic. The Analysis
>>     Specification defines the set of Analysis Services that will be
>>     applied, and it's limits.
>>
>
>     Nope, /*Analysis Specifications*/ provide only the product
>     specification, its valid min max range for each of the tests,
>     */Analyses/*, it contains. When creating the Sample record, he
>     Analyses themselves are templated from*Analysis Services, ASs*,
>     the collection of tests your lab do.
>
>     These can be added manually  1-by-1 on the Sample create form, or
>     by selecting a previously configured /*Analysis Profiles*/ or
>     panel. Analyses are compulsory in this form at the moment, you
>     have to select at least 1
>
>
>     /
>
>     /
>     //
>     /*
>     Analysis Specifications*/ is for valid ranges only, and many can
>     be kept  e.g. in gov Food regulations there are for 100s of
>     Products/Sample Types, and Bika applies only the relevant spec for
>     the Product and Analyses selected for testing
>
>>     Once I have created the sample (I imagine this to be QC employee
>>     in charge of sampling the production lines), I receive it (I
>>     imagine this to be the QC technician in our lab receiving it from
>>     the other guy).
>>
>     Lab clerks are also authorised for /Receiving /Samples.
>
>>     Also, in a pharmaceutical environment, the Analysis Profile
>>     should be linked with the product. Under BIKA behaviour, it's
>>     possible to accidentally choose the incorrect Analysis Profile,
>>     and therefore analysis the product incorrectly, I mean with the
>>     unintended Analysis Profile
>>
>     mmm, most lab users should pick that up. If you regularly sample
>     the same sample points, you could also use Sampling Rounds, a
>     further layer of automation, improved TAT and reduced human error
>
>
>>     In a robust workflow the only input data DURING the day to day
>>     workflow should be which is the product you are willing to
>>     analyse, the remaining data should come from setup data.
>>
>
>     K, that is gap 2. Logging shortly
>
>>     Once I have completed I Save and Send the results (I imagine this
>>     to be QC technician loading the results)
>>
>
>     Best to interface your instruments bi-directionally to completely
>     eliminate human transcription errors. It will also reduce your TAT
>     significantly
>
>>     . I prepublish the results.
>>
>
>     Pre-publishing provisional results is optional.
>
>     You skipped most important step, /Verification: /authorised users,
>     eg QC supervisor, review the captured results submitted by the
>     Analysts (before clients see the results) in context of peer and
>     QC outcomes.
>
>     Results out of the specified ranges are highlighted. The
>     /Verifier/ may then retract results for retesting and verify
>     others. Once a Sample has some verified results, those may be
>     pre-published.
>
>>     And then I finally published it. For this I need to go to Clients
>>     –> DENVER FARMA SA à Samples àin the SamplesàVerified (this can
>>     be the QC supervisor),
>>
>
>     They do the critical /Verification/ step,  where-after Clients
>     already get to see the results online. /Publishing/ itself is done
>     thereafter, but is not as critical and you could assign it to
>     clerks say.
>
>>     I check the sample I press Publish. I understand workflow
>>     finishes here. Is it possible to edit the COA layout?
>>
>
>     It is getting easier but still has a bit of a coding threshold. It
>     is probably best to have a professional do it.
>
>>     CONCLUSION: I think the most compromising limitation to consider
>>     BIKA in a pharmaceutical environment is the apparent inability to
>>     link a product with an analysis specification.
>>
>
>     As explained, Bika actually does that
>
>
>
>     In other labs, you could have more than 1 spec per product, e.g
>     the import specifications per country, and only then the user has
>     to pause and select the correct one. In Bika 3.2 we had a default
>     spec feature but it did not make the cut to new Senaite code base
>
>     Hope this helps
>     Bests
>     Lemoene
>
>
>
>
> -- 
>
> *Luciano Tombazzi ***
>
> Mozart s/n - Garin
>
> Buenos Aires - Argentina
>
> Te: 54 11 5650-9518 int. 109
>
>
>
> _______________________________________________
> Bika-Users mailing list
> Bik...@li...
> https://lists.sourceforge.net/lists/listinfo/bika-users

Re: [bika-users] Manufacturing labs Re: Bika demo

[Luciano T. <luc...@de...>]

Dear Lemoene,

Thank you very much for your comments.

I have defined

Sample Type: Carbamazepina 100 mg x 30 comprimidos
(I thought sample type was use to identify the kind of sample, for example,
tables, ampoules, vials, semisolid, etc.)

Analysis Specification: Carbamazepina 100 mg x 30 comprimidos
(I understand this is used for defining the product properties and it´s
limits)

Analysis Profile: Carbamazepina 100 mg x 30 comprimidos
(I understand this for designing a template with all the properties that
will be analysed)

Is there any way in which BIKA can determine that, once I have selected
Sample Type Carbamazepina 100 mg x 30 comprimidos, it MUST use Analysis
Profile and Specification with the same name for testing the sample?

With best regards, Luciano Tombazzi.



El dom., 10 nov. 2019 a las 18:12, lemoene (<lem...@gm...>)
escribió:

> Hi L
>
> Dear Lemoene, Thank you very much. I have been making some test on BIKA. Please
> don't take as a critic, I am amazingly surprised by BIKA.It's hard to
> believe it's free and open source.
>
>
> Always good to hear that!-) All criticism welcome, *'Users do not realise
> how much well documented bug reports are appreciated by devs who want to
> perfect their work soonest. OS matures quickly*
>
> Yours are frequently asked and I hope you don't mind me replying via the
> user group for everybody's benefit.
>
> *Batch*
>
> When trying to add the following batch, the following message appears:
>
> [image: image.png]
>
>
> But if I do it from the Client module, it works. I fill in exactly the
> same information that the one I filled in batch module and it works fine. I
> wonder if it´s a bug or if I am doing something wrong.
>
> It works for me, please try again. Client users may now create batches too
>
> I was expecting to find a field which indicates the code number or
> description of the product.
>
> That happens on the Sample create form. Remember that for your lab, Sample
> Type will be  translated to Product
>
>
>
> This is defined in the following step (Sampling).
>
>
> If you do not need to capture data about sampling, it can be disabled for
> simplified workflow
>
> we identify the product ONLY by the batch number.
>
>
> Bika identifies Products by their Titles, eg *Sleepwell 2020* in above
> example. Your inhouse use of the Batch term differs from Bika's.  In
> production environments, Bika Batches normally contain all the samples for
> a specific production *Lot* or *Production Run*, and contain all its
> samples and results for the duration of the run, from raw material testing
> to the final packaged product.
>
>
>
> *Bika uses Sample Batching to group Samples together where this makes
> logical sense, to manage them to publication in context, sans the system
> noise generated by other analysts and managers In manufacturing labs,
> Batches are often configured as Work Orders, Production Runs or Lots. For
> research labs, Batches as configured as Experiments or Projects*
>
> [...] identified by both the GTIN (GS1) and the Batch Number.
>
>
> Ah. We do not have specific attributes on Sample Types for Product IDs.
> Bika handles multiple IDs, in this case any of in-house ID, catalogue
> number, GTIN/UPC/EAN, Part #, etc. Will log an improvement requests shortly.
>
> *Sampling*
>
> When sampling I applied the following logic. The Analysis Specification
> defines the set of Analysis Services that will be applied, and it's limits.
>
>
> Nope, *Analysis Specifications* provide only the product specification,
> its valid min max range for each of the tests, *Analyses*, it contains.
> When creating the Sample record, he Analyses themselves are templated from*
> Analysis Services, ASs*, the collection of tests your lab do.
>
> These can be added manually  1-by-1 on the Sample create form, or by
> selecting a previously configured *Analysis Profiles* or panel. Analyses
> are compulsory in this form at the moment, you have to select at least 1
>
>
>
>
>
>
>
> * Analysis Specifications* is for valid ranges only, and many can be
> kept  e.g. in gov Food regulations there are for 100s of Products/Sample
> Types, and Bika applies only the relevant spec for the Product and Analyses
> selected for testing
>
> Once I have created the sample (I imagine this to be QC employee in charge
> of sampling the production lines), I receive it (I imagine this to be the
> QC technician in our lab receiving it from the other guy).
>
> Lab clerks are also authorised for *Receiving  *Samples.
>
> Also, in a pharmaceutical environment, the Analysis Profile should be
> linked with the product. Under BIKA behaviour, it's possible to
> accidentally choose the incorrect Analysis Profile, and therefore analysis
> the product incorrectly, I mean with the unintended Analysis Profile
>
> mmm, most lab users should pick that up. If you regularly sample the same
> sample points, you could also use Sampling Rounds, a further layer of
> automation, improved TAT and reduced human error
>
>
> In a robust workflow the only input data DURING the day to day workflow
> should be which is the product you are willing to analyse, the remaining
> data should come from setup data.
>
>
> K, that is gap 2. Logging shortly
>
> Once I have completed I Save and Send the results (I imagine this to be QC
> technician loading the results)
>
>
> Best to interface your instruments bi-directionally to completely
> eliminate human transcription errors. It will also reduce your TAT
> significantly
>
> . I prepublish the results.
>
>
> Pre-publishing provisional results is optional.
>
> You skipped most important step, *Verification: *authorised users, eg QC
> supervisor, review the captured results submitted by the Analysts (before
> clients see the results) in context of peer and QC outcomes.
>
> Results out of the specified ranges are highlighted. The *Verifier* may
> then retract results for retesting and verify others. Once a Sample has
> some verified results, those may be pre-published.
>
> And then I finally published it. For this I need to go to Clients –>
> DENVER FARMA SA à Samples àin the SamplesàVerified (this can be the QC
> supervisor),
>
>
> They do the critical *Verification*  step,  where-after Clients already
> get to see the results online. *Publishing* itself is done thereafter,
> but is not as critical and you could assign it to clerks say.
>
> I check the sample I press Publish. I understand workflow finishes here.
> Is it possible to edit the COA layout?
>
>
> It is getting easier but still has a bit of a coding threshold. It is
> probably best to have a professional do it.
>
> CONCLUSION: I think the most compromising limitation to consider BIKA in a
> pharmaceutical environment is the apparent inability to link a product with
> an analysis specification.
>
>
> As explained, Bika actually does that
>
>
>
> In other labs, you could have more than 1 spec per product, e.g the import
> specifications per country, and only then the user has to pause and select
> the correct one. In Bika 3.2 we had a default spec feature but it did not
> make the cut to new Senaite code base
>
> Hope this helps
> Bests
> Lemoene
>
>
>

-- 

*Luciano Tombazzi *



Mozart s/n - Garin

Buenos Aires - Argentina

Te: 54 11 5650-9518 int. 109

[bika-users] Manufacturing labs Re: Bika demo

[lemoene <lem...@gm...>]

Hi L

> Dear Lemoene, Thank you very much. I have been making some test on 
> BIKA. Please don'ttake as a critic, I am amazingly surprised by 
> BIKA.It's hard to believe it's free and open source.

Always good to hear that!-) All criticism welcome, /'Users do not 
realise how much well documented bug reports are appreciated by devs who 
want to perfect their work soonest. OS matures quickly/

Yours are frequently asked and I hope you don't mind me replying via the 
user group for everybody's benefit.

> *Batch*
>
> When trying to add the following batch, the following message appears:
>
> image.png
>
>
> But if I do it from the Client module, it works. I fill in exactly the 
> same information that the one I filled in batch module and it works 
> fine. I wonder if it´s a bug or if I am doing something wrong.
>
It works for me, please try again. Client users may now create batches too

> I was expecting to find a field which indicates the code number or 
> description of the product.
>
That happens on the Sample create form. Remember that for your lab, 
Sample Type will be  translated to Product



> This is defined in the following step (Sampling).
>

If you do not need to capture data about sampling, it can be disabled 
for simplified workflow

> we identify the product ONLY by the batch number.
>

Bika identifies Products by their Titles, eg /Sleepwell 2020/ in above 
example. Your inhouse use of the Batch term differs from Bika's.  In 
production environments, Bika Batches normally contain all the samples 
for a specific production /*Lot*/ or */Production Run/*,*//*and contain 
all its samples and results for the duration of the run, from raw 
material testing to the final packaged product.

    /Bika uses Sample Batching to group Samples together where this
    makes logical sense, to manage them to publication in context, sans
    the system noise generated by other analysts and managers

    In manufacturing labs, Batches are often configured as Work Orders,
    Production Runs or Lots. For research labs, Batches as configured as
    Experiments or Projects/

> [...] identified by both the GTIN (GS1) and the Batch Number.
>

Ah. We do not have specific attributes on Sample Types for Product IDs. 
Bika handles multiple IDs, in this case any of in-house ID, catalogue 
number, GTIN/UPC/EAN, Part #, etc. Will log an improvement requests shortly.

> _Sampling_
>
> When sampling I applied the following logic. The Analysis 
> Specification defines the set of Analysis Services that will be 
> applied, and it's limits.
>

Nope, /*Analysis Specifications*/ provide only the product 
specification, its valid min max range for each of the tests, 
*/Analyses/*, it contains. When creating the Sample record, he Analyses 
themselves are templated from*Analysis Services, ASs*, the collection of 
tests your lab do.

These can be added manually  1-by-1 on the Sample create form, or by 
selecting a previously configured /*Analysis Profiles*/ or panel. 
Analyses are compulsory in this form at the moment, you have to select 
at least 1


/

/
//
/*
Analysis Specifications*/ is for valid ranges only, and many can be 
kept  e.g. in gov Food regulations there are for 100s of Products/Sample 
Types, and Bika applies only the relevant spec for the Product and 
Analyses selected for testing

> Once I have created the sample (I imagine this to be QC employee in 
> charge of sampling the production lines), I receive it (I imagine this 
> to be the QC technician in our lab receiving it from the other guy).
>
Lab clerks are also authorised for /Receiving /Samples.

> Also, in a pharmaceutical environment, the Analysis Profile should be 
> linked with the product. Under BIKA behaviour, it's possible to 
> accidentally choose the incorrect Analysis Profile, and therefore 
> analysis the product incorrectly, I mean with the unintended Analysis 
> Profile
>
mmm, most lab users should pick that up. If you regularly sample the 
same sample points, you could also use Sampling Rounds, a further layer 
of automation, improved TAT and reduced human error


> In a robust workflow the only input data DURING the day to day 
> workflow should be which is the product you are willing to analyse, 
> the remaining data should come from setup data.
>

K, that is gap 2. Logging shortly

> Once I have completed I Save and Send the results (I imagine this to 
> be QC technician loading the results)
>

Best to interface your instruments bi-directionally to completely 
eliminate human transcription errors. It will also reduce your TAT 
significantly

> . I prepublish the results.
>

Pre-publishing provisional results is optional.

You skipped most important step, /Verification: /authorised users, eg QC 
supervisor, review the captured results submitted by the Analysts 
(before clients see the results) in context of peer and QC outcomes.

Results out of the specified ranges are highlighted. The /Verifier/ may 
then retract results for retesting and verify others. Once a Sample has 
some verified results, those may be pre-published.

> And then I finally published it. For this I need to go to Clients –> 
> DENVER FARMA SA à Samples àin the SamplesàVerified (this can be the QC 
> supervisor),
>

They do the critical /Verification/ step,  where-after Clients already 
get to see the results online. /Publishing/ itself is done thereafter, 
but is not as critical and you could assign it to clerks say.

> I check the sample I press Publish. I understand workflow finishes 
> here. Is it possible to edit the COA layout?
>

It is getting easier but still has a bit of a coding threshold. It is 
probably best to have a professional do it.

> CONCLUSION: I think the most compromising limitation to consider BIKA 
> in a pharmaceutical environment is the apparent inability to link a 
> product with an analysis specification.
>

As explained, Bika actually does that



In other labs, you could have more than 1 spec per product, e.g the 
import specifications per country, and only then the user has to pause 
and select the correct one. In Bika 3.2 we had a default spec feature 
but it did not make the cut to new Senaite code base

Hope this helps
Bests
Lemoene

Re: [bika-users] Worksheet view error

[lemoene <lem...@gm...>]

Hi Didinson

> Hi all; I'm using a Bika Lims 3.2 and Ubuntu 18.04 OS and I have a 
> problem for visualization a worksheet after send to tramit this. I 
> transcrip traceback.

Ja you should really be on the latest Senaite1.3.* release. I doubt 
anybody can help you with this one still.

Bests
Lemoene


>
> ______________
> Traceback (innermost last):
>
>     Module ZPublisher.Publish, line 138, in publish
>     Module ZPublisher.mapply, line 77, in mapply
>     Module ZPublisher.Publish, line 48, in call_object
>     Module bika.lims.browser.worksheet.views.results, line 125, in 
> __call__
>     Module Products.Five.browser.pagetemplatefile, line 125, in __call__
>     Module Products.Five.browser.pagetemplatefile, line 59, in __call__
>     Module zope.pagetemplate.pagetemplate, line 132, in pt_render
>     Module five.pt.engine, line 98, in __call__
>     Module z3c.pt.pagetemplate, line 173, in render
>     Module chameleon.zpt.template, line 306, in render
>     Module chameleon.template, line 209, in render
>     Module chameleon.template, line 187, in render
>     Module c4d887212a2eaa2537e64491332a56ac.py, line 1498, in render
>     Module f8e632b34211f0fec72d344bc733ce7b.py, line 1249, in 
> render_master
>     Module f8e632b34211f0fec72d344bc733ce7b.py, line 521, in 
> render_content
>     Module c4d887212a2eaa2537e64491332a56ac.py, line 1397, in 
> __fill_content_core
>     Module five.pt.expressions, line 161, in __call__
>     Module bika.lims.browser.bika_listing, line 1096, in contents_table
>     Module bika.lims.browser.bika_listing, line 1275, in __init__
>     Module bika.lims.browser.worksheet.views.analyses, line 95, in 
> folderitems
>
> ValueError: invalid literal for int() with base 10: 'new' - 
> Expression: "provider:plone.abovecontentbody" - Filename: ... 
> theme/sunburst/skins/sunburst_templates/main_template.pt 
> <http://main_template.pt> - Location: (line 117: col 89) - Source: ... 
> ent="structure provider:plone.abovecontentbody" tal:conditio ... 
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Expression: 
> "here/main_template/macros/master" - Filename: ... 
> ika/lims/browser/worksheet/views/../templates/results.pt 
> <http://results.pt> - Location: (line 5: col 21) - Source: 
> metal:use-macro="here/main_template/macros/master" 
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Arguments: repeat: {...} (0) 
> template: <ViewPageTemplateFile - at 0x7f9f2192f610> views: 
> <ViewMapper - at 0x7f9f2e083310> modules: <instance - at 
> 0x7f9f6fcbf5f0> args: <tuple - at 0x7f9f78993050> here: 
> <ImplicitAcquisitionWrapper WS19-2329 at 0x7f9f1ff87230> 
> wrapped_repeat: <SafeMapping - at 0x7f9f46c04ba8> user: 
> <ImplicitAcquisitionWrapper - at 0x7f9f242dbf50> nothing: <NoneType - 
> at 0x55c5d6a71560> target_language: <NoneType - at 0x55c5d6a71560> 
> translate: <function translate at 0x7f9f4a4195f0> container: 
> <ImplicitAcquisitionWrapper WS19-2329 at 0x7f9f1ff87230> root: 
> <ImplicitAcquisitionWrapper Zope at 0x7f9f3b10d460> request: <instance 
> - at 0x7f9f2915d200> traverse_subpath: <list - at 0x7f9f23225b90> 
> default: <object - at 0x7f9f788b3580> context: 
> <ImplicitAcquisitionWrapper WS19-2329 at 0x7f9f1ff87230> view: 
> <ManageResultsView manage_results at 0x7f9f2a4bf0d0> macroname: master 
> options: {...} (0) loop: {...} (3) last_uid: 
> fac08a92ebfe4b3cb8d92b66cef367be
>
> _________
>
> What can I do?
>
> Best Regards...!
>
>
> _______________________________________________
> Bika-Users mailing list
> Bik...@li...
> https://lists.sourceforge.net/lists/listinfo/bika-users

[bika-users] Worksheet view error

[Didinson M. <dmu...@gm...>]

Hi all;

I'm using a Bika Lims 3.2 and Ubuntu 18.04 OS and I have a problem for
visualization a worksheet after send to tramit this. I transcrip traceback.

______________
Traceback (innermost last):

    Module ZPublisher.Publish, line 138, in publish
    Module ZPublisher.mapply, line 77, in mapply
    Module ZPublisher.Publish, line 48, in call_object
    Module bika.lims.browser.worksheet.views.results, line 125, in __call__
    Module Products.Five.browser.pagetemplatefile, line 125, in __call__
    Module Products.Five.browser.pagetemplatefile, line 59, in __call__
    Module zope.pagetemplate.pagetemplate, line 132, in pt_render
    Module five.pt.engine, line 98, in __call__
    Module z3c.pt.pagetemplate, line 173, in render
    Module chameleon.zpt.template, line 306, in render
    Module chameleon.template, line 209, in render
    Module chameleon.template, line 187, in render
    Module c4d887212a2eaa2537e64491332a56ac.py, line 1498, in render
    Module f8e632b34211f0fec72d344bc733ce7b.py, line 1249, in render_master
    Module f8e632b34211f0fec72d344bc733ce7b.py, line 521, in render_content
    Module c4d887212a2eaa2537e64491332a56ac.py, line 1397, in
__fill_content_core
    Module five.pt.expressions, line 161, in __call__
    Module bika.lims.browser.bika_listing, line 1096, in contents_table
    Module bika.lims.browser.bika_listing, line 1275, in __init__
    Module bika.lims.browser.worksheet.views.analyses, line 95, in
folderitems

ValueError: invalid literal for int() with base 10: 'new' - Expression:
"provider:plone.abovecontentbody" - Filename: ...
theme/sunburst/skins/sunburst_templates/main_template.pt - Location: (line
117: col 89) - Source: ... ent="structure provider:plone.abovecontentbody"
tal:conditio ... ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Expression:
"here/main_template/macros/master" - Filename: ...
ika/lims/browser/worksheet/views/../templates/results.pt - Location: (line
5: col 21) - Source: metal:use-macro="here/main_template/macros/master"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - Arguments: repeat: {...} (0) template:
<ViewPageTemplateFile - at 0x7f9f2192f610> views: <ViewMapper - at
0x7f9f2e083310> modules: <instance - at 0x7f9f6fcbf5f0> args: <tuple - at
0x7f9f78993050> here: <ImplicitAcquisitionWrapper WS19-2329 at
0x7f9f1ff87230> wrapped_repeat: <SafeMapping - at 0x7f9f46c04ba8> user:
<ImplicitAcquisitionWrapper - at 0x7f9f242dbf50> nothing: <NoneType - at
0x55c5d6a71560> target_language: <NoneType - at 0x55c5d6a71560> translate:
<function translate at 0x7f9f4a4195f0> container:
<ImplicitAcquisitionWrapper WS19-2329 at 0x7f9f1ff87230> root:
<ImplicitAcquisitionWrapper Zope at 0x7f9f3b10d460> request: <instance - at
0x7f9f2915d200> traverse_subpath: <list - at 0x7f9f23225b90> default:
<object - at 0x7f9f788b3580> context: <ImplicitAcquisitionWrapper WS19-2329
at 0x7f9f1ff87230> view: <ManageResultsView manage_results at
0x7f9f2a4bf0d0> macroname: master options: {...} (0) loop: {...} (3)
last_uid: fac08a92ebfe4b3cb8d92b66cef367be

_________

What can I do?

Best Regards...!

[bika-users] Billing. Invoice export. Include your format now

[lemoene <lem...@gm...>]

Hi All

We are inching closer to have Bika Statement export sponsored, to Solis, 
Xero and Bika angels Quantum Analytics <https://lims.quantumlab.co.za/>' 
Pastel format, improvement request Billing. Statement export to Xero, 
Solis, Pastel. <https://jira.bikalabs.com/browse/LIMS-3072>

Not a very big one (max $2k?) and it is easy to see that the more 
formats we get sponsored and we do all at once, much savings can be had 
by all. We'll need an annotated example or format specification. Let us 
know.

Bests
l

[bika-users] Portlets Re: Dashboard manipulation

[lemoene <lem...@gm...>]

Thanks Leigh-Anne
> I would like each user to see relevant information according to their 
> role.
>
> E.g. Analysts would see different portlets showing:
>
>   * Samples awaiting analysis assigned to them
>   * Samples awaiting results verification (for verifiers)
>
> etc.
>
> Managers would see portlets for each step of the testing workflow. 
> Kind of like a quick access area for pending work. Especially any 
> alarms :)

I updated improvement request, https://jira.bikalabs.com/browse/LIMS-3083

> I see the below when I try to edit the dashboard but I have no idea 
> how to deal with portlets.
>
> image.png

The Bika alerts are not listed anymore but are all coded. The Plone 
portlets can be used with general content where labs use it for document 
management, promotions, news and events, etc. Plone 4 manual, Portlet 
Management 
<https://docs.plone.org/4/en/working-with-content/portlet-management/index.html>.

Bests, Lemoene


> Regards
>
> *LEIGH-ANNE *
>
>
> On Wed, 2 Oct 2019 at 12:55, lemoene <lem...@gm... 
> <mailto:lem...@gm...>> wrote:
>
>     Thanks for posting Leigh-Anne
>
>>     Hello all,  I would like to set up the dashboard in BIKALims for
>>     different users in such a way that different user profiles (I.e.
>>     manager or technician) are shown different things relevant only
>>     to them. How can I go about this? I see referral to porlets in
>>     the Senaite manual but it's not clear exactly how to do this?
>>     P.S. I have no programming background. Laymans please
>
>     OK.
>
>       * What do you want to show to the different users?
>
>     With eventual sponsorship, we want to bring back the Bika
>     portlets, dropped in the Senaite core in favour of the dash board
>     where you can already set view privileges:
>
>
>     The portlets of earlier fulfilled the additional function of
>     alerting users of specific events they have to tend to. They can
>     be performance debilitating when run live, calculating every time
>     a page carrying them are opened, and updating while open
>
>     In an improvement request awaiting sponsorship <grin> we suggest
>     they only be updated once every 5 (or configurable number of)
>     minutes, with the option of a refresh button. I often see a rather
>     nice expansion of this in production labs where a product drifting
>     out of spec can immediately be alerted to a (noisy) production
>     line on a prominently mounted tablet running the alert full screen
>     (pulsing amber and with loud hailing speakers attached...)
>     Automation rulz rock ok
>
>     Bests
>     l
>
>
>     Uploaded image for project: 'LIMS'
>
>      1. LIMS-3083 Add-on. Alert portlets
>         <https://jira.bikalabs.com/browse/LIMS-3083>
>
>
>
>
>
>
>
>
>     _______________________________________________
>     Bika-Users mailing list
>     Bik...@li...
>     <mailto:Bik...@li...>
>     https://lists.sourceforge.net/lists/listinfo/bika-users
>
>
>
> _______________________________________________
> Bika-Users mailing list
> Bik...@li...
> https://lists.sourceforge.net/lists/listinfo/bika-users

Re: [bika-users] Dashboard manipulation

[Leigh-Anne M. <lei...@qu...>]

Dear Lemoene,

I would like each user to see relevant information according to their role.

E.g. Analysts would see different portlets showing:

   - Samples awaiting analysis assigned to them
   - Samples awaiting results verification (for verifiers)

etc.

Managers would see portlets for each step of the testing workflow. Kind of
like a quick access area for pending work. Especially any alarms :)

I see the below when I try to edit the dashboard but I have no idea how to
deal with portlets.

[image: image.png]

Regards



*LEIGH-ANNE *

On Wed, 2 Oct 2019 at 12:55, lemoene <lem...@gm...> wrote:

> Thanks for posting Leigh-Anne
>
> Hello all,  I would like to set up the dashboard in BIKALims for different
> users in such a way that different user profiles (I.e. manager or
> technician) are shown different things relevant only to them. How can I go
> about this? I see referral to porlets in the Senaite manual but it's not
> clear exactly how to do this? P.S. I have no programming background.
> Laymans please
>
>
> OK.
>
>    - What do you want to show to the different users?
>
> With eventual sponsorship, we want to bring back the Bika portlets,
> dropped in the Senaite core in favour of the dash board where you can
> already set view privileges:
>
>
> The portlets of earlier fulfilled the additional function of alerting
> users of specific events they have to tend to. They can be performance
> debilitating when run live, calculating every time a page carrying them are
> opened, and updating while open
>
> In an improvement request awaiting sponsorship <grin> we suggest they only
> be updated once every 5 (or configurable number of) minutes, with the
> option of a refresh button. I often see a rather nice expansion of this in
> production labs where a product drifting out of spec can immediately be
> alerted to a (noisy) production line on a prominently mounted tablet
> running the alert full screen (pulsing amber and with loud hailing speakers
> attached...) Automation rulz rock ok
>
> Bests
> l
>
>
> [image: Uploaded image for project: 'LIMS']
>
>    1. LIMS-3083 Add-on. Alert portlets
>    <https://jira.bikalabs.com/browse/LIMS-3083>
>
>
>
>
>
>
>
> _______________________________________________
> Bika-Users mailing list
> Bik...@li...
> https://lists.sourceforge.net/lists/listinfo/bika-users
>

Re: [bika-users] Dashboard manipulation

[lemoene <lem...@gm...>]

Thanks for posting Leigh-Anne

> Hello all,  I would like to set up the dashboard in BIKALims for 
> different users in such a way that different user profiles (I.e. 
> manager or technician) are shown different things relevant only to 
> them. How can I go about this? I see referral to porlets in the 
> Senaite manual but it's not clear exactly how to do this? P.S. I have 
> no programming background. Laymans please

OK.

  * What do you want to show to the different users?

With eventual sponsorship, we want to bring back the Bika portlets, 
dropped in the Senaite core in favour of the dash board where you can 
already set view privileges:


The portlets of earlier fulfilled the additional function of alerting 
users of specific events they have to tend to. They can be performance 
debilitating when run live, calculating every time a page carrying them 
are opened, and updating while open

In an improvement request awaiting sponsorship <grin> we suggest they 
only be updated once every 5 (or configurable number of) minutes, with 
the option of a refresh button. I often see a rather nice expansion of 
this in production labs where a product drifting out of spec can 
immediately be alerted to a (noisy) production line on a prominently 
mounted tablet running the alert full screen (pulsing amber and with 
loud hailing speakers attached...) Automation rulz rock ok

Bests
l


Uploaded image for project: 'LIMS'

 1. LIMS-3083 Add-on. Alert portlets
    <https://jira.bikalabs.com/browse/LIMS-3083>

[bika-users] Dashboard manipulation

[Leigh-Anne M. <lei...@qu...>]

Hello all,

I would like to set up the dashboard in BIKALims for different users in
such a way that different user profiles (I.e. manager or technician) are
shown different things relevant only to them.

How can I go about this? I see referral to porlets in the Senaite manual
but it's not clear exactly how to do this?

P.S. I have no programming background. Laymans please

Regards


*LEIGH-ANNE *

[bika-users] More Instrument reports Re:

[lemoene <lem...@gm...>]

Hi A

> Hope this finds you well. I have been pottering around a bit in 
> BikaLims, but I am interested in running some reports about my 
> instruments (e.g. how many of them need bi-annual calibration as 
> opposed to annual). How can I do this, is there a way for me to create 
> my own reports?
>

Hope you  not mind me replying via the user-list where we had a related 
question just last week

    > Hi all,  How do I export info (eg instruments) into a csv?

    Not facility for that at the moment - not an often requested operation. Is it for accreditation documentation?

    Bika Senaite lists and tables easily copy to spreadsheet (Chrome to OpenOffice, Google sheets) for smaller data sets.

    Bigger sets can be summarised in Bika's Management Reports and then saved as CSV.


That said, we Bika does not have a display column for Instrument 
calibration cycle, just expiry date (unfeasibly futuristic in the screen 
shot:)




It is getting easier to create your own report lay-outs but doing so has 
a templating threshold to scale - don't believe LIMS vendors selling you 
WYSIWIG report generators... Another option could be is to make more 
columns available on lists and provide a CSV export button. Pivot tables 
are alive and kicking I understand.

/Pick any two of good, cheap and fast: /A professional coder will code 
your reports, depending on complexity, quickly and affordably. Or, rope 
some  computer science students in to write your reports as part of 
their task work. Reports are relatively easy and a good entry point.

Let us know how it goes. Subscribe at 
https://sourceforge.net/projects/bika/lists/bika-users to receive 
follow-ups.

Bests
l

Re: [bika-users] Exporting from LIMS

[lemoene <lem...@gm...>]

Hi Shaun
>
> Hi all,  How do I export info (eg instruments) into a csv?
>

Not facility for that at the moment - not an often requested operation. 
Is it for accreditation documentation? Bika Senaite lists and tables 
easily copy to spreadsheet (Chrome to OpenOffice, Google sheets) for 
smaller data sets

 From the demo

    Instrument 	Type 	Brand 	Model 	Expiry Date 	Methods
    Agilent GC MS
    <https://demo.bikalabs.com/lims1/bika_setup/bika_instruments/instrument-32>
    	
    GC system
    <https://demo.bikalabs.com/lims1/bika_setup/bika_instrumenttypes/instrumenttype-15>
    	
    Agilent Technologies
    <https://demo.bikalabs.com/lims1/bika_setup/bika_manufacturers/manufacturer-4>
    	

    	
    2022-07-01
    	

    Agilent Triple Quad (QQQ)
    <https://demo.bikalabs.com/lims1/bika_setup/bika_instruments/instrument-31>
    	
    GC system
    <https://demo.bikalabs.com/lims1/bika_setup/bika_instrumenttypes/instrumenttype-15>
    	
    Agilent Technologies
    <https://demo.bikalabs.com/lims1/bika_setup/bika_manufacturers/manufacturer-4>
    	
    Sartorius A200S
    	
    2022-09-01
    	
    GCMS <https://demo.bikalabs.com/lims1/methods/method-8>,Test
    <https://demo.bikalabs.com/lims1/methods/method-25>
    Auto Colony Counter
    <https://demo.bikalabs.com/lims1/bika_setup/bika_instruments/instrument-30>
    	
    Colony Counter
    <https://demo.bikalabs.com/lims1/bika_setup/bika_instrumenttypes/instrumenttype-7>
    	
    Accumax
    <https://demo.bikalabs.com/lims1/bika_setup/bika_manufacturers/manufacturer-2>
    	

    	
    2022-09-01
    	
    Auto Colony Counting
    <https://demo.bikalabs.com/lims1/methods/method-31>,Aerobic Plate
    Count <https://demo.bikalabs.com/lims1/methods/method-23>
    AZ 86505 Conductivity Meter
    <https://demo.bikalabs.com/lims1/bika_setup/bika_instruments/instrument-29>
    	
    Conductivity Meter
    <https://demo.bikalabs.com/lims1/bika_setup/bika_instrumenttypes/instrumenttype-9>
    	
    AZ
    <https://demo.bikalabs.com/lims1/bika_setup/bika_manufacturers/manufacturer-7>
    	
    V-10 Plus
    	
    2022-09-01
    	

    Biomerieux Vidas 12
    <https://demo.bikalabs.com/lims1/bika_setup/bika_instruments/instrument-28>
    	
    Pathogen Analyser
    <https://demo.bikalabs.com/lims1/bika_setup/bika_instrumenttypes/instrumenttype-28>
    	
    Biomerieux
    <https://demo.bikalabs.com/lims1/bika_setup/bika_manufacturers/manufacturer-11>
    	

    	
    2022-09-01

Some bigger sets can be pulled out with Reports and then saved as CSV. 
Bika use to have a query function that is not all that straight forward 
to implement with nonSQL Python. If all goes well we might have Report 
later that exports full Analysis results sets - most current are 
management summaries - to be used in spreadsheet pivot tables an the likes.

Keep'm coming!
Bests
l



> Shaun
>
>
>
> _______________________________________________
> Bika-Users mailing list
> Bik...@li...
> https://lists.sourceforge.net/lists/listinfo/bika-users

[bika-users] Exporting from LIMS

[Shaun G. <sh...@gr...>]

Hi all 

 

How do I export info (eg instruments) into a csv?

 

Shaun

 

[bika-users] Deciphering Jira emails Re: To the tracker; -) Re: Sample Point GPS

[lemoene <lem...@gm...>]

> Thanks for posting Shaun

You should've received a few mails from the tracker now, pretty geeky. 
Issue /Reporters, Assignees /and everybody on its /Watch list/ are 
notified by mail of important updates. One day in a next life, i'll find 
this template and make it more humanly accessible. Best is to only note 
who did what, then click on the issue itself, scroll to las comment and 
add your remarks.

This one made me laugh









All screen shots here BTW done with Zephyr Capture plug-in

Nog veel geluk ermee!
Good week
L

>
>> Hi all,  Is there a way to change the entry of the latitude and 
>> longitude to decimals instead of degrees?
>>
>
> Now that could be a really small customisation - some of these are 
> going to backfire with egg... A Python function and displaying both 
> formats could do. Maybe a selection toggle in the set-up if we want to 
> be fancy.
>
> Not mind, opportunity for the pedantic, these best be logged as 
> */Improvement Request/*
>
>     /Through logging feature requests, users indicate to analysts and
>     developers how the system can be enhanced. Aggregating these,
>     delivers FOSS' best-of-breed designs. //
>     ////
>     //Where users have similar requirements, they can be combined to
>     lower the cost of development./
>
> Re your other post, Samples not being created, that'll be a /*Bug 
> Report*/. There are als Support, Task and Feature Request issue types.
> /**/
>
>     /Well documented bug reports
>     <https://www.bikalims.org/support-and-service-provision/how-to-get-system-issues-attended-to-fast> are
>     hugely appreciated and contribute much to the rapid maturation of
>     Open Source software and reduced central Testing.
>     //
>     ///Assistance with items logged is administered by volunteers or
>     your contracted professional service provider. Add as much
>     information possible to make it easy for them to understand you
>     and reduce turnaround./
>
>     There are very good drills on how to be most effective, especially
>     with bugs, see Best practice for Best outcomes
>     <https://www.bikalims.org/support-and-service-provision/how-to-get-system-issues-attended-to-fast#bestpractice>.
>
>
>     Log your finds here
>     <http://jira.bikalabs.com/secure/RapidBoard.jspa?rapidView=15&projectKey=LIMS&view=planning.nodetail&selectedIssue=LIMS-2986&quickFilter=45>...
>     Bika uses phenomenal ///project tool/ Jira icon 32Jira as tracker
>     . Do install the Zephyr  Capture browser plug-in for through the
>     web screenshots, annotation and logging. Zephyr Capture makes bug
>     reporting fun.
>     <https://www.bikalims.org/support-and-service-provision/how-to-get-system-issues-attended-to-fast#jiracapture>
>     /
>
> See you in Jira, be sure to register with email address - that way you 
> are kept informed of updates, questions and eventual resolution.
>
> Good weekend!
> l

[bika-users] To the tracker;-) Re: Sample Point GPS

[lemoene <lem...@gm...>]

Thanks for posting Shaun

> Hi all,  Is there a way to change the entry of the latitude and 
> longitude to decimals instead of degrees?
>

Now that could be a really small customisation - some of these are going 
to backfire with egg... A Python function and displaying both formats 
could do. Maybe a selection toggle in the set-up if we want to be fancy.

Not mind, opportunity for the pedantic, these best be logged as 
*/Improvement Request/*

    /Through logging feature requests, users indicate to analysts and
    developers how the system can be enhanced. Aggregating these,
    delivers FOSS' best-of-breed designs. //
    ////
    //Where users have similar requirements, they can be combined to
    lower the cost of development./

Re your other post, Samples not being created, that'll be a /*Bug 
Report*/. There are als Support, Task and Feature Request issue types.
**/**/

    /Well documented bug reports
    <https://www.bikalims.org/support-and-service-provision/how-to-get-system-issues-attended-to-fast> are
    hugely appreciated and contribute much to the rapid maturation of
    Open Source software and reduced central Testing.
    //
    ///Assistance with items logged is administered by volunteers or
    your contracted professional service provider. Add as much
    information possible to make it easy for them to understand you and
    reduce turnaround./

    There are very good drills on how to be most effective, especially
    with bugs, see Best practice for Best outcomes
    <https://www.bikalims.org/support-and-service-provision/how-to-get-system-issues-attended-to-fast#bestpractice>.


    Log your finds here
    <http://jira.bikalabs.com/secure/RapidBoard.jspa?rapidView=15&projectKey=LIMS&view=planning.nodetail&selectedIssue=LIMS-2986&quickFilter=45>...
    Bika uses phenomenal ///project tool/ Jira icon 32Jira as tracker .
    Do install the Zephyr  Capture browser plug-in for through the web
    screenshots, annotation and logging. Zephyr Capture makes bug
    reporting fun.
    <https://www.bikalims.org/support-and-service-provision/how-to-get-system-issues-attended-to-fast#jiracapture>
    /

See you in Jira, be sure to register with email address - that way you 
are kept informed of updates, questions and eventual resolution.

Good weekend!
l

Re: [bika-users] Unique COA ID, Title Re : BIKA LIMS Upgrade

[lemoene <lem...@gm...>]

Hi Afrin

> Hello Lemoene, Thank you for re-opening this improvement request. We 
> will be waiting for this feature.

I was hoping you'd respond with Yes I have Python capacity and/or 
budget;-) It could  be a while before anybody gets to it. If you don't 
pre or republish COAs you should be OK.

Bests, have good weekend
l


>
> Thank you so much.
>
> On Thu, Sep 19, 2019 at 5:13 AM lemoene <lem...@gm... 
> <mailto:lem...@gm...>> wrote:
>
>     Hi AS
>
>     I hope you don't mind me replying via the list for benefit all.
>     Please subscribe
>     <https://sourceforge.net/projects/bika/lists/bika-users> to stay
>     abreast of updates
>
>>     I installed senaite lims along with bika coa addon to publish
>>     multiple samples into one report. Everything looks fantastic and
>>     works great for us
>
>     Good news. Remember that for Production LIMS, you need load
>     balancing and performance enhancing, typically ZEO, nginx, Varnish.
>     <https://www.bikalims.org/bika_senaite_professional_services#production>
>>     The lab needs COA NUmber/ID on results report. I found that on
>>     senaite Manual for publishing COA. But I am sure how to
>>     setup/achieve this step. Can you please guide me on this.
>>     image.png
>>
>
>     Ouch, that was wishful thinking. The screenshot is from Bika LIMS
>     3.2, Water and Cannabis, where we implemented unique COA IDs.
>
>     Is a must for ISO 17025 and regulatory compliance at labs
>     publishing more than one version of a sample's  COA, typically one
>     or two /Preliminary/ ones, before a final one, flexing for
>     potential follow-ups. They must have different IDs.
>
>     The feature did not make the migration to the Senaite code (yet),
>     and I see we re-opened the original improvement request. The Bika
>     Senaite ID machinery is well flexible and robust, and re-doing
>     this code can't be to complex/costly (2nd time today...)
>
>     Do you have cattle budget or code
>     <https://www.bikalims.org/contribute> Python?-]
>
>         https://jira.bikalabs.com/browse/CAN-6
>
>         Ditto Unique PDF title, https://jira.bikalabs.com/browse/BC-89
>
>     Keep'm coming
>     Lemoene
>
>
>
>
>
> -- 
> Sincerely,
>
> Afrin Shaik
> Database Administrator
> Kirkman Group, Inc.
>
> CONFIDENTIALITY NOTICE: This e-mail transmission may contain 
> confidential and privileged information or information proprietary to 
> the sender or exempt from disclosure under state or federal law, 
> including HIPAA.  Unless you are the named recipient, you may not use, 
> copy or disclose to anyone the message or any information contained in 
> the message.  If you have received this message by mistake, please 
> notify the sender by reply e-mail and delete this message.  Nothing in 
> this message should be interpreted as a digital or electronic 
> signature that can be used to authenticate a contract or other legal 
> document.  Thank you. 

[bika-users] Sample Point GPS

[Shaun G. <sh...@gr...>]

Hi all

 

Is there a way to change the entry of the latitude and longitude to decimals
instead of degrees?

 

Shaun

Re: [bika-users] + LIMS Combo Re: Bika Veterinary Setup and configuration

[Shaun G. <sh...@gr...>]

Hi all

 

I can't seem to add a sample in Bika LIMS - am I missing something?

 

Shaun

 

From: lemoene <lem...@gm...> 
Sent: Thursday, September 19, 2019 12:18 PM
To: bika user list <bik...@li...>; Bika Health
<bik...@go...>
Subject: [bika-users] + LIMS Combo Re: Bika Veterinary Setup and
configuration

 

Hi All

Hi Lemoene.  Ah, I did not think of Bika Health. Will Bika LIMS be able to
integrate with Bika Health? Then I only have to set up the instruments once.


That'll be ideal, but for one Bika LIMS Batches were morphed into Clinical
Cases (a patient disease event - they may have more than one) in Bika
Senaite Health We had an improvement request logged for bringing Batches
back into Health next to Cases, can't find it now. Not too difficult/costly
I always guess... to be investigated.

Seen in Biobanking requirements first, big batches _Studies, or Collections
- of  Samples, some of which may be part of Cases taken up in more details. 

To be properly thought through, there could be more exceptions




Please could you set us up on Bika Health?

Will dm demo creds. I see an opportunity to populate a Bika Vet demo..-) 

Also remembered that we did some work for Equigerminal in Portugal, very
breed focused, some genetics thrown in. The project petered out, some of the
code lives on, notably the Abaxis VetScan VS2 and ScilVet abc instrument
interfaces.

Bests
l