INTEROP DEMO STEPS

• Basics

  • purpose: basics functionalities of interop prototype
  • self-executable cam shot (old Lotus Camshot)
  • steps
    1. basic multiple DL search: http://128.82.7.86:8088/interop/demo/index.html and launch search interface. Choose libraries and keyword "computer", use view type "original view", and then begin search. Open another browser and go to www.needs.org and search for "computer". Compare results.
    2. DL removal: from demo page click on "remove" DL link, and then remove NEEDS. Go back to search page and NEEDS should not show up.
    3. DL registration: make sure www.cs.odu.edu/~shi/interop/demo/xmldoc/needs_101804.xml is valid, from demo page click on DL "registration" link, register "NEEDS" and the url. Go back to search page and make sure NEEDS shows up.
    4. search registered DL: pick NEEDS and start a new search for "network".
    5. test caching: go to search page, and search for "computer". Results should come up right away as it has been searched. But if start a new search for "computer" with creator "smith", cache miss and have to go to remote DL to get new results.
    6. XML specification tutorial: if you want to learn how to create a XML specs for a DL, you can check the tutorial.
        

• User-centered, Keyword-driven Dynamic Search

  • purpose: demonstrate Interop advanced interactive search service based on keyword-hits information about a DL
  • self-executable cam shot
  • steps
    1. show complete universal search interface based on Dublin Core metadata set (http://128.82.7.86:8088/interop/servlet/dlibServlet?param=init), compare with DC elements
    2. show DL specification include complete search interface description like weight, form type, length, and label. Use NEEDS as sample (http://128.82.7.86:8088/interop/servlet/dlibServlet?formname=info then click on NEEDS). show simulated DL native search interface based on XML spec. Compare that with NEEDS native search interface
    3. show common basic keywords set from Arc log and Arc metadata database ( http://128.82.7.86:8088/interop/demo/selectedHit.html ), threshold use 1, and keyword source using "user access log" and "Arc metadata database".
    4. build real-time keyword-hits database for a DL based on commone keywords set:
       1. open NEEDS search interface, search for "computer", show results page displaying number of hits
       2. show NEEDS XML spec, check DOCHIT part for parsing rules to retrieve hits information
       3. go to Interop build keyword hit page (http://128.82.7.86:8088/interop/servlet/dlibServlet?formname=showkeywordhitpage), input keyword "computer", check "save to db", pick NEEDS and submit
       4. show keywords-hits results from interop database: http://128.82.7.86:8088/interop/demo/selectedHit.html, threshold use 1, and keyword source using "real-time hits".
       5. explain when build realtime keyword hits, if leave keyword blank, will submit all keywords from basic keywords set (in implementation, use the first 1000 keywords from Arc metadata db that has threshold > 200)
    5. show interactive search interface based on input keyword (http://128.82.7.86:8088/interop/demo/initUI.html): input "computer", then "interactive search" and submit, compare hits display with the keywords-hits info from database; compare dynamic interface with DL native interface;
    6. interactive interface generation algorithm: base weight for each UI field (based on 100, keyword 100, author 80, ...); plus weights from keyword hits (even for the same DL, also give weights: like in IEEE, keyword author weight is 1, but collection may only 0.5); plus weights from user selection (from log, for those fields that user picked, not implemented yet)

       •     int weight_author = 80;

       •     int weight_subject = 50;

       •     int weight_keyword = 100; 

       •     int weight_archive = 30;

       •     int weight_hits = 80;

       •     double factor_UI = 0.3;

       •     double factor_hits = 0.7;  //overallweight = weightUI * factorUI + weightHits * factorHits

       •     int threshhold = 10;       //if overall weight > threshhold, show in interface

    7. field display threshold can be change dynamically, see results
       • check info page for current UI_threshold setting, change it to 10 by http://128.82.7.86:8088/interop/servlet/dlibServlet?UI_threshold=10, repeat step 5, notice "date" field has been removed; so if search "network security" published in 2002, will not filter enough using date (which is used by LTRS)
       • (old dummy results) sample query: all about "network security" published in 2002
         • threshold = 5: result interface (updated 062102)
         • threshold = 10: result ("Date" field not showing up, used by LTRS)
         • query directly against LTRS: result
    8. additional user customization: http://128.82.7.86:8088/interop/demo/UI/UI_interactive_select.htm

• Results Parsing, Presentation and Automatic Metadata Retrieval

  • purpose: demonstrate parsing metadata from DL results page; display parsed results to users in consistent way
  • self-executable cam shot
  • steps
    1. available metadata from sample DL: search NEEDS for "computer", check displayed metadata from both result page and record page, check html source for display pattern.
    2. show interop DTD and NEEDS XML spec, check result page and record page metadata parsing rules definition.
    3. go to interop search page and search for "computer", compare results with NEEDS result from both result and record page
    4. go to CogPrints search page and search for "computer", notice that results page has not much metadata but detail page has rich information. Back to the interop search results page for "computer" and compare.
    5. results presentation: go to search interface and search for "keyword=computer&title=computer&boolean=all", check "group by creator" and "group by DL"

• Local Repository and Intelligent Cache

  • purpose: demonstrate intelligent cache based on local metadata repository retrieved from DLs
  • self-executable cam shot
  • steps
    1. local repository design: http://www.cs.odu.edu/~shi/interop/demo/doc/tabledef.sql
       • table design: http://www.cs.odu.edu/~shi/interop/demo/doc/tabledef.sql
       • sample data: http://www.cs.odu.edu/~shi/interop/demo/doc/dissertation/demo/metadata_db_screenshot.html
       • procedure to save metadata to repository: http://www.cs.odu.edu/~shi/interop/demo/doc/procedure.sql
    2. local repository search
       • go to search page, search for "computer", check search results
       • sql query transferred from html query: check log file, should have something like "WHERE UPPER(archive) IN ('COGPRINTS', 'CSTC', 'IEEE', 'LTRS', 'NACA', 'NEEDS', 'ACM', 'WCR' ) AND ((UPPER(KEYWORD) LIKE '%COMPUTER%' OR UPPER(TITLE) LIKE '%COMPUTER%' OR UPPER(DESCRIPTION) LIKE '%COMPUTER%') )"
    3. metadata cache
       • in-memory cache: http://128.82.7.86:8088/interop/servlet/dlibServlet?formname=showallmetadata
       • manual save to repository: click on savetodb, show all metadata (all pink metadata should be blue means all metadata are from local database instead of from remote DL)
       • automatic save to db: every 60 min
    4. cache replacement algorithm
       • go to info page verify cache size and keep safe size, and check metadata in cache http://128.82.7.86:8088/interop/servlet/dlibServlet?formname=showallmetadata
       • change cache size to 10 by http://128.82.7.86:8088/interop/servlet/dlibServlet?maxmetadatainmemory=10, and cache keep safe size to 8 (so remove least used one from the two oldest ones) by http://128.82.7.86:8088/interop/servlet/dlibServlet?metadatainmemorykeepsafe=8, verify metadata in cache http://128.82.7.86:8088/interop/servlet/dlibServlet?formname=showallmetadata
       • search CogPrints limit results 5, verify metadata in cache
         search NEEDS limit results 5, verify metadata in cache
         change cache keep safe size to 9, search CogPrints limit 1, now should always remove oldest from cachein-memory cache: http://128.82.7.86:8088/interop/servlet/dlibServlet?formname=showallmetadata
    5. cache implementation details: http://www.cs.odu.edu/~shi/interop/demo/doc/caching_implementation.html

     

• InterOp System Management

  • purpose: demonstrate system maintenance and management of Interop
  • self-executable cam shot
  • steps
    1. go to http://128.82.7.76:8088/interop/demo/index.html and then click on "Search Engine and Site Management", try each link