Migrating submissions from old phase to new phase

Ready for functional review/QA/staging!

- [x] Use leaderboard entry as submission to move, if no leaderboard entry grab latest
- [x] `auto_migration` phase flag
- [x] `http://domain.com//competitions/check_phase_migrations` url, pinged every 3 hours
 

In _submit_results_page.html, consider adding a field, which indicates whether manual submission are allowed or not (e.g. look for phasestate to see how information is passed from the view to js code).  Then modify ‘decorateLeaderboardButton’ in ‘Competition.js’. If $('#manual_submission').val() is true, then do what the function currently does; otherwise, btn.addClass('hide'); Would that work?

 

 

From: Eric Carmichael [mailto:notifications@github.com] 
Sent: Tuesday, June 17, 2014 5:10 PM
To: codalab/codalab
Cc: cpoulain
Subject: Re: [codalab] Migrating submissions from old phase to new phase (#452)

 

In codalab/apps/web/templates/web/common/_submission_details_template.html:

> @@ -25,7 +25,11 @@
>                          </div>
>                          <div class="small-2 large-4 columns preloader-handler"></div>
>                          <div class="small-2 large-4 columns">
> -                            <button class="button rFloat hide"></button>
> +                            {# Hide "add to leaderboard" button if force_Submission_to_leaderboard is enabled #}

What would you recommend to solve the problem of showing 'Add To Leaderboard' button with force_submission_to_leaderboard = True?

Simply hiding it seems OK to me, for the sake of getting this merged sooner-than-later.

—
Reply to this email directly or view it on GitHub <https://github.com/codalab/codalab/pull/452/files#r13893888> .  <https://github.com/notifications/beacon/3453398__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcxODY2OTM5OSwiZGF0YSI6eyJpZCI6MzM3NTMzNjZ9fQ==--8b4a28f6e16db4a9b263163a2fa58185c5f86fb5.gif>