You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Okay, maybe we can call it "offline_comments"? I don't think that these comments need to be integrated to the DAQ system, they are explicitly post-DAQ and optional. The issue of who should be allowed to enter the comments is a good one, but there's no access controls on the rest of the DB so I think no restrictions are fine for now.
Ideally one would be able to view and edit these comments from the web site. Editing should involve some extra authentication work, and either one would have to access a copy of the website from inside the counting house or figure out a way to pass the values in from the outside. So, I think that to start with just modifying the comments via the python API is fine, but some more work would be needed to make this a non-expert activity.
We need another field where post-run comments could be added. It would be very useful if this could be be implemented before the next run.
The text was updated successfully, but these errors were encountered: