-
Notifications
You must be signed in to change notification settings - Fork 1
Description
What are you missing?
In the current upload process, the user has to do their sample updates and registration batchwise via the distinct batch component.
Why do you need a solution?
Multiple Reasons
1.) Its needlessly cumbersome for other facilities that want to update multiple batches at the same time.
2.) For Facilities working with a singular batch, the distinction and focus on multiple batches is confusing
3.) Batch component takes up a lot of space in the sample grid making the visualization of samples within the view less ideal.
4.) By removing the batchwise focus during sample editing/registration, it would allow the dev team to reuse the generic filtergrid currently being defined within the measurement context.
Ideas
1.) Remove the batch component and move the batch definition as a (ideally mandatory) distinct column within the sample templates for:
A) Registration
B) Editing
UI Prototype can be found here
Please also ensure that for each sample the Modification and Registration Date is shown within the sample grid UI.
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Status