GTN Header - Adding a Answer Key Histories drop-down menu #4881
Conversation
Realised I also need to follow up on another PR to add that troubleshooting snippet here!
There was a problem hiding this comment.
Thanks for getting the conversation started!
I've proposed a more structured data format, and it's an interesting idea about the histories index. I'm not sure how best to handle that.
You would envision people going to this separate page to see the available histories?
And I guess I wonder what we want to do in the future, with the workflow testing framework, if we should plan to attach these to specific workflows (somehow).
topics/single-cell/tutorials/scrna-case_alevin/histories_index.md
Outdated
Show resolved
Hide resolved
|
I think the answer key history list should be a drop-down menu, and then the final option (or first option, depending) should ALWAYS be the history_index.md that I started, labelled "Using history answer keys" as the button. So if they understand, they can just click the history and it imports it, or if they don't, they can select 'using history answer keys' to learn |
|
I put an 'input histories' there, but actually, that's probably not necessary (although I could absolutely see a future wherein the 'Get data' sections automatically pull from the input histories just like they pull from Zenodo, but it's not strictly needed atm). I think mentally I was thinking it would be valuable to quickly see which tutorials have input histories and which don't, so that we could make the input histories and keep everything up to date, but that probably goes with the whole workflow / history / automation plan and isn't necessary NOW, so happy for it to be binned. |
|
I think this is a good interim plan. We can make something like this work |
|
Ahk, bad me, I've put this in two places |
no this is fine, perfect even. you filed an issue to see if the implementation was reasonable/desired, we agreed, and now you've opened a PR to implement this (which we will get around to eventually i promise). I've tagged this PR as "Fixes #4594" which will ensure that when this is merged the associated issue is auto-closed. that's a great workflow! Especially for feature requests where you want feedback on if it's possible or so. |
|
Looks good I think, added an optional 'date' field that can be used (or not, or automatically extracted from the history/etc).
|
|
Woooo! |
This is the first attempt to get the conversation started
I'm wondering if it would be ideal to have a landing page, like with the workflows, where we stipulate how to import a history, compare, and drag datasets between histories so they can help themselves if they get stuck.
Fixes #4594