DOC PREVIEW
Rutgers University CS 336 - Principles of Information and Database Management

This preview shows page 1-2-20-21 out of 21 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 21 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 21 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 21 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 21 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 21 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

1Principles of Information and Database Management198:336Week 10 – Apr 11Matthew StoneProject UpdateWhere you should beWhat to do nextTimeline for the rest of the semester2Designing an applicationExample I’ve been working on– Run survey experiment over the webBackgroundStudying face-to-face communication– We want to design animated characters that signal relationships and emotion like people– We need to know what signals people use– We need to know how to animate those signals3MethodologyFour steps– Collect and analyze recordings of people talking in conversation– Ask other people what speakers seem to be doing – find reliable signals– Develop a data format for specifying those signals in animation – XML! – Ask about what animated characters seem to be doing – make sure signals are reliableWeb interface for step 2Need an interface to – Set subjects up for the experiment– Show subjects data and collect their judgments– View individual responses– Analyze overall results for experiment4More SpecificallyMap of pages in the interfaceStart pageNew subjectView resultsSessionInstructionsPlay clipGet judgmentFinish sessionSet up nextSearch: itemor subjectGet overviewJudgments of itemJudgments of subjectOverall resultsWhat this doesOrganizes the code you have to write– Each interface state corresponds to a page– Have to write code for each page• In Java, one servlet class per page• Perhaps share low-level classes across pagesHighlights need for state in interface5Aside: State and the WebHTTP has no state– New connection for each request– Browser sends all available information as part of the request– Through parameters: get/post form inputs– Through cookies: special attribute-value pairsAside: State and the WebYou have to be explicit about state– Build suitable HTML on the fly– Include “hidden inputs”<input type=“hidden” name=“x” value=“y” />– Specify actions in forms based on context– If you’re fancy, set cookies and get cookies6Map and StateHere, you need to keep track of key info:– User, Session type, Item list, Current item– E.G. through hidden inputsSessionInstructionsPlay clipGet judgmentFinish sessionSet up nextFleshing out designSpell out how pages interact with DB– To take updates from last response – To satisfy request– To create page7More SpecificallyStart pageNew subjectView resultsSessionInstructionsPlay clipGet judgmentFinish sessionSet up nextSearch: itemor subjectGet overviewJudgments of itemJudgments of subjectOverall resultsStart screenStart pageNew subjectView results8Start screenNothing has been inputNo queries needed to make the pageInstructionsSessionInstructions9InstructionsIf “New Subject” action has just happened– Must create a new ID for current subjectTo create the page– Must access the next protocol for this subject– Update the DB to store this subject & protocol– Save the ID & protocol & start info in the state– Must get and display protocol instructionsPlay clip, get judgmentPlay clipGet judgment10Play clip, get judgmentIf just got a judgment– Insert new entry,based on user, session, protocol, clip, valueGet the next judgment– Based on session and protocol– Format page to play appropriate media– Set up action to do based on what’s leftFinish up sessionFinish sessionSet up next11Finish up sessionIf just got a judgment– Insert new entry,based on user, session, protocol, clip, value– Better reuse this code from clip page!Determine what’s next– If there’s another session, get ready to start– Otherwise thanks for playing!Experimenter’s Search InterfaceSearch: itemor subjectGet overview12Experimenter’s search interfaceAlways the same page– Menus for kind of search– Text field for search key– Action for overview results pageItem JudgmentJudgments of item13Item judgmentGet results from database– Based on search of judgments on this itemFormat results as a tableSubject JudgmentsJudgments of subject14Overall resultsOverall resultsOverall resultsGet and display results– Find conditions for experiment– Select out the averages– Display the results as a table(or graph, perhaps with error bars)15So there you have itMap of pages in the interfaceStart pageNew subjectView resultsSessionInstructionsPlay clipGet judgmentFinish sessionSet up nextSearch: itemor subjectGet overviewJudgments of itemJudgments of subjectOverall resultsReally one third of the project!Now you know exactly what DB stores– Description of experimentprotocolsconditions– Descriptions of items– Judgments from subjects about items in conditions16Really one third of the project!Now you know how to break up pages– Know forms, links, queries you need– Know what code can be shared across pages– Know special structure on each pageNote on key featuresA little of everything– Updates as well as selects.– More than one kind of user.– Active links as well as forms.Put yourself in your users’ shoes– Make something that fits them, their task17Next StepAnyone can revise by Thursday 6pm.Then, DB and SQL overview by recitation Wed 20.DB and SQLHow will you store information?– Relational schema for your stuffHow will you query it?– For each page, what are the SQL commands– Use ? notation for prepared statements– Indicate how each of the ?s get values18What you should expect to doWork from detailed map of your applicationWrite out the schema and queries on paperCreate the schemas in a real db– E.G. oracleTry out the queries with examples– Make sure the results are what you expect– If not, debug your queries!What you should expectBy the time you hand this inyour project should be two thirds done!19Information RetrievalText as data– legal decisions– scholarly articles– web pages!Information retrievalRelevance ranked query– user specifies query termswords that are likely to occur in a document that they are interested in– dbms returns an ordered list of documentsdocuments higher in the list should match the query more closely than documents lower down20Vector space modelText database with four records:1 agent James Bond good agent2 agent mobile computer3 James Madison movie4 James Bond movieJust keep track of words that occurVector space modelNew table: document agent bond computer James …121012 1 0 1 03 0 0 0 14 0 1 0 121Dot


View Full Document

Rutgers University CS 336 - Principles of Information and Database Management

Download Principles of Information and Database Management
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Principles of Information and Database Management and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Principles of Information and Database Management 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?