Primary Set-Up UI: "Prizes" Section

[acshields]

Designs

Section Display Order

• "Prizes" section is displayed after the "Timeline" section
• "Prizes" section is displayed before the footer of the set-up screen

Specification Section Fields & Functionality

Header of Section

• Section Title: "Prizes"

Main Body Question/Answers

Field 1 is required, but layout (number of rows) are determined by Prize conditional logic described in Issue 750

[maxceem]

1. What are the possible prize types? Should we hardcode them, or there is some API endpoint for retrieving them?

   

2. We already have prize type per prize, where we are using USD at the moment. Where should we store the global prize type which is Monetary on the screen? I mean inside API.

   

3. Checkpoint prize has x5 mark:

   1. Is it always 5 or should we be able to edit it somehow?

   2. In terms of API. Do I understand it correctly, that we have to store it as 5 records of checkpoint prize, as there is no place to store such a multiplier?

   

4. Do I understand it correctly that we only show the Checkpoint prize for challenge of type === Design and format === Challenge. Not for tasks and not for first2finish.

[vikasrohit]

1. It should be hard coded for now. @rootelement please let us know the possible values of prize types.

2. I guess, it is meant for choosing exact prize type per prize. I am assuming that first prize type selection is just a categorization of the actual prize types e.g. the final prize type might be USD, INR, DR POINTS etc, however, USD and INR can be categorized as Monetary prizes types and DR Points can be called as Points category. Again, we need expert life line here from @rootelement

3. i) @acshields we need your inputs here
   ii) Yes, even if we are hard coding that x5, we have to store it as multiple items in the prizeSet.

4. Yes. Do we have format field available in the challenge payload? I don't remember we setting this field when creating a challenge.

[maxceem]

@vikasrohit here is format

[vikasrohit]

ohk, it is actually type in the api. https://github.com/topcoder-platform/work-manager/blob/develop/src/components/ChallengeEditor/Type-Field/index.js#L13.

[acshields]

Question 1

Prize Type @rootelement - are we even in a position technically where we could/should be supporting different prize types right now? (outside of the question of are we business-ready for it). @vikasrohit - I ask for two reasons:

1. Trying to determine whether we don't develop the UI for this question at all right now, or if we do.
2. If we do, it just dawned on me that this question should probably live in the "Advanced Settings" question section.

Question 2

Monetary Type Dropdown @rootelement - will welcome your opinion here. In my opinion, while I don't think there is anything prohibiting the use of different currencies in the same challenge (might be wrong), I do think it would be very unusual for a user to want to do this. From a logical standpoint, what I think we should do is:

• Make USD $ the default
• Allow user to change the default in the dropdown list
• Ask the user if this change applies to all of the other prizes's currency

OR

• Move the currency dropdown under the Prize section's Advanced Settings, as a part 2 question to the "Prize Type" one, where if a user selects "Monetary" then they can also pick the desired currency.
• Make the USD $ the default for monetary type
• If the user changes the monetary type in Advanced Settings, these changes would apply to all of the prizes.

I am leaning towards option 2 here, but @vikasrohit I wanted your input on if one is more preferred to the other from a technical standpoint. Also, will you need me to get the "Prizes" portion of the design update to show these changes?

Question 3

Checkpoint Prize Multiplier - @vikasrohit - yes, this was the intention behind the design. However, before we solidify a workable strategy on this let me chat with Tony on this. I have a couple business operations questions for him.

[acshields]

@vikasrohit - I checked in with Tony on a couple of my business operations questions for the checkpoint prizes. What he confirmed for me:

• Design: Has standard prize amounts, which the platform should enforce (I will create a separate issue for this).
• Checkpoint Prize Value: The checkpoint prizes are always the same value.

Essentially, what I was trying to confirm was that for checkpoints & the UI was that:

1. Having a single field for checkpoint prize entry is the easiest
2. With just one field, all the user needs to enter is the prize value (if not already standardized, like Design) and the number of checkpoint prizes, i.e. the multiplier (if not already standardized, like Design).

Given those insights, I would pursue the technical strategy that allows the # of checkpoint prizes to be stored as items in the Prizeset.