Revision as of 20:20, 8 June 2012

Large Projects

1. Learning algorithm for search result order.
2. Grouping for queries with multiple free query slots. Might conflict with previous item.
3. Classify negative and positive extractions.
4. Create a reduced index by moving some filtering logic from the frontend to the index.
5. Creating an in-link ratio for removing over-linked entities.
6. Adding resolver or other synonym database (e.g., Freebase also-known-as or Google crosswikis)
7. Creating a simple pipeline for adding new data to the demo (e.g. from current news text)
8. Add OLLIE extractions

Small Projects

1. Freebase autocompletion for types and entities, preferably not using old hacky method.
2. Make popovers persistant.
3. Progress bar on query.
4. Better logic for filtering out near subset types.
5. New icon.
6. Remove bad FreeBase types.

Ideas

1. Show all unique sentences if any sentence contains an extraction instance with confidences > threshold. Presently we don't show any sentences with extractions < threshold.

Goals

1. Presentable on the smart phone
2. Queries complete in less than 10 s

Queries

Good

1. (type:Film, based on, true story)
2. (*, symbol of, type:Country)
3. What companies sell which cars?
4. What actors starred in which movies?
5. domesticated in

Spam

1. type:Actor, featured on

Restarting the Web Demo on Reliable

Restarting the Servlet Process

1. Log in to reliable as knowall via SSH
2. Run the command 'screen -ls' and check for a detached screen called 'openie-frontend'. If it is already running:
   1. Switch to it using the command 'screen -r openie-frontend'
   2. Press Control-c to kill any process that might already be running.
3. If the 'openie-frontend' screen was not already running, start a new one with the command 'screen -S openie-frontend'.
4. Run the command 'sbt "start 8088"'. This will start the extraction browser servlet listening on reliable.cs:8088, to which openie.cs forwards requests.
5. If everything works normally, stdout should display a small amount of output ending with the text "STARTING", without any error messages or stack traces. At this point, the Servlet is ready to serve demo requests.
6. Verify that the demo is accessible at http://openie.cs.washington.edu and http://reliable.cs.washington.edu:8088, and check that a few example queries behave correctly. (If only the latter URL works, support should be able to help, refer them to wreq #173026)
7. Detach the screen session by pressing Control-a d.

Updating the source code

1. Kill the existing process
2. 'git pull' or 'git stash', 'git pull', 'git stash pop' if there are changes
3. Start the demo as normal