Separate successful conversions from drafts #54
Conversation
…first page of Guided Mode
|
I'm still not crazy about classifying a pipeline as being 'done' at any point It's so common to want to rerun on a new batch of files, or even reupload to DANDI Don't get me wrong, we should definitely have some kind of history or log that keeps track of what pipelines were completed and how they were run, but it doesn't have to become a state of the pipeline itself |
|
Yeah, that makes sense. This is why I've tried to separate pipeline design, pipeline runs, and DANDI uploads in #58. In that case, there'd only be validated / approved pipelines that have gone through the entire design process—which are always able to be revised or run on different data. Is there anything about the wording you'd like me to change right now? |
TBH the only classification I'd give is 'in progress' to indicate a pipeline is not complete (complete meaning only that they are past the metadata form step, not that they hit the 'run' button) |
|
Maybe we should mock it up a little bit in Figma first - putting this into draft until then |
|
Can you draft a small mockup for this? I'm envisioning that the existing pipelines looks exactly as it does now except any pipeline that didn't hit the 'run conversion' button is flagged as 'in progress' The history tracker is probably a separate feature altogether and can be put in a different place in the app too |
|
@garrettmflynn Should we keep this open, move to an issue, or close? |
|
If we don't really want this separation (at least for now), we can just close it. Otherwise we open a new Issue that clearly defines how we'd want a separation between existing conversions and completed conversions to look. |
That would be ideal |
This PR changes the rendering of successful / completed conversions on the main Getting Started page so that successful conversions are distinguished from drafted ones.
A few cosmetic changes are also added to the page to align it with NWB GUIDE rather than SODA.