HackTheHearst Contest Requirements
The goal of the hackathon is to develop a compelling app or user interface to facilitate access to the digital images and collections information that the Phoebe A. Hearst Museum of Anthropology is making available through an API. This user interface should allow users to pursue real research questions, and engage with the material in new ways. Each group will present their project expo-style to judges and spectators on the morning of Sunday, September 21, and the sixteen highest-ranked projects will be presented before a panel of judges in the early afternoon. The winning group will present their project before a public audience later that day as part of the closing event (see the event schedule for details).
The following requirements and guidelines apply:
To be eligible for awards and prizes, entries must:
- increase online access to the Hearst Museum's digital collections information.
- be based on the API for the Hearst Museum’s digital collections information (i.e., use the API to ensure that data presented are current).
- not use a proprietary platform or programming language (e.g. no ASP.NET).
- not use a proprietary API or an API not available to other participants.
- be checked into GitHub by 12:01 AM on September 21, 2014, for technical judging.
- be finished or presented "as is" during the expo round of judging, which begins on September 21, 2014 at 10:00 AM.
- not be indecent, defamatory, in obvious bad taste, or disrespectful in any way.
- abide by HackTheHearst's anti-harassment policy.
- comply with campus security and accessibility policies.
- Here are some tips for web accessibility
- The winning entry must generate no errors when run against the WAVE Web Accessibility Tool
- If an entry is selected for deployment, it will undergo a security review using AppScan
- be created by a team composed of members who are not employees of the Phoebe A. Hearst Museum of Anthropology or of UCB Research IT, and are not immediate family members of any such employee or of any HackTheHearst speaker, mentor, or judge.
- be reachable by judges at a publicly addressable URL (with or without credentials) on Sunday, September 21, 2104. Note: if your team does not have the resources to do this, speak with one of the technical mentors at the kick-off event and we'll work with you to find a way to make this possible. Here are some suggestions for Platform as a Service (PaaS) options in case you don't already have a place to deploy your project:
- Heroku: Supports Ruby (including Rails & Sinatra), Java, Python (including Django & Flask), Node.js, PHP, Scala (including Scalatra), Clojure, Play
- Google App Engine (GAE): Supports Java, Python (including Django & Flask), PHP, Go
- Openshift: Supports Java, PHP, Python (including Django & Flask), Zend Server, Perl, Node.js, Ruby (including Rails & Sinatra), Vert.
- give the Hearst Museum a non-exclusive right to use the software developed.
To have the best chance of succeeding in HackTheHearst, you'll want the help of a strong and balanced team. We'll leave it up to you to determine the ideal number of team members and the best balance of knowledge, skills and experience among your team members. We recommend you assemble a team of about 4 people that has as many of the following strengths as possible (note that single individuals will often fill more than one of the following roles):
- someone with web design experience
- someone with UX (user experience) design knowledge
- someone with web engineering experience
- someone with programming expertise
- someone with subject matter knowledge
- someone with knowledge of the audience
All teams must be composed of members who have registered to participate in HackTheHearst. Participants may either register for HackTheHearst as a pre-defined team, or register as individuals who will later form or join a team.
Teams, once formed, must be recorded by the event organizers. API keys will be given to team members after their team is officially recorded, but no earlier than the official start of HackTheHearst. To record a team, a member of the team must present the names of the team members (and an optional team name) to a designated staff member(s) at the opening event, or sent to email@example.com.
A team of technical mentors, subject area mentors, and target audience mentors will be available to all teams participating in the HackTheHearst events. Mentors will be available in person at the kick-off event, and available throughout the hackathon timeframe (September 10–21, 2014) by email to answer questions and provide guidance. There will also be a number of informal mentoring sessions between September 10 and September 21 where mentors and participants can meet up and talk (see the event schedule for details).
App development time frame
- Each participating team will be given an API id and key once their team has been officially recorded. The recording of teams will begin at 6:00 PM on September 10, 2014.
- Once teams have their API id and key, they will have until 12:01 AM on Sunday, September 21, 2014 to develop a fully or partially functional app or interface.
There are four prize tracks for HackTheHearst:
- Overall best app (1st, 2nd, and 3rd places)
- Best app for K–12 education (1st and 2nd places)
- Best app for research and university education (1st and 2nd places)
- Best app for tribes and heritage communities (1st and 2nd places)
All apps are eligible for the overall competition. Teams will self-select which track(s) they wish to be considered for for the other three tracks.
- All entries must be checked into GitHub no later than 12:01 AM on September 21, 2014, to be submitted for technical judging.
- All entries will be judged against specific judging criteria.
- All entries must be presented to judges and spectators in the expo round of judging on September 21, 2014 at 10:00 AM. If an entry is not presented during this expo round, it will not be reviewed by the judges, and team members will be ineligible for prizes.
- Presentation order for the 16 finalists will be randomly assigned between 12:30 and 12:40 PM on September 21.
- One or more entries may be selected to be deployed using University resources for a period of 18 months. This may or may not include the winning entry.
- All decisions of the judges are made at the judges’ sole discretion and are final in all matters relating to the HackTheHearst events.