Trying to understand the steps to set a printer for the specimen labels - Most of the instructions reference file names and directory structures that do not match the OS V.2.0 - Do I need to deploy the web-service as JBOSS container in the PC where the printer is physically connected ? how do I configure the PRINT LABEL BUTTON -> even though I have done nothing to set it up - it gives me this message ==> Specimen labels print job 5 created successfully where are these jobs and how can be integrated with a printer or configure…any guidance would be appreciated.
Hi @Rolando_Ramirez,
In OpenSpecimen v2.0, the print label functionality is a built-in feature as opposed to older versions where additional components has to be deployed. All the print configurations can be handled using REST APIs.
For details please refer label printing configuration.
~Nitesh
The major change is that OS does not need the “print web service” any more.
However, you will still need an intermediate software like BarTender, NiceLabel etc to actually print the labels. We have a tie up with NiceLabel and will be testing with it.
~Sri
Thanks for clearing this out. I’ll look into the REST API link. Thanks
Nitesh,
Would have a guide for the integration of the OS printing labels and the intermediate software (NiceLabel) . Something more or less like this link below:
https://catissueplus.atlassian.net/wiki/pages/viewpage.action?pageId=25002009
also,
what are the permissible variables for the default_print_rules.csv ? and is this custom sample okay for OS.
----file start
#Class Type Login IPRange LType Tokens Printer
Tissue * * 127.0.0.1 Std specimen_label,specimen_type,specimen_type,specimen_location default
Fluid * * 127.0.0.1 Std specimen_label,specimen_type,specimen_barcode,specimen_quantity default
Molecular * * 127.0.0.1 Std specimen_label,specimen_lineage,specimen_barcode,specimen_quantity default
–file end
and when using the API for a windows environment for configuring the printer_rules which one of the 3 will work in your opinion.
1
{ “module”: “label_printer”, “name”: “rules_file”, “value”: “c:/os/specimen_print_rules.csv”}
2
{ “module”: “label_printer”, “name”: “rules_file”, “value”: “c:\os\specimen_print_rules.csv”}
3
{ “module”: “label_printer”, “name”: “rules_file”, “value”: “c:\os\specimen_print_rules.csv”}
I’m trying to see if I can use the auxiliary software from Nice Label “Automation Builder Easy” - is this part of the integration of your testing?
Thanks
-Rolando
Hi @Rolando_Ramirez,
We are in the process of completing all the documentation for v2.0. To answer your question, yes the sample print rules file shared with you is completely okay.
The configuration you shared is also fine and should work with OS.
Below JSON format will work fine on Windows:
{ “module”: “label_printer”, “name”: “rules_file”, “value”: “c:/os/specimen_print_rules.csv”}
~Nitesh
Sure Nitesh the file is okay but I added 2 more lines to the csv file - One for Fluid and other for Molecular
-I also included specimen_barcode, specimen_quantity as they were part of the variables accepted in OS version 1.2 -
Just wondering if you see any problem with the 2 extra rows I defined.
--------------------------------------FILE content
Tissue * * 127.0.0.1 Std specimen_label,specimen_type,specimen_type,specimen_location default
Fluid * * 127.0.0.1 Std specimen_label,specimen_type,specimen_barcode,specimen_quantity default
Molecular * * 127.0.0.1 Std specimen_label,specimen_lineage,specimen_tissueSite,specimen_quantity default
One more question in regard the LABELS in OS V2. Where could I find the BARCODE field when adding specimens - I think in version 1.2 was an specific field for it or the BARCODE field - in Version 2 is this based on auto_labels formats for Parent, Derivative, and aliquots when creating the Collection Protocol ? and then map it to a barcode variable in the LABEL TEMPLATE DESIGN (bartender - niceLabel)
Here’s the fields available when adding a new specimen -
Hi @Rolando_Ramirez,
Yes, you are correct the label will get generated and assigned automatically based on the format defined at CP level. For barcode, in the current UI, there is no direct provision to specify the barcode.
As both the label and barcode are going to be unique in the system. So you can map this label value with barcode while designing template.
Note: We are working on showing the barcode field on specimen UI too. This will be available in coming beta release.
~Nitesh
Nitesh,
Thanks for your response - Since you may know about the amount of work that requires to make modifications to the initial form for the specimens - I’m wondering if this form can be customized so it can have a legacy BARCODE field added to it - Obvious concern will be if this customization is done locally to the source code, most likely later will create problems for future upgrades to OS.
I’m just trying to weight the level of work that is needed for this modification.
Thanks
-Rolando
Cant you just print the label as a barcode?
At this point we do not have a fixed date for this but this will be fixed in one of the upcoming releases. Currently we are busy with wrapping up other use cases and testing/bug fixes. Once done we will fix this issue which might be 4-6 weeks away.
By putting both label and barcode on all the specimen pages it will clutter the screens, especially if most people dont use both. So we might need to make it configurable at the system or CP level to enable the barcode field.
~Sri
Related to this discussion, some users have been confused about the difference between “specimen label” and “barcode” fields in v1.1. This confusion arises when someone uses external software like BarTender or NiceLabel to generate a printable 1D or 2D barcode using the “specimen label” value. Since “specimen label” is a unique identifier within OS, it makes sense to use this value to generate a unique barcode, when possible. It looks like in v2.1, there is no barcode field - is that correct, @srikanth_adiga ? Attached is a screenshot from the public OS demo site of collected specimens for reference.
No barcode field yet in the UI. Its in the pipeline to add once someone needs it. The backend API supports it.
We did to want to clutter the UI with fields that most people dont use. So even if we add the barcode field, it will be configurable either at the system level or the CP level to display it.
~Sri
I seem to recall there were some plans to not need an intermediate software application for barcode label printing in a future version of OpenSpecimen. Am I correct? If so, is there any approximate timeline for this enhancement?
Thanks,
Matt
There were plans. However we could not make much technical progress on that front. At this stage this plan is shelved.
You will need Bartender, NiceLabel or CodeSoft (or others) in between OpenSpecimen and the printer. Unfortunately these applications run only on Windows. So if you have OpenSpecimen on Linux, you will still need an extra Windows box to configure the printer.
~Sri