Abstract:
Embodiments of the invention provide a system and methods for producing and retrieving video with story-based content. Embodiments of the invention use an interview process to capture a contributor&#39;s knowledge in the form of a narrative or story. An enabling feature of such embodiments is that one or more predetermined questions are associated with each predetermined story topic. Embodiments of the invention also provide a mechanism for appending a story with insight from one or more other vantage points (personal perspectives) as part of the knowledge capture process. In embodiments of the invention, the story/question relationship may be used to classify KM records. Metadata associated with the story and/or the contributor may also be used for the automatic classification and retrieval of such records.

Description:
BACKGROUND AND SUMMARY 
       [0001]    1. Field of the Invention 
         [0002]    The invention relates generally to video production and/or the selective retrieval of video, and more particularly, but without limitation, to a system and methods for producing and retrieving video with story-based content. 
         [0003]    2. Description of the Related Art 
         [0004]    The field of knowledge management (KM) relates generally to the capture, storage, and retrieval of knowledge. Typically, KM is an effort to share such knowledge within an organization to improve overall operational performance. KM can also be used to share historical knowledge more broadly, or to facilitate a collaborative development environment (i.e., to expand knowledge). 
         [0005]    Various KM systems and methods are known. For example, knowledge databases, libraries, or other repositories have been established so that articles, user manuals, books, or other records can be classified and stored. The records can then be selectively retrieved based on the classification. 
         [0006]    Known KM schemes have many disadvantages, however. For instance, the capture (or creation) of knowledge may be performed on an ad hoc basis, rather than in response to known organizational needs. Furthermore, the capture process may not effectively extract the tacit (subconscious or internalized) knowledge of the domain expert or other contributor. For these and other reasons, the amount, percentage, or degree of useful records in the KM repository may be lacking. 
         [0007]    In addition, known processes for classifying records often rely on manual intervention to assign subject-based classifications. Such manual intervention may delay knowledge sharing and/or increase the costs associated with a KM initiative. Another disadvantage is that retrieval processes that rely on subject-based classifications in response to search queries may be ineffective due to an inherent lack of context. Moreover, it may be difficult for a user to efficiently identify and review the relevant portion(s) of records that are responsive to a search query of the KM repository. 
         [0008]    For at least the foregoing reasons, improved systems and methods are needed to support the capture and retrieval processes associated with a KM process. 
       SUMMARY OF THE INVENTION 
       [0009]    Embodiments of the invention seek to overcome one or more of the shortcomings described above. Embodiments of the invention use an interview process to capture a contributor&#39;s knowledge in the form of a video-based narrative or story. An enabling feature of such embodiments is that one or more predetermined questions are associated with each predetermined story topic are presented to a storyteller during production of the video. Embodiments of the invention also provide a mechanism for appending a video story with insight from one or more other vantage points (personal perspectives) as part of the knowledge capture process. 
         [0010]    In embodiments of the invention, the story/question relationship may be used to classify KM records. Metadata associated with the story and/or the contributor may also be used for the automatic classification and retrieval of such records. Moreover, in embodiments of the invention, the retrieval process includes a method for sequencing a stream of responsive video records for presentation to a knowledge recipient. 
         [0011]    An embodiment of the invention provides a method for capturing a video file. The method includes: displaying a story topic menu; receiving a story topic selection; displaying a question menu based on the story topic selection; receiving at least one question selection; and video recording a response to the at least one question selection. 
         [0012]    Another embodiment of the invention provides a method for retrieving a video file. The method includes: identifying at least one video file in an archive; receiving a desired run time; ranking the at least one video file into a video playlist; truncating the video playlist based on the desired run time to produce a truncated video playlist; and sequentially streaming video content associated with the truncated playlist to a user. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0013]    The present invention will be more fully understood from the detailed description below and the accompanying drawings, wherein: 
           [0014]      FIG. 1A  is a flow diagram of a video-based story capture process, according to an embodiment of the invention; 
           [0015]      FIG. 1B  is a flow diagram of a video-based story capture process, according to an embodiment of the invention; 
           [0016]      FIG. 2  is an illustration of a graphical user interface, according to an embodiment of the invention; 
           [0017]      FIG. 3  is an illustration a graphical user interface, according to an embodiment of the invention; 
           [0018]      FIG. 4  is an illustration of a graphical user interface, according to an embodiment of the invention; 
           [0019]      FIG. 5  is an illustration of a graphical user interface, according to an embodiment of the invention; 
           [0020]      FIG. 6  is a flow diagram of a video-based story capture process, according to an embodiment of the invention; 
           [0021]      FIG. 7  is a flow diagram of a process for associating metadata with a video story, according to an embodiment of the invention; 
           [0022]      FIG. 8  is a flow diagram of a story retrieval process, according to an embodiment of the invention; 
           [0023]      FIG. 9  is an illustration of a graphical user interface screen, according to an embodiment of the invention; 
           [0024]      FIG. 10  is an illustration of a graphical user interface, according to an embodiment of the invention; 
           [0025]      FIG. 11  is an illustration of a graphical user interface, according to an embodiment of the invention; 
           [0026]      FIG. 12A  is an illustration of a graphical user interface, according to an embodiment of the invention; 
           [0027]      FIG. 12B  is an illustration of a graphical user interface, according to an embodiment of the invention; 
           [0028]      FIG. 13  is a flow diagram of a story retrieval process, according to an embodiment of the invention; 
           [0029]      FIGS. 14A and 14B  are a flow diagram of a story retrieval process, according to an embodiment of the invention; and 
           [0030]      FIG. 15  is a functional architecture of a KM system, according to an embodiment of the invention. 
       
    
    
     DETAILED DESCRIPTION 
       [0031]    Embodiments of the invention will now be described more fully with reference to  FIGS. 1 through 15 , in which embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In the drawings, reference designators may be duplicated for the same or similar features. 
       Story Capture Process 
       [0032]    One necessary feature of KM is capturing or otherwise creating knowledge from domain experts or other sources. 
         [0033]    Historically, storytelling has been used to entertain and/or to distribute knowledge. Unfortunately, storytelling, whether in writing or in person, is typically in the form of a narrative (e.g., a description of a series of events). Moreover, the narrative is not always fully captured by the recipient for later recall and use. In embodiments of the invention, a storyteller selects a story topic, and then is presented with one or more predetermined questions that are associated with the selected story topic. The storyteller&#39;s responses may therefore be a personal experience narrative that is somewhat directed by the question(s) presented. In addition, in embodiments of the invention the storyteller&#39;s responses may be video recorded for later use. Embodiments of the invention also capture alternative vantage points on the story in video format. In embodiments of the invention quantitative information from a storyteller and/or vantage point contributor may also be captured to supplement the video story. 
         [0034]    Such a capture process has many benefits. For instance, the predetermined questions may be crafted to satisfy organizational objectives. One such objective may be, for instance, to capture knowledge that will be strategically useful to the organization. Another objective might be to encourage the storyteller to reveal tacit knowledge, or even knowledge that might be perceived as unfavorable to the storyteller. Where they exist, the alternative vantage points associated with a video story may provide a richer transfer of knowledge concerning the same events. Story capture processes are described in more detail with reference to  FIGS. 1-7  below. 
         [0035]      FIG. 1A  is a flow diagram of a video-based story capture process, according to an embodiment of the invention. As shown therein, the process begins in step  105 . A user logs into a system in step  110 , which may include, for example, entering a login identifier (ID) and password. The user then selects a story generation function in step  115 . Step  115  may be distinguished, for instance from the selection of a story retrieval function. In step  120 , a user receives and responds to speech training prompts. Such training may later be useful for extracting keywords or other information from the story content. In step  125 , a user selects a story topic, for instance from a menu of possible story topics. The user then selects at least one question that is associated with the selected story topic in step  130 . Next, in step  135 , the user responds to a first or next question. An embodiment of step  135  is also described below with reference to  FIG. 1B . Then, in conditional step  140 , a user determines whether to answer another question. Where the result of conditional step  140  is in the affirmative, the user may return to step  135 . Otherwise, the user may click on a response to a question about the selected story topic in step  145 . 
         [0036]    For example, in step  145 , a user could receive a question such as “Do you consider yourself an expert in this subject area?” or “May interested parties contact you directly to discuss your video story?” and the user could respond to such questions by clicking on a “yes” button or a “no” button on a graphical user interface (GUI). Other types of quantitative information could also be collected from the user in step  145  to supplement the user&#39;s recorded video story. 
         [0037]    The user may receive and select publication options for the story in step  155 . As used herein, publication refers to posting a video story on a website (e.g., You Tube, My Space, or other personal blog), sending the video story to one or more email addressees, and/or saving the video to a local or remote data store. A user may send one or more invitations for vantage point comments in step  160 . Vantage point comments refer to video comments and/or quantitative information provided by other actors in the user&#39;s video story. In conditional step  165 , a user considers whether to record another video story. Where the user decides to do so, the process returns to step  125 ; otherwise the process terminates in step  170 . 
         [0038]    Variations to the process illustrated in  FIG. 1A  are possible. For example, step  115  may be implicit, where other options do not exist. In addition, in alternative embodiments, steps  120 ,  140 ,  145 ,  150 ,  155 ,  160  and/or  165  may be omitted, according to design choice. 
         [0039]      FIG. 1B  is a flow diagram of a video-based story capture process, according to an embodiment of the invention.  FIG. 1B  is a more detailed embodiment of step  135  discussed above. As illustrated in  FIG. 1B , the process begins by providing quantitative information about the first or next question. Such quantitative information could be provided, for instance, in response to a “yes” or “no” question. Such information could also be provided on a Likert or other psychometric response scale. Preferably, step  175  includes clicking on a button, box, or other GUI feature that facilitates its collection. An example of such a GUI feature is described below with reference to  FIG. 4 . 
         [0040]    In step  180 , the user records a video story response to the first or next question. In embodiments of the invention, step  180  includes using a camera, microphone, and media application to produce a video recording. Then, in step  185 , the user may associate one or more digital images and/or audio files with the user&#39;s question response. Step  185  could include, for instance, uploading a digital photograph that is related to the user&#39;s response to the first or next question. 
         [0041]      FIG. 2  is an illustration of a graphical user interface (GUI), according to an embodiment of the invention. As illustrated in  FIG. 2 , a GUI  205  includes a login portion  210 . The login portion  210  may include, for example, data fields for login ID, password, and/or an acknowledgement of terms and conditions. The GUI  205  may be used in the execution of login step  110 . 
         [0042]      FIG. 3  is an illustration a graphical user interface, according to an embodiment of the invention. As shown therein, a GUI  305  includes a story selection portion  310  and a media portion  315 . In embodiments of the invention, the story selection portion  310  may be used, for example, for a user to execute step  115 . The media portion  315  may be used by a user to upload, for example, photos and/or audio files associated with the selected story as discussed above with reference to step  185 . 
         [0043]      FIG. 4  is an illustration of a graphical user interface, according to an embodiment of the invention. As shown therein, a GUI  405  includes a video display portion  410 , a control portion  415 , a publication portion  420 , and a quantitative information input portion  425 . A user may use the GUI  405  in responding to a first or next question in step  135 . For example, a user may record, play, pause, or perform other viewing and/or editing functions using the control portion  415 . A user may view portions of the video in the video display portion  410 . Before, during, or after recording a response to the first or next question, the user may provide quantitative information using the quantitative information input portion  425 . Upon completion of the recording, a user may publish the recorded video story using the publication portion  420 , in accordance with publication step  155 . 
         [0044]      FIG. 5  is an illustration of a graphical user interface, according to an embodiment of the invention. As shown therein, a GUI  505  includes an electronic mail (email) listing portion  510  and an invitation button  515 . During the execution of invitation step  155 , a user may enter one or more email addresses into the email listing portion  510  and select the invitation button  515  to invite comment from friends, colleagues, or other persons having a vantage point associated with the primary contributor&#39;s recorded video story. 
         [0045]    The processes illustrated in  FIGS. 6 and 7  are presented from the perspective of a process embodied in a KM system. 
         [0046]      FIG. 6  is a flow diagram of a video-based story capture process, according to an embodiment of the invention. After beginning in step  605 , the process authorizes a storyteller in step  610 . Authorization step  610  may include, for instance, presenting GUI  205  to the storyteller, receiving information that the storyteller enters into the login portion  210 , and verifying the login ID and password based on stored user account data. Then, in step  615 , the process may receive the storyteller&#39;s selection for story generation. The process outputs speech training prompts to the storyteller and receives responses to the speech training prompts in step  620 . Such speech training prompts may require the storyteller, for instance, to speak one or more predetermined words into a microphone. The process may display a story topic menu to the storyteller, for example using GUI  305 , in step  625  and receive a story topic selection from the storyteller in step  630 . In step  635 , the process displays a question menu based on the storyteller&#39;s story topic selection. In step  640 , the process receives one or more question selections from the user. Then, in step  645 , the process receives and records a video response to a first or next question, for instance using GUI  405 . Optionally, step  645  could include receiving quantitative information from the storyteller using a GUI feature such as the quantitative information input portion  425  illustrated in  FIG. 4 . Step  645  may also include receiving or otherwise associating digital images, audio files, or other non-video content with the user&#39;s story. In step  650 , the process associates metadata with the recorded response. An embodiment of step  650  is described in more detail below with reference to  FIG. 7 . 
         [0047]    In conditional step  655 , the process determines whether to present the storyteller with another question associated with the selected story topic. The operation of step  655  could be controlled by the system or could be based on the storyteller&#39;s input. Where the result of conditional step  655  is answered in the affirmative, the process returns to step  645 . Otherwise, the process advances to step  660  to display a publication menu to the storyteller. In step  665 , the process receives the storyteller&#39;s publication selection and publishes the recorded story based on the publication selection. The process displays a vantage point invitation prompt in step  670  and then receives invitation data and executes vantage point invitations in step  680 . Step  670  may include, for example, presenting GUI  505  to the storyteller. The invitation data could be or include, for instance, one or more email addresses. In conditional step  680 , a storyteller is presented with the option of recording another video story. Where the storyteller wishes to do so, the process returns to step  625 ; otherwise, the process terminates in step  685 . 
         [0048]    Variations to the process illustrated in  FIG. 6  are possible. For example, step  615  may be implicit, where other options do not exist. In addition, in alternative embodiments, steps  620 ,  650 ,  655 ,  660 ,  665 ,  670 ,  675  and/or  680  may be omitted, according to design choice. 
         [0049]      FIG. 7  is a flow diagram of a process for associating metadata with a video story, according to an embodiment of the invention. The process illustrated in  FIG. 7  is a more detailed illustration for an embodiment of process step  650 . As shown in  FIG. 7 , the process begins in step  705 , and then identifies a first group of metadata in step  710  based on the story topic and the selected question. 
         [0050]    In step  715 , the process performs speech-to-text conversion based on an audio portion of the recorded video. In step  720 , the process identifies significant terms in the text based on the speech-to-text conversion. Step  720  may be, for example, rule-based and/or index-based. A rule-based identification could be or include, for instance, determining the frequency of each word used in the video. Index-based identification could be or include comparing each word used in the video to a predetermined index of significant terms. In step  725 , the process identifies a second group of metadata based on the significant terms that were identified in step  720 . 
         [0051]    In step  730 , the process may identify a third group of metadata based on origination data. Origination data may be, for example, based on user account data such as a user&#39;s sex or age. Moreover, origination data may include, for instance, the date or time that a story was recorded, or the date or time that events described in the story took place. 
         [0052]    In step  735 , the process identifies a fourth group of metadata based on quantitative information. Such quantitative information may be based, for instance, on the storyteller&#39;s interaction with the quantitative information input portion  425  of GUI  405  in the execution of step  645 . 
         [0053]    In step  740 , the process associates the first, second, third, and/or fourth groups of metadata with the recorded video story. The process terminates in step  745 . From the description of step  740  it should be clear that steps  710 ,  715 ,  720 ,  725 ,  730  and/or  735  are optional. 
         [0054]    A vantage point contributor may use processes and GUIs that are similar to those discussed above with reference to  FIGS. 1A through 5 . In addition, a KM system may use processes similar to those discussed above with reference to  FIGS. 6 and 7  to capture vantage point contributions. 
         [0055]    In embodiments of the invention, metadata that is associated with a recorded video story in step  650  may be used in a story retrieval process. 
       Story Retrieval Process 
       [0056]      FIG. 8  is a flow diagram of a story retrieval process, according to an embodiment of the invention. As illustrated therein, the process begins in step  805  and a user may login in step  810 . In step  815 , a user selects a story retrieval function. A user may then select a template search in step  820  and receive a story topic menu in step  825  based on the selected template search. As used herein, a template refers to a predetermined association between each story topic and one or more questions relating to the story topic. Accordingly, a user selects a story topic from the story topic menu in step  830  and then receives a question menu based on the selected story topic in step  835 . In step  840 , a user selects at least one question from the question menu. A user then selects a desired run time in step  845  and requests a responsive video stream in step  850 . 
         [0057]    In step  855 , a user receives a video stream based on the selected at least one question and the desired run time. The video stream received in step  855  may be or include, for instance, video clips associated with each of multiple storytellers in response to the selected story topic and question(s). Step  855  may also include viewing quantitative information received from storytellers and/or vantage point contributors. Step  855  may also include scoring by the user of the retrieval process; for instance a viewer may score one or more retrieved videos based on the utility of such video(s) to the viewer. The process terminates in step  860 . 
         [0058]    Variations to the process illustrated in  FIG. 8  are possible. For instance, step  815  may be implicit where other options do not exist. In addition, step  845  may be omitted, according to design choice. Moreover, step  855  may include receiving one or more video files rather than a video stream. 
         [0059]      FIGS. 9-12  are graphical user interfaces (GUI&#39;s) that may be used in executing story retrieval processes. 
         [0060]      FIG. 9  is an illustration of a graphical user interface, according to an embodiment of the invention. As shown therein, a GUI  905  includes a story menu  910 , a keyword portion  915 , and a login portion  920 . GUI  905  may be used, for example, during steps  810  and  830  described above with reference to  FIG. 8 . 
         [0061]      FIG. 10  is an illustration of a graphical user interface, according to an embodiment of the invention. As shown therein, a GUI  1005  includes a question portion  1010 , a perspective portion  1015 , and a duration portion  1020 . The GUI  1005  may be used, for example, in selecting at least one question from the question menu as described above with reference to step  840 . In particular, the question portion  1010  illustrates that a user may select one or more questions during the retrieval process. In the embodiments illustrated in  FIGS. 9 and 10 , the questions listed in question portion  1010  are associated with the “Tour of Duty” user selection in story menu  910 . A different story topic selection would result in a different set of questions. The perspective portion  1015  illustrates that a knowledge consumer may request video in step  850  from the story of an originator (or originators) and/or one or more invited vantage point contributors. The duration portion  1020  may be used in executing step  845 . 
         [0062]      FIG. 11  is an illustration of a graphical user interface, according to an embodiment of the invention. As shown therein, a GUI  1105  may include a vantage point menu  1110 . The vantage point menu  1110  may be used, for example, to further refine a request for video in step  850 . 
         [0063]      FIG. 12  is an illustration of a graphical user interface, according to an embodiment of the invention. As shown therein, a GUI  1205  includes a video display portion  1210 , control buttons  1215 , a publication button  1220 , and a quantitative information display portion  1230 . The video display portion  1210  may further include a question overlay portion  1225 . 
         [0064]    During execution of step  855 , a user may view a stream of video in the video display portion  1210  and control such stream using the control buttons  1215 . Preferably, during review of the video stream, a user may see text associated with the video stream in the question overlay portion  1225 . For example, as illustrated in  FIGS. 10 and 12 , where a user has selected the question “did you experience fear?” in question portion  1010 , a user may observe that same question displayed in the question overlay portion  1225  during receipt of the responsive video stream. Publication button  1220  allows a user to publish the retrieved video stream. The quantitative information display portion  1230  allows a user of the retrieval process to view quantitative information that has been previously collected from an originator (storyteller) and/or vantage point contributors. 
         [0065]      FIG. 12B  is an illustration of a graphical user interface (GUI)  1235 , according to an embodiment of the invention. GUI  1235  is identical to GUI  1205 , except that GUI  1235  includes a scoring portion  1240  rather than a quantitative information display portion  1230 . The scoring portion  1240  is configured to solicit and collect feedback from a user of the retrieval process. In the illustrated embodiment, such feedback is related to the utility of the retrieved video story(ies). In an embodiment of the invention, a user may individually score each of multiple videos included in a retrieved video stream using the scoring portion  1240 . Alternative embodiments of the invention could combine the features of GUIs  1205  and  1235 , according to design choice. 
         [0066]      FIG. 13  is a flow diagram of a story retrieval process, according to an embodiment of the invention. The process begins in step  1305 , and a user may login to a KM system in step  1310 . In step  1315 , a user selects a story retrieval process. Next, a user may select a keyword search function in step  1320  and enter at least one keyword in step  1325 . In step  1330 , a user selects a desired run time. A user may then request a responsive video stream in step  1335 . Step  1335  could include specifying whether the knowledge recipient wishes to receive only responsive video stories from primary contributors (originators), or whether the knowledge recipient would like to also receive video clips from vantage point contributors instead of, or in addition to, those of the primary contributors. Where step  1335  includes a request for responsive video clips from vantage point contributors, step  1335  may include a menu for the selection of one or more vantage point contributors. A user receives the video stream based on the selected at least one keyword and the desired run time in step  1340 , and the process terminates in step  1345 . Step  1340  may include viewing quantitative information received from storytellers and/or vantage point contributors. Step  1340  may also include scoring by the user of the retrieval process; for instance a viewer may score one or more retrieved videos based on the perceived utility of such video(s) to the viewer. 
         [0067]    A user may use GUI  905  while performing portions of the process illustrated in  FIG. 13 . For example, a user may use the login portion  920  to execute step  1310 , and a user may use the keyword portion  915  to execute steps  1320  and/or  1325 . Furthermore, a user may use GUIs  1205  and/or  1235  to perform step  1340 . 
         [0068]    Variations to the process illustrated in  FIG. 13  are possible. For instance, steps  1310  and  1330  may be omitted, according to design choice. In addition, step  1315  may be omitted where the story retrieval function is inherent. Moreover, step  1340  could include receiving one or more video files instead of a video stream. 
         [0069]      FIGS. 14A and 14B  are a flow diagram of a story retrieval process, according to an embodiment of the invention.  FIGS. 14A and 14B  are from the perspective of a process embodied in a KM system. The process illustrated in  FIG. 14B  is a continuation of the process illustrated in  FIG. 14A . A user of the video story retrieval process may also be referred to herein as a viewer. 
         [0070]    As illustrated in  FIGS. 14A and 14B , the process may begin in step  1400  and then authorize a user in step  1405 . Step  1410  may include, for instance, receiving a login ID and password from a user, and comparing same to stored user account data. In step  1410 , the process receives a story retrieval command from a user. The process receives a search command from a user in step  1415  and determines a type of search being requested in conditional step  1420 . 
         [0071]    The illustrated KM system process may utilize GUI  905  in executing steps  1405  and  1495 . 
         [0072]    Where the type of search being requested is a template search (e.g., one based on a predetermined association between story topics and questions), the process advances to step  1425  to display a story topic menu. In step  1430 , the process receives a story topic selection from a user. The process then displays a question menu to a user in step  1435  based on the story topic selection. In step  1440 , the process receives at least one question selection from a user and then identifies at least one video in an archive based upon the question selection in step  1445 . 
         [0073]    The illustrated KM system process may utilize GUI  905  in executing step  1425  and may further use GUI  1005  to execute steps  1435  and  1440 . The KM system may use metadata identified in step  710  to execute step  1445 . 
         [0074]    Where the result of conditional step  1420  indicates a keyword search, the process receives at least one keyword in step  1450 . The KM system may use GUI  905  to execute step  1450 . Then, in step  1455 , the process identifies at least one video in an archive based on the at least one keyword. The KM system may execute step  1455 , for instance, by comparing the received at least one keyword to the first, second, and/or third group of metadata identified in the process described above with reference to  FIG. 7 . 
         [0075]    Upon the conclusion of either step  1445  or step  1455 , the process prepares a video playlist in step  1460  that is based on the at least one video. Optionally, step  1460  could include ranking or otherwise ordering each of the videos in the playlist, for example by relevance, chronology, or other criteria. 
         [0076]    The video playlist may be reduced in cull step  1462 . In one respect, culling step  1462  may include displaying run time options to a viewer in step  1464 , receiving run time selections in step  1466 , and truncating the video playlist based on the run time selection in step  1468  to produce a truncated video playlist. In another respect, culling step  1462  may include displaying quantitative information associated with videos in the video playlist to the viewer in step  1470 , receiving play selections from the viewer based on the quantitative information in step  1472 , and truncating the video playlist in step  1474  based on the play selections to produce the truncated video playlist. Thus, in embodiments of the invention, the culling step  1462  may be based on run time selections and/or quantitative information. 
         [0077]    Videos associated with the truncated video playlist may be presented to a viewer in output step  1476 . More specifically, the KM system may receive playback commands from the viewer in step  1478  and sequentially stream video content to the viewer based on the truncated video playlist and the playback commands in step  1480 . Preferably, the process may execute step  1480  using fade-to-white transitions between videos in the presented video stream. 
         [0078]    Output step  1476  may also include displaying quantitative information in step  1482  that is associated with the truncated video playlist. Display step  1482  may display, for instance, quantitative information that has been collected from an original storyteller and/or from vantage point contributors. The format of such quantitative information display may be or include, for instance cross-tab charts, frequency charts, bar graphs, and/or pie charts. The information display portion  1230  of GUI  1205  is the type of output that could result from execution of step  1482 . 
         [0079]    Output step  1476  may also include receiving interview scoring information from the viewer in step  1484 . Such scoring information may be an opinion ranking or other type of qualitative information, and may be received for each video in the video stream that is presented to the viewer. The scoring portion  1240  of GUI  1235  is an exemplary mechanism for executing step  1484 . 
         [0080]    The processes described above with reference to output step  1476  may be performed in parallel or on an interrupt basis. Steps  1482  and  1484  are optional. 
         [0081]    At the conclusion of output step  1476 , the process may receive publication selections in step  1486  and publish video associated with the truncated video playlist in step  1488  based on the publication selections. As described above, publication could include posting a video story on a website (e.g., You Tube, My Space, or other personal blog), sending the video story to one or more email addressees, and/or saving the video to a local or remote data store. The process terminates in step  1490 . 
         [0082]    Variations to the process illustrated in  FIG. 14  are possible. For instance, steps  1410 ,  1415 , and/or  1420  may be combined or omitted, according to application needs. In an alternative embodiment, the template and keyword-type searches could be combined; for instance a keyword search could be used to narrow results from a template search. 
         [0083]    The processes described above with reference to  FIGS. 6 ,  7 ,  14 A, and  14 B may be implemented in hardware, software, or a combination of hardware and software. 
       Knowledge Management System 
       [0084]      FIG. 15  is a functional architecture of a KM system, according to an embodiment of the invention. As shown therein, a server  1505  is coupled to a client  1510  via a link  1515 . 
         [0085]    The server  1505  may be an application server and may include server-side application code  1520 . In addition, the server  1505  may include or be coupled to a story archive  1525  and/or a user account data store  1530 . Thus, in one respect, the server  1505  may function as a data server. The client  1510  may be a thick client or a thin client. The client  1510  may include, for example, browser code  1535 , client-side application code  1540 , and input/output (I/O) devices and drivers  1545 . The client  1510  may also include or be coupled to a client data store  1550 . The link  1515  may be or include a wired or wireless communication network. For instance, the link  1515  could be or include the Internet or other network. 
         [0086]    Together, the server  1505  and client  1510  are configured to execute the processes described above with reference to  FIGS. 6 ,  7 ,  14 A and  14 B. Although not shown, the server  1505  and client  1510  each include processors. A server processor (not shown) in the server  1505  can execute the server-side application code  1520 , and a client processor (not shown) in the client  1510  can execute the client-side application code. 
         [0087]    Variations to the KM system illustrated in  FIG. 15  are possible. For example, the KM system could include more than one server, such as a separate application server and database server. Likewise, the KM system could include more than one client, as is typical in client-server architectures. The allocation of application code between the server(s) and the client(s) is subject to design choice. 
         [0088]    It will be apparent to those skilled in the art that modifications and variations can be made without deviating from the spirit or scope of the invention. For example, alternative features described herein could be combined in ways not explicitly illustrated or disclosed. Thus, it is intended that the present invention cover any such modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.