-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a cleaner way for inputting projects and judges #7
Comments
CSV actually isn't that bad if its done right. Every experience I've had with, say, devpost, has been terrible. I assume you were already using a google form as the gathering mechanism, which would make sense, then the only change might be to create an api endpoint for adding hacks, and have the form ping your endpoint (gscript ftw) or at the point that you just have a POST point you can write a bunch of frontents including perhaps a not-awful webform of your own. |
Yup, HackMIT just used a Google form (well, actually, we initially used Typeform, but then Typeform went down halfway through project submission). Yeah, having something that grabs submissions from a google form would be neat. And yeah, eventually building in project submission would be nice. |
Alright, so Annotator=Judge, and Item=hack. So realistically in a perfect world you'd want to be able to register a team early (as in, at the start of the competition as part of registration), have the team sent a secret via email much like the judges are, and the secret give them access to a form where they can input (/update) information about the item. And simultaneously expand the Item table to include other project metadata like pictures, github links, etc. |
Yeah. Though having people submit stuff through Devpost is kinda nice because a lot of people like having their projects publicly visible on there. And having people submit two almost identical forms is kinda tedious. |
Right, without a devpost api (either import or export, as far as I can On Wed, Jul 27, 2016 at 2:46 AM Anish Athalye [email protected]
|
Oops, I mixed up this thread with #8. Yeah, having a google sheets import mechanism or a custom frontend for having judges sign up would be great. |
Still interested in incorporating Google Sheets? If so, should this type of input be similar to the csv/xlsx PR that was submitted recently? This could be useful because entries could be updated in realtime, and it forces organizers to have a backup db... |
Google sheets import seems like it shouldn't be too bad (but at that point, having to download and upload a CSV doesn't seem too bad either). Google sheets sync could be cool, but I'm not sure how useful it is. Also, it seems like it could be pretty hard to implement. Not sure if it's worth the effort / the effort may be better spent on #44, for example (or maybe even something analogous to that for judge sign-up). |
Right now, there's a CSV import system, but it would be nice if there were a cleaner alternative way of doing it.
This is a design problem, so discuss here before writing any code.
The text was updated successfully, but these errors were encountered: