Method and apparatus for management of multimedia assets

• US 6,477,537 B2
• Filed: 02/22/2001
• Issued: 11/05/2002
• Est. Priority Date: 07/10/1996
• Status: Expired due to Term

• Current Assignee: University of Southern California
• Original Assignee: Survivors of the Shoah Visual History Foundation
• Inventors: Gustman, Samuel
• Primary Examiner(s): Mizrahi, Diane D.
• Application Number:
  US09/792,381
• Publication Number:
  US 20020049604A1
• Time in Patent Office: 621 Days
• Field of Search: 707/103, 707/104.1, 707/102, 707/10, 707/206
• US Class Current: 1/1
• CPC Class Codes: G06F 16/40 of multimedia data, e.g. slideshows comprising image and additional audio data retrieval of still image data G06F16/50; retrieval of audio data G06F16/60; retrieval of video data G06F16/70
• CPC Class Codes: G06F 16/48 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99935 Query augmenting and refining, e.g. inexact access
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

The system is a generalized solution for management of multimedia assets. Generalized interfaces are used between a browser component, indexing server, archive server, tertiary storage manager, and method player components. The generalized interface defines a communication protocol that can be used by any browser, indexing server, archive server, tertiary storage manager, or method player component. Thus, system components supplied by multiple vendors can be interconnected to form a multimedia system that communicates using the generalized interfaces of the invention. A browser component can accept input such as search requests and display multimedia data. An indexing server component includes a data catalogue that catalogues multimedia data. The catalogue can be used to identify catalogue elements associated with data that can satisfy a search request. A search mechanism is used to identify the desired multimedia data. A search mechanism can create additional catalogues that are a subset of the catalogue provided on the indexing server. An archive server identifies a tertiary storage manager that manages the store containing the multimedia data. The tertiary storage manager retrieves the corresponding multimedia data from its store and sends it to a method play which plays it in a display region of the browser. The invention retains the content and results of a search such that it is only necessary to perform a search once. Search elements are used to store the content of a search, i.e., search criteria. A segment element is used to store the results of a search.

Claims

1. An application program interface (API) embodied on a computer readable medium for execution on a computer in conjunction with an application program to interface components in a multimedia system comprising:

an API protocol means comprising a command interface between a first system component and at least one additional system component, said command interface comprising;

means for selecting multimedia data that satisfies a criteria of said first system component selected using said API protocol means, said multimedia data associated with a multimedia catalogue, said catalogue associated with said at least one additional system component;

means for retrieving from said at least one additional system component multimedia data selected by said selecting means;

means for displaying said multimedia data retrieved by said retrieving means.

2. The API protocol means of claim 1 wherein said first system component comprises a browser and said at least one additional system component comprises a method player.

3. The API protocol means of claim 1 wherein said first system component comprises a browser and said at least one additional component comprises an archive server.

4. The API protocol means of claim 3 wherein said browser and said indexing server are vendor independent.

5. The API protocol means of claim 3 wherein said multimedia data comprises a person catalogued in said indexing server.

6. The API protocol means of claim 5 wherein said protocol means comprises an interface that receives an identifier to said person and returns a full name of said person.

7. The API protocol means of claim 5 wherein said protocol means comprises an interface that receives an identifier to testimony and returns a survivor identifier of said person corresponding to said testimony identifier.

8. The API protocol means of claim 5 wherein said protocol means comprises an interface that receives an identifier to said person and returns a testimony identifier of said person identified by said person identifier.

9. The API protocol means of claim 5 wherein said protocol means comprises an interface that receives a first name and a last name and returns a number of person identifiers corresponding to said first name and said last name.

10. The API protocol means of claim 5 wherein said protocol means comprises an interface that receives a first name and a last name and returns a set of person identifiers corresponding to said first name and said last name.

11. The API protocol means of claim 3 wherein said multimedia data comprise a thesaural keyword catalogued in said indexing server.

12. The API protocol means of claim 11 wherein said protocol means comprises an interface that receives an identifier to said thesaural keyword and returns a keyword identifier of said thesaural keyword.

13. The API protocol means of claim 11 wherein said protocol means comprises an interface that receives an identifier to said thesaural keyword and returns a label of said thesaural keyword.

14. The API protocol means of claim 11 wherein said protocol means comprises an interface that receives an identifier to said thesaural keyword and a search string and returns a number of said thesaural keywords wherein a label field of each of said thesaural keywords corresponding to said thesaural keyword identifiers comprise said search string.

