1. A Dynamic Approach to Knowledge Capture and Retrieval: Delivering Lessons Learned to NASA Scientists and Engineers Presenter: Swapna Gupta Advisor: Dr. Randy Smith University of Alabama

2. Lessons Learned System

3. Problem Lessons (Knowledge) do not have a definite structure Who defines the structure? –Hard to successfully anticipate and rigidly define final approved agency-wide format –In spite of performing thorough requirements analysis, the structure evolves

4. Lesson Submission: HTML Forms-Limitations Force structure, Limit expressiveness –Information forced into semantically inappropriate fields Weakens search Format evolves, affects other parts of the system –Database schemas, code to store/search/present lessons changes

5. Dynamic Lessons Learned System Lesson Submission –Dynamic Forms Allow users to create their own forms –Pick and choose from a library of elements Allow users to create their own elements –All lessons can vary in format and yet not affect the storage/search/presentation mechanism –Allows construction of ‘static’ forms From Aggregate elements

6. Dynamic Form Interface

7. The Search Interface

8. Status of Current Implementation Make dynamic forms and submit lessons using them Create and use new elements Lessons stored as XML trees in XML repository Lessons are searchable A super schema of elements maintained, to be made available to outside sources like Dublin Core elements

9. Next Steps Working on –Dynamic presentation (Sachin) –A higher interface (Mrinalini) Providing recommended forms as a first step Next steps –An approval process (Curator?) for lessons and elements –A user study –Use element to make a controlled vocabulary of terms with agreed upon meanings Look into ontologies and use them for searches

10. Related Work Form Description Language –Intended to define forms that dynamically adjust depending upon screen space eXtensible Interface Markup Language –Intended for separating user interface specification from display devices Using ontologies marked up with presentation information to generate web forms

11. Questions?

12. Element Type Primitive Type –String –Number –Large Text –Static Text –Choices (one/many) –Choices (many/many) Aggregate Type

13. Element elementName displayName type briefDescription detailedDescription presentationStyle isApproved PrimitiveElement AggregateElement consituents Aggregate Type and Pre-defined Forms PreDefinedForm:AggregateElement elementName=llisForm displayName=LLIS Format Type=Aggregate briefDescription=This format is recommended by LLIS detailedDescription=The format contains… isApproved=true Constituent=Author,Subject,Date… PreDefinedForm:AggregateElement elementName=llisForm displayName=LLIS Format Type=Aggregate briefDescription=This format is recommended by LLIS detailedDescription=The format contains… isApproved=true Constituent=Author,Subject,Date…

14. Incorporating New and Legacy Formats Type Aggregate Let users group together any number of existing elements (primitive and aggregate) Can be used to provide recommended pre-defined forms New Formats – involve creating new aggregate types Old Formats still valid and part of system Addition of new formats does not affect search or rendering of lessons

15. Lesson Search Driven by element library Refined Search Specify search within constituents of aggregate types

16. Implementation XML file stores element library –Drives the Dynamic Form interface –Can drive Search interface Submitted lessons stored as XML files in XML repository –XML Schemas for lessons generated on the fly Retrieval –A search interface, driven by element library –New additions immediately reflected –cross-format search - With each new element XPath query formats generated and saved Presentation –Each element associated with a presentation style –Or whole lesson associated with a presentation style

17. Dynamic Lessons Learned System (DLLS) Dynamic Form Java Servlets Search Interface Mgmt Interface Java Servlets Element Library Drives and Guides Web Browser Element Library Lessons (XML Documents) + Schema New Element XML Repository Approve, Disapprove, Edit, Remove Lessons Approve, Disapprove, Edit, Remove Elements Search and Retrieve Lessons Element Submission Lesson Submission Email

18. Cost Incurred Burden on Approval Process Implementation

19. Future Steps User Interaction Studies Ontologies –Better organization –Better semantics –Guide lesson submission and retrieval Retrieval –Guided Search Approval Process –Lesson Approval –Element Approval

20. - - - - - - - - - -

21. string <![CDATA[The Subject or Title reflects the primary topic of the Lesson Learned. A carefully written Subject should contain some of the Topic(s) that will help other users find this lesson in the future.]]>... Figure 4. Example XML for storing element information