1 / 7

Accountability Project

Accountability Project. Search, Logging and Storage. Overview of the Search Module. KB. Query Log. Business Logic Executor. Search. 1. “ Dani ”. 2. “ Dani ”. “Hotdog”. 3 . “ Dani ”. 5. “Hotdog”. Data Miner. 4. Mine “ Dani ”. 5. Construct. Aintno. Social Graph. Dani.

zaria
Download Presentation

Accountability Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Accountability Project Search, Logging and Storage

  2. Overview of the Search Module KB Query Log Business Logic Executor Search 1. “Dani” 2. “Dani” “Hotdog” 3. “Dani” 5. “Hotdog” Data Miner 4. Mine “Dani” 5. Construct Aintno Social Graph Dani

  3. Components Needed for the Search and Storage • Business Logic Executor (external) - BLE • Data Miner - DM

  4. Assumptions • BLE is a blackbox • KB used for the BLE is transparent • The world only has immutable data (we do not have to worry about data versioning)

  5. Business Logic Executor • Aintno’srules are executed on the facts available in the Aintno’s KB that generates a bunch of keywords related to a particular individual to query the social graph with. • It is up to the BLE to invoke more queries if the results do not satisfy what Aintno was looking for (such as: if the results do not indicate that Dani has anything to do with hot dogs ask the question “Do any of Dani’s friends have pictures of Dani eating hot dogs?”)

  6. Data Miner • Takes in the webid of the person and queries FB for the entire graph • Caches the graph on a local store • Provenance info stored with the data (timestamp of when the data was cached, who’s data it is)

  7. Search Module • Search will take in the webid of an individual and relay it to the DM • Based on what the DM populates in the “social graph” cache, it issues another query that looks for the keyword • Logging information is relayed to the Query Logger • It is reasonable to assume that the BLE will automate their search process through our search interface (there will be a set of keywords to search for that their program will repeatedly call our service) • A sub-component of this module would be the  Query Logger that logs things like: who issued the query, who’s social graph was queried, what time was the query issued, what was the final result of the query • API of the Search Module: • input: webid of a person + keywords to query for • output: search result in a graph?

More Related