15. The API protocol means of claim 11 wherein said protocol means comprises an interface that receives an identifier to said thesaural keyword and a search string and returns a set of thesaural keyword identifiers wherein a label field of each of said thesaural keywords corresponding to said thesaural keyword identifiers comprise said search string.

16. The API protocol means of claim 1 wherein said multimedia data comprise a type catalogued in said indexing server.

17. The API protocol means of claim 16 wherein said protocol means comprises an interface that receives an identifier to said type and returns a type label of said type.

18. The API protocol means of claim 16 wherein said protocol means comprises an interface that receives an identifier to said type and returns a type description of said type.

19. The API protocol means of claim 16 wherein said protocol means comprises an interface that receives an identifier to said type and returns a number of keywords of said type.

20. The API protocol means of claim 16 wherein said protocol means comprises an interface that receives an identifier to said type and returns a set of keyword identifiers of said type.

21. The API protocol means of claim 16 wherein said protocol means comprises an interface that receives an identifier to said type and returns a number of type identifiers wherein a type label field of each type corresponding to said type identifiers comprises said search string.

22. The API protocol means of claim 16 wherein said protocol means comprises an interface that receives a search string and returns a set of type identifiers wherein a type label field of each type corresponding to said type identifiers comprises said search string.

23. The API protocol means of claim 16 wherein said protocol means comprises an interface that receives a search string and returns a set of type identifiers wherein a type description field of each type corresponding to said type identifiers comprises said search string.

24. The API protocol means of claim 16 wherein said protocol means comprises an interface that receives a search string and returns a number of type identifiers wherein a type description field of each type corresponding to said type identifiers comprises said search string.

25. The API protocol means of claim 16 wherein said protocol means comprises an interface that receives a search string and returns a set of type identifiers wherein a type description field of each type corresponding to said type identifiers comprises said search string.

26. The API protocol means of claim 16 wherein said protocol means comprises an interface that receives an identifier to said type and returns a number of parent type identifiers of said type.

27. The API protocol means of claim 16 wherein said protocol means comprises an interface that receives an identifier to said type and returns a set of parent type identifiers of said type.

28. The API protocol means of claim 16 wherein said protocol means comprises an interface that receives an identifier to said type and returns a preferred parent type identifier of said type.

29. The API protocol means of claim 16 wherein said protocol means comprises an interface that receives an identifier to said type and returns a number of child type identifiers of said type.

30. The API protocol means of claim 16 wherein said protocol means comprises an interface that receives an identifier to said type and returns a set of child type identifiers of said type.

31. The API protocol means of claim 1 wherein said first system component comprises a browser and said at least one additional system component comprises an indexing server.

32. The API protocol means of claim 31 wherein said multimedia data comprises testimony catalogued in said catalogue of said indexing server.

33. The API protocol means of claim 32 wherein said selecting means comprises an interface that receives an identifier to said testimony and returns a number of phrases in said testimony.

34. The API protocol means of claim 32 wherein said selecting means comprises an interface that receives an identifier to said testimony and returns a set of phrases in said testimony.

35. The API protocol means of claim 32 wherein said selecting means comprises an interface that receives an identifier to said testimony and a phrase identifier and returns a phrase structure of said testimony.

36. The API protocol means of claim 32 wherein said selecting means comprises an interface that receives an identifier to said testimony and returns a number of segments of said testimony.

37. The API protocol means of claim 32 wherein said selecting means comprises an interface that receives an identifier to said testimony and returns a set of segments of said testimony.

38. The API protocol means of claim 32 wherein said selecting means comprises an interface that receives an identifier to a collection type of said testimony and returns a number of segments corresponding to said collection type.

39. The API protocol means of claim 32 wherein said selecting means comprises an interface that receives an identifier to a collection type and returns a set of segments of said collection type in said testimony.

40. The API protocol means of claim 32 wherein said selecting means comprises an interface that receives an identifier to said testimony and returns a number of keywords in said testimony.

41. The API protocol means of claim 32 wherein said selecting means comprises an interface that receives an identifier to said testimony and returns a set of keywords in said testimony.

42. The API protocol means of claim 32 wherein said selecting means comprises an interface that receives an identifier to said testimony and returns a number of thesaural keywords in said testimony.

43. The API protocol means of claim 32 wherein said selecting means comprises an interface that receives an identifier to said testimony and returns a set of thesaural keywords in said testimony.

44. The API protocol means of claim 32 wherein said selecting means comprises an interface that receives an identifier to said testimony and returns a number of person keywords in said testimony.

