.
FRDCSA | internal codebases | Seeker

Seeker Architecture Diagram: GIF

Jump to: Project Description | Capabilities

Project Description

Capabilities

• Search (for seeker) often uses specialized searches.
• Setup a general troubleshooting assistant (that uses seeker to launch web searches for given problems, and breaks things down into steps that can be solved by annotated web searches, etc.)
• Come up with a better quanitifcation of the various modes of getting software. Develop seeker to its full potential.
• brainleach should integrate with seeker in order to systematically handle links. seeker could benefit from the same HTN system.
• queue AppConfig in study, need to get a sort of process model for these systems, so that they can store the various things they need to. for instance, the data model for seeker would include the status of the search.
• Pipe cso searches through seeker
• (write system to browse fravia (seeker itself should do that))
• Maybe seeker should actually handle requests for software, and utilize cso, radar, etc.
• seeker can even help us find things on our own computer.
• seeker might eventually make use of web intelligence (measure popularity of various things), and web information extraction technologies, query planning (like Fetch technologies Ariadne...)
• seeker should make use of the linkranker software
• seeker should definitely determine how heavily to stress certain channels.
• seeker obviously incorporates some of critics abilities to remember what the user has already seen. In fact, that part of fweb that records sentences could be generalized to serve as the backend for clear, seeker, critic and fweb.
• Index frustrating searches. Store all previous searches in seeker.
• Should sanctus handle seeker functionality?