We may want to attach competitions/such with users authed on ChaHub.....................

I am trying to add the idea of a Producer to ChaHub, which is any server (i.e. competitions) which produces data for ChaHub. What if we want to associate a user profile as the owner of this competition, how should we go about that?

• handle duplicates (receiving same competition twice)
• Handle creating "api keys" for each new competition server...

• Be able to connect to OrcID or github or something like that
• Be able to register an account manually
• Create base schemas
• Be able to search through data

Is active is returning more results with a query than without one.

Should be able to open a modal like above which produces an html iframe

Add default searches to Base view get_context_data() so we don't have to wait for that first search to load.

Un-Published Competitions are currently pushed

We should:

• double check the logic on the is_valid check
• check edge cases:
  • What happens if someone publishes a competition, then un-publishes it. It will still have an entry but not a valid link

Next Deadline is currently not working

• Not displaying
• Filter does not work

the name of the organizer and
when created.

URL should update as you search so if you copy + paste address to someone, they see what you see.

• Add Chahub logo to upper right
• Add codalab like footer
• Add contact
• Add link for Github issues
• Verbosely highlight that Chahub is a service of/for Codalab

Allow search results to be filtered by producer:

IE: Only from codalab.lri.fr or competitions.codalab.org

Add prize amount to the competition tile and add filtering

When someone shares Chahub to Facebook it should show a nice logo, description, etc.

Form should have these fields:

1. title
2. description
3. url
4. start
5. end
6. organizer email

Form should submit to an approval process, maybe emailing a few selected people, and then following a link "approves" the competition and adds it to ChaHub. This competition can be manually changed by administrators, or maybe through some admin interface in the future. The user will have to register before submitting the competition to be able to edit it in the future, or at least they will need to provide an email we can track and verify for editing permissions.

We'll probably want to setup django-activity-stream

• Chagle
• Competitions V2
• ChaLab

Eventually will pair with Chaladmin

Design

What if I accidentally end up with 2 accounts on Chahub?

We should have a protocol for allowing you to completely delete old/unwanted accounts. All submissions would be marked as made by "missing user" at that point.

How can I reclaim my lost submissions/competitions from deleting an old account on Chahub?

We could have a protocol for re-assigning datapoints (competition, submission, task, solution, etc.) to a given user. This could be in User Management section of Chahub to "reassign" a user -- all of their datapoints would point to some new user and the old user would be removed.

What happens if you "login with Chahub" to an existing Chahub and already have an account on Competitions?

It will connect with OAuth your account on Competitions to Chahub if Chahub email matches an email from Competitions. It will not make a new account on Competitions. If your email on Competitions is different from your Chahub login, there is no way for Chahub to match you to that account on competitions.

We could have a button once logged in to "link with Chahub" your profile?

How does a site add a "sign in with Chahub" button

We have to register them in python-social-auth and give them a client secret/etc. to generate OAuth tokens for users

How will hall of fame work with users spread across so many servers?

Users will be uniquely identified by their email. Many emails may belong to one account, but the email must be unique across Chahub. When a submission is finished it is sent to Chahub and is associated with a user.

To even associate submissions with a User, how do we get Users?

Upon confirming your User account by email, the User will be sent to Chahub.

Race condition: what if someone signs up and makes a submission, but does not exist yet on Chahub yet?

Chahub will raise an error and return that it was not able to successfully add the User. The User model and submission will be marked for re-trying. Every hour or so the server attempts to re-submit failed sends, and should resend the Submission and User.

To make it not a permanent failure loop we will make sure USERS are sent/processed before SUBMISSIONS! It's not the biggest deal, because if we do retries properly User should get caught even if it arrives after, then the next send should contain the Submission that is now valid.

Spec

Chahub

1. Setup django-oauth-toolkit again, if it's not still there
2. Ability to register on Chahub
   1. Registration should require email activation, at least on prod
   2. Does reset password work?
3. User model should be able to accommodate many emails
   1. Remove field email and add emails which can be a Postgres array of strings?
4. User management:
   1. Ability to delete account
   2. Ability to assign a user to an existing user, overriding the old user with the new master user
   3. The above "Reassigning" should require a confirmation prompt where you type in the user's name you are deleting

Codalab v1.5

1. Setup python-social-auth
   1. Make sure Chahub returns the information necessary to generate user: email, username
2. Make a Chahub adapter
3. Add a "login with Chahub" link in header
4. Add a "login with Chahub" link in login form
5. Make ClUser a ChahubMixin
6. For existing users, we should have a "link with Chahub" button that automatically creates an account on Chahub with the same email and initializes a "password reset" process to enter in a new password... is this overkill?

Codalab v2

Still in dev, will implement these as necessary

Platform name, Start, End, # of participants, next deadline date

Add in header: the current number of:

1. competition
2. competition organizers
3. registered users
4. active users (made entries in the last 3-6 months or so)

Color phase deadline red if within 1 week or some such

• Fuzziness too fuzzy? (Possibly boost the title field more)
• Competition Tile organization/layout tweaks
• Possibly strip html/js from description. (Check on v1.5 if you can imbed js in the description)

Clear the database of old entries.

Competitions from before valid checks, is_active logic, and other changes may still be displaying

Possibly boost html_text by 2:

• Searching for Chalearn (keyword should be stored in the html_text field) does not give us proper results

Can use these as a base example https://www.kaggle.com/tags

• Establish QA Review from Phase 1 Wireframe
• Implement Necessary Changes
• Ensure all pages have proper UX Flow

Create embeddable widgets for v1.5 search: IE: Replace the current database query search with a widget that utilizes Chahub

Sorting by participants currently is not taking all competitions into account. IE: AutoML has more participants than the default query sorted by participants.

Start the process of setting Chahub up on an official domain: IE: Chahub.org

Should link to API docs (https://www.chahub.org/api/v1/ -- but relative to the current server, of course)

It's pushing the search to the left

When sending to chahub, set timestamp to None until we eventually get a valid response. We can re-try this with a celery task every ~5 minutes for each chahubmixin class that fails. We'll need to somehow set each of these classes in some global list to check against.

I.e. Competition(ChaHubMixin) and Submission(ChaHubMixin) might both need retries, so when we query we'll have to check like...

for model in ChaHubModels:
    needs_retry = model.objects.filter(chahub_needs_retry=True)
    for instance in needs_retry:
        # Saving forces chahub update
        instance.save()

Instead of displaying the same default, generate a random logo like GitHub does for each profile. This will make it look better when scrolling and such through RAMP results

The crawlers will be simpler if they require no storage, we can leverage Chahub to remember which competitions have been seen or not. Instead of sending competitions one-by-one, we would work with 2 endpoints:

1. competition-existence-check/ which takes a JSON list of competition REMOTE ids and returns the ids that do not yet exist on Chahub
2. modify competition/ POST to accept a list.

the name of the organizer and
when created.