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

Storage location incorrect if "Storage addon" is used #7

Open
Migulo opened this issue Jun 11, 2019 · 1 comment
Open

Storage location incorrect if "Storage addon" is used #7

Migulo opened this issue Jun 11, 2019 · 1 comment
Labels
Bug 🐞 Something isn't working

Comments

@Migulo
Copy link

Migulo commented Jun 11, 2019

Description

If samples are stored by using the "Storage addon" the "Storage location" part of the sample specification is not updated within the "Sample View" to the storage location of the "Storage addon.

Reproduction guide

Storage location within the "Storage addon": SS_0001

image
Storage location within the "Sample view": R29 Schwerlastregal

image

Observed behaviour

See above

Expected behaviour

If a samples is stored by using the storage addon, the storage location within the sample view should be consistent with the storage location of the storage addon

Versions

  • OS: Linux

  • senaite.core: 1.3.0

  • senaite.impress: 1.2.0

  • senaite.core.listing: 1.1.0

  • senaite.core.storage: 1.0.0

Traceback

<<BACKTRACE IF RELEVANT>>

Screenshot

see above

@xispa xispa transferred this issue from senaite/senaite.core Jun 19, 2019
@ramonski ramonski added the Bug 🐞 Something isn't working label Dec 7, 2023
@ramonski
Copy link
Contributor

ramonski commented Dec 7, 2023

Yes, this is in fact an issue that we need to take care of.
Currently, the "Storage" field in senaite.core is not aware of the senaite.storate location.
Probably it can be simply set if the sample is stored and unset if it is recovered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug 🐞 Something isn't working
Development

No branches or pull requests

2 participants