ORP Proposal Submission Tool
Naming technical goals #14
Replies: 3 comments 2 replies
-
|
id agree that the database id as the indentifer is a bit naff. that being said, ya just replacing 1 identifier with another less reliable one. You would need to add some defaults. such as "technical goal + incrementing number" for the cases where users dont fill them in, as otherwise youd have a dropdown full of empty rows. a part of me wonders if we're looking at this in the wrong side. Maybe instead of a dropdown with summary data in the observation form, which when selected, shows the table with that row's data. maybe the observation form should have the tables for targets and technical goals, and the user actively "selects" the row they want for this observation, so theres no need for a dropdown at all, and thus no need for the summary? Ive noticed that the mantine tables youve used so far are not selectable, but there must be modes to make them selectable. |
Beta Was this translation helpful? Give feedback.
-
|
a very simple proof of concept for a selectable table can be found here: orppst/pst-gui#74 where it just allows the targets table in targets to be selectable. If we think this is suitable, we can migrate the logic to the observation edit page and impliment it as required. |
Beta Was this translation helpful? Give feedback.
-
|
Conceptually, I think this could work. Practically, I'm not sure how much screen real estate it would take. I don't know how many targets and technical goals are in the average proposal 🤷🏻♂️ |
Beta Was this translation helpful? Give feedback.
-
|
could limit the screen real estate problem by making the table scroll-able with a max elements at view at any given time. |
Beta Was this translation helpful? Give feedback.
-
|
orppst/pst-gui#77 is a impl of this idea in full. |
Beta Was this translation helpful? Give feedback.
-
At the moment technical goals consist of an array of numbers and units with no overall descriptor.
When a user is prompted to select a technical goal within an observation, they are presented with each goal's database id, which clearly will mean nothing to anyone.
I don't see a way of creating a readable summary / description of technical goals on the fly, so my idea is we add a free form text field to technical goals for investigators to name goals accordingly.
Beta Was this translation helpful? Give feedback.
All reactions