While working with the SENAITE lims (senaite.lims 2.1.0), we’ve come across such a use-case as requiring users to access the LIMS system in their time zones. Tinkering with the SENAITE UI we came across this site setup (/@@dateandtime-controlpanel ) and had the following questions, 1.) Can the setting be user specific other than global/for all users and 2.) If yes, can it be set automatically based on the user’s client information?
Hi @mksd,
We are happy to provide individual support via our paid services.
Please contact hello@ridingbytes.com for further details and to receive an offer.
Thank you for your understanding and best regards,
Ramon
Thanks for the pointer @mksd, I somewhat can’t locate the timezone setting through the portal. However I have an impression that theoretically, this is supported already in plone from the following Plone community thread. I’ll also look into a suggested plone.app.event add-on and share my findings here.
I however cannot see the effect of doing so when I change my browser’s time zone. To confirm this, I created two analysis requests in different timezones and received them using the respective timezones to change their status. The received time timezones where inconsistent. Additionally changing my browser’s timezone doesn’t consequently change time I see.
Is this your way at Mekom Solutions of building a serious business relationship with a software vendor?
If so, I would highly recommend investing in a business communication course.
We will look into that as soon as possible and eventually open a PR if this is a bug.
I think it was clear through this thread that we were documenting our steps in researching SENAITE’s ability to support a specific use case. Namely, does SENAITE allow clients to be on different timezones? Does its UI reflect this appropriately, etc?
It sounded like a fair question to ask the community.
We felt (and apologies if this is inappropriate) that it wasn’t adequate to book a paid-for consultation to get a bug confirmed. We were rather trying to 1) first confirm that there is indeed a bug and then 2) if confirmed, potentially book a consultation with a service provider to get it fixed.
P.S. I always say, in the name of our company, that the most basic way to give back is at least to present ourselves which we have done (for instance here where it is clear what we attempt to do with SENAITE) and to provide feedback, such as reporting bugs. I am sure that you will find it interesting that in the community where we are most active (OpenMRS), we often do not get either of those two steps from others: many organisations use (and make business) anonymously and do not even bother reporting bugs, sharing their use cases or provide feedback.