2024-01-18: QC Stakeholders meeting #382
Replies: 2 comments
-
I am not able to make it to the stakeholders meeting tomorrow, but just wanted to share my perspective that it might make more sense to focus on first getting mouse QC working in Code Ocean before adding additional features like container reports. Much of the infrastructure will have to change to ensure compatibility with Code Ocean, and it may be a waste of effort to build new features only to have to re-do or refactor things after the Code Ocean switch. Another consideration is that the way that cell matching (which is central to container reports) works and how the data output is formatted may be quite different once it is implemented in Code Ocean, so building a report against the current LIMS data format doesn't really make sense. In general, migration to Code Ocean should be the highest priority, other than urgent bug fixes, as we work towards the goal of decoupling from LIMS as soon as possible. |
Beta Was this translation helpful? Give feedback.
-
I will go ahead and make an issue for migration to code ocean so we can view that in context of all the other open tickets. I'm guessing that ticket will really morph into a couple of milestones at least that will spawn tickets of their own as we implement specific things. |
Beta Was this translation helpful? Give feedback.
-
Agenda:
QC Stakeholder meeting kick-off!
Beta Was this translation helpful? Give feedback.
All reactions