Closed vpchung closed 4 months ago
@tschaffter @rrchai please update the ticket as you see fit.
@vpchung Thanks!
I like the "continuous benchmarking", but it might be a little lengthy for our existing filter panel. A shorter alternative name would be ideal. Otherwise, we can still adjust the UI accordingly as we go, or not.
Oo good point. What about:
The last one could work, considering our team is "Challenges and Benchmarking" ?
"Benchmarking" +1 or could shorten "Continuous Benchmarking" to "Continuous Benchmark" (20) as well. You can make it call, unless @tschaffter has an alternative suggestion?
I feel < 22 chars won't look overextended in the filter panel
My vote goes to Continuous Benchmark.
Could we add the category "Hackathon" while we are at it? This may help us to identify a more generalizable solution/implementation.
PR started in #2404.
Though the facet values are there, neither of them work. Instead, an error is received when trying to use either of them 😅
This is probably where you guys come in! @tschaffter @rrchai
@tschaffter do you think this is something we can add to the sprint this month, now that we have ~12 hackathons in our db?
Let's go for it!
As a user, it would be great to find challenges that are considered continuous benchmarks, e.g. CODA TB, Multi-Atlas Labeling Beyond the Cranial Vault, or hackathons, e.g. QBI Hackathon 2023
Re: benchmarks: rather than add it as a challenge status, it may be more appropriate to add this as a challenge category instead, e.g.
Development workflow
openchallenges-api-description
) (@vpchung )