Coding for planned samples - Enterprise only feature?

John_M · October 16, 2018, 8:24am

Hi,
I have tested out bulk importing of our past collected samples in community versions 5.1.0 and 4.3.4. The coding for planned samples, outlined on - https://openspecimen.atlassian.net/wiki/spaces/CAT/pages/28442626/Bulk+import+planned+specimens – Option #1, doesn’t seem to work on the Community edition. Could you tell me if this an Enterprise only feature please?

Thanks,
John

Neha_Nimgire · October 16, 2018, 2:39pm

Hi @John_M,

This is a feature available in both community and enterprise edition.
For importing planned samples using bulk import, you need to assign codes at specimen requirement level and use the same in the bulk import sheet under column ‘Specimen Requirement Code’.

Is the code field visible at the SR level?
Were you able to add codes at the specimen requirement level?
If yes, can you provide us the bulk import sheet you tried?

Thanks,
Neha

John_M · October 17, 2018, 7:39am

Hi @Neha_Nimgire,
Yes codes are visable and set at SR level to the same as the import file.
I’ve attached the bulk import sheet and a screenshot of the SR with codes.

specimenParent_IN_4998.csv (1.8 KB)

Thanks,
John

John_M · October 23, 2018, 2:35pm

Hi @Neha_Nimgire,

So is this user error or is the coding for planned specimens not working?

Best wishes,
John

Neha_Nimgire · October 24, 2018, 10:55am

Hi @John_M,

We are not able to reproduce the issue on our side. Can you try reproducing the issue on our demo site - http://demo.openspecimen.org/?

Let us know once you able to do so.

Thanks,
Neha

John_M · October 24, 2018, 1:21pm

Hi @Neha_Nimgire,

Found the problem, the specimen type was ‘Whole blood’ in my upload file. But ‘Whole Blood’ in the specimen requirement. This caused the mismatch. The coding feature worked correctly once changed.

Thank you for taking a look at the issue.

Best wishes,
John