45. The API protocol means of claim 32 wherein said selecting means comprises an interface that receives an identifier to said testimony and returns a set of person identifiers in said testimony.

46. The API protocol means of claim 32 wherein said multimedia data further comprises a phrase catalogued in said indexing server.

47. The API protocol means of claim 46 wherein said protocol means comprises an interface that receives an identifier to said testimony and an identifier to said phrase and returns a starting location of said phrase in said testimony.

48. The API protocol means of claim 46 wherein said protocol means comprises an interface that receives an identifier to said testimony and an identifier to said phrase and returns an ending location of said phrase in said testimony.

49. The API protocol means of claim 46 wherein said protocol means comprises an interface that receives an identifier to said testimony and an identifier to said phrase and returns a number of keywords in said phrase in a testimony.

50. The API protocol means of claim 46 wherein said protocol means comprises an interface that receives an identifier to said testimony and an identifier to said phrase and returns a set of keyword identifiers in said phrase in said testimony.

51. The API protocol means of claim 46 wherein said protocol means comprises an interface that receives an identifier to said testimony, an identifier to said phrase, and a string and returns a number of phrases wherein said string comprises a phrase description of said phrase in said testimony.

52. The API protocol means of claim 46 wherein said protocol means comprises an interface that receives an identifier to said testimony and a string and returns a set of phrase identifiers wherein said string comprises a phrase description of said phrase.

53. The API protocol means of claim 31 wherein said multimedia data comprise a keyword catalogued in said indexing server.

54. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and returns a type identifier of said keyword.

55. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and returns a number of authority identifiers corresponding to said keyword.

56. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and returns a set of authority identifiers corresponding to said keyword.

57. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and identifier to an authority record and returns a set of reference details of said authority record comprising said keyword.

58. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and returns a number of testimonies comprising said keyword.

59. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and returns a set of testimony identifiers corresponding to said keyword.

60. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and returns a number of segments corresponding to said keyword.

61. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and returns a set of segment identifiers corresponding to said keyword.

62. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and an identifier to a testimony and returns a number of phrases corresponding to said keyword in said testimony.

63. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and an identifier to a testimony and returns a set of phrase identifiers corresponding to said keyword in said testimony.

64. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and a search string and returns a boolean value indicating a label field of said keyword comprises said search string.

65. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives a search string and returns a set of keyword identifiers wherein a label field of each of said set of keywords corresponding to said keyword identifiers comprise said search string.

66. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and a search string and returns a boolean value indicating a description field of said keyword comprises said search string.

67. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives a search string and returns a set of keyword identifiers wherein a description field of each of said keywords corresponding to said keyword identifiers comprise said search string.

68. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and a search string and returns a boolean value indicating a Soundex code field of said keyword comprises said search string.

69. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives a search string and returns a set of keyword identifiers wherein a Soundex code field of each of said keywords corresponding to said keyword identifiers comprise said search string.

70. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and returns a number of parent keyword identifiers of said keyword.

71. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and returns a set of parent keyword identifiers of said keyword.

72. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and returns a keyword identifier of a preferred parent keyword of said keyword.

73. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and returns a number of child keyword identifiers corresponding to said keyword.

74. The API protocol means of claim 53 wherein said protocol means comprises an interface that receives an identifier to said keyword and returns a set of child keyword identifiers corresponding to said keyword.

75. The API protocol means of claim 31 wherein said multimedia data comprise a segment catalogued in said indexing server.

76. The API protocol means of claim 75 wherein said protocol means comprises an interface that receives an identifier to said segment and returns a collection type of said segment.

77. The API protocol means of claim 75 wherein said protocol means comprises an interface that receives an identifier to said segment and returns a segment description of said segment.

78. The API protocol means of claim 75 wherein said protocol means comprises an interface that receives an identifier to said segment and returns a number of phrases in said segment.

79. The API protocol means of claim 75 wherein said protocol means comprises an interface that receives an identifier to said segment and returns a set of phrase identifiers in said segment.

80. The API protocol means of claim 75 wherein said protocol means comprises an interface that receives an identifier to said segment and returns a number of keywords in said segment.

81. The API protocol means of claim 75 wherein said protocol means comprises an interface that receives an identifier to said segment and returns a set of keyword identifiers in said segment.

82. The API of claim 75 wherein said protocol means comprises an interface that receives an identifier to said segment and returns a number of instances of a string in a segment description of said segment.

83. The API protocol means of claim 75 wherein said protocol means comprises an interface that receives an identifier to said segment and a string and returns a number of instances of said string wherein said string