• FEATURES
  • PRICING
  • MARKETPLACE
  • CASE STUDIES
  • BLOG
  • v3.3 Improvements: remove "auto" container from dropdown

    I see one improvement for v3.3 is to remove the “auto” option for containers, as the auto function has not been implemented. I see details for the improvement in the following JIRA: https://openspecimen.atlassian.net/browse/OPSMN-3197?filter=16600

    Since container enhancements are being considered for future versions of OpenSpecimen, I wanted to share some container-related feedback we received from a prospective user:

    While the “copy first to all” button assigns the container name to collected specimens, row/column are not assigned. It would be nice to select row 1 column 1 for the first aliquot and be able to have OpenSpecimen autofill row 1 column 1-7 in the same box for the remaining 6 aliquots.

    Are there any other users who would find an autofill option helpful when storing collected specimens?

    In this case, the system will assign the next locations once you submit. Did it not work?

    ~Sri

    We are also interested in the auto fill feature

    @srikanth_adiga in v2.5, the auto feature does not appear to be working; specimens are assigned a virtual location. In previous OS versions, I recall the system assigned specimens to the next available location, and did not allow the user to specify from which storage position the auto-assignment starts. I think our prospective user is envisioning being able to specify the starting storage location position where auto-assignment starts (and to do so from the specimen collection page).

    Hello Matt,

    I checked this scenario on demo site and it is working as you expect. Please see screenshots below. You can check this patient which I entered - Test_Patient


    During collection, select position for first aliquot and submit. Post submit, the system will auto assign next available positions in the same box. Is this not working in v2.5?

    Thanks,
    Poornima

    Thank you Poornima. It looks like auto is working for v2.5 - it’s just working in a much different (but good) way compared to previous versions. Our users really haven’t had much need for the auto feature until a recent request.

    I see that if a container name is not selected, the storage position defaults to virtual. When a container name and row/column are specified, specimens downstream in the tree are assigned to sequential available positions. I see it is possible to specify multiple container and row/column starting points. I will follow up with the user and see if this functionality meets their needs.