-
Notifications
You must be signed in to change notification settings - Fork 0
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
Improve Portal landing view data table #303
Comments
I notice on subject API it takes values from the LIMSRow. Wondering if that should be changed to use LabMetadata at the API side. |
Descoping from 0.9.0 release for now |
Dependency on LIMSRow is high. We will need more time to refactor at backend. Marking it as rolling refactor. Any newer feature/work shall be using LabMetadata. On frontend, we will introduce with UI v2 release. |
Descope from 2.0 release for now. Somehow, this is ongoing refactor happening underway. We shall revisit and finalise in future iteration. |
Related #548 |
Attempted to tackle this with --
However. Portal landing home page still rely on LIMS kind of view whereas showing Runs <> Meta linking together as DataTable. Anyhow. This is still considered some baby-step progressed. Descoping it from 2.1 milestone. Shall revisit again, future iteration. |
Context:
At the mo, in Portal landing page, the data table view is using LIMS data to allow show/filter Runs, Subjects...
Action:
The text was updated successfully, but these errors were encountered: