john-hewitt / scrambled Goto Github PK

when parsing into javascript. don't forget!

it currently is not....

Workers should not be able to move on to the next sentence if they have not completed the current one. Should be fairly simple (if janky) — say, create a counter variable, and when it hits the length of the current sentence array, enable the next button. We'll just have to be careful to make sure the "next" button starts out disabled, and reset the counter every time we get a new sentence.

30 columns have our gold standards. Will 30 further columns have the workers' solutions (if they exist?)

What will the format be? Will they be '|||'-delimited? My vote is yes.

Also, using the issue tracker on GitHub? What are we, actual software engineers?

Not hard to see why this is a problem.

figure out a nice way to get all the sentences from MTurk's input format into our Javascript stuff. uses ${variable_name} format...probably will end up using '${sentence' + curr_sentence_index + '}' or something