NASA Search Portal Bug Fixes Contest - Part 2

Welcome to NASA Search Portal - Bug Fixes Contest. As part of this contest, you will fix the issues raised earlier as part of a Bug Hunt Contest.

You no longer have to install Solr or any other database. We have already hosted the database and the recommendation engine and have configured the application to use the endpoints to interact with them. As part of deployment, you only need to install a nodejs application. This should be simple enough.

Project Overview

NASA needs your help building an enterprise search portal. NASA & Topcoder have completed the design and frontend code for a search interface that is intuitive for beginner to advanced users which allows users to search against NASA intranet as well as public internet data sets.

As part of this project, we are integrating the search engine (Solr Cloud) which will serve as a backend to the Enterprise Search User Interface and seek to expand the capabilities of the existing application.

Contest Overview

We ran a Bug Hunt contest earlier where lots of bugs were raised. As part of this contest you will have to fix the issues reported in them. Only 22 issues are in scope.

You will find all details on how to reproduce the issue, the browser the issue was reproduced in, the current behaviour vs the expected behaviour in the tickets itself. You can ask questions for specific tickets in the ticket itself.

Final Submission Guidelines

1. Submit only the Source Code folder. You can submit only the changes via a git patch or submit all the code. Upload your submission through the Submit and Review tool for this contest.

2. DO NOT update the Deployment Guide (unless a ticket’s fix is changes to the DG itself). Instead kindly make sure that for each issue, you have carried out the following:

   1. Fix the issue

   2. Commit the changes specific to that issue. You can set the ticket # in the commit message. For example, a fix for ticket #22 will have the commit message ‘Fix for #22 - Add a maxlength attribute to the exclude word and exclude domain filter’.

   3. You will make the reviewers life easier with the above approach. They will know precisely what changes were carried out for which issues since each change will be associated with a commit / ticket.
3. You do not have to provide any video for this contest
4. You do not have to update the Verification Steps in the Deployment Guide
5. DO NOT create any Pull Requests. You are fixing all issues in scope. See point 1 above. Only winner will be asked to create Pull Request.