Method and System for Managing Metadata

• US 20080201299A1
• Filed: 11/29/2004
• Published: 08/21/2008
• Est. Priority Date: 06/30/2004
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Lakkala, Harri, Hakala, Tero, Lehikoinen, Juha, Salminen, Ilkka, Huuskonen, Pertti, Karhu, Mika, Sorsa, Timo
• Application Number:
  US11/630,238
• Publication Number:
  US 20080201299A1
• Time in Patent Office: Days
• US Class Current: 707/3
• CPC Class Codes: G06F 16/48 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually

Abstract

Methods and systems for managing metadata are described. The method comprises steps of receiving a request from an application to access a metadata attribute corresponding to a piece of content, determining whether the application is authorized to access the metadata attribute, retrieving the metadata attribute upon determining that the application is authorized to access the metadata attribute, and transmitting the metadata attribute to the application. A metadata storage medium may be accessed and searched for the metadata attribute. A system for associating content data, context data, and an event is also described. The system allows for a user to search for content data based upon context data. Another method for associating data is described. The method includes steps of initiating a mufti-media call session, initiating an application independent of the mufti-media call session, and associating collected metadata from the application and the mufti-media call session.

Claims

1. A method for managing metadata, the method comprising steps of:

receiving a request from an application to access a metadata attribute corresponding to a piece of content;

determining whether the application is authorized to access the metadata attribute;

retrieving the metadata attribute upon determining that the application is authorized to access the metadata attribute; and

transmitting the metadata attribute to the application,

wherein the metadata attribute is stored in a metadata storage medium separate from the piece of content.

2. The method of claim 1, wherein the step of retrieving includes steps of:

accessing a metadata storage medium;

searching the metadata storage medium for the metadata attribute; and

identifying the metadata attribute.

3. The method of claim 2, wherein the step of retrieving includes a step of decrypting the metadata attribute.

4. The method of claim 1, further comprising steps of:

determining whether the metadata attribute has been modified; and

automatically storing the modified metadata attribute.

5. The method of claim 4, wherein upon determining the metadata attribute has been modified, the method includes a step of modifying a second metadata attribute to indicate the modified first metadata attribute.

6. The method of claim 4, wherein the step of automatically storing includes automatically storing the modified metadata attribute in a device external to the application.

7. The method of claim 1, wherein the request from the application to access the metadata attribute is a request to modify the metadata attribute.

8. The method of claim 7, further comprising a step of modifying the metadata attribute in response to the request from the application.

9. The method of claim 1, wherein the step of determining includes determining an access right to modify the metadata attribute.

10. The method of claim 9, wherein the access right is an indication of applications authorized to modify the metadata attribute.

11. The method of claim 1, wherein the metadata attribute is a private metadata attribute.

12. A computer-readable medium storing computer-executable instructions for performing the steps recited in claim 1.

13. A system for managing metadata, comprising:

an authorization system configured to determine whether an application is authorized to access a metadata attribute corresponding to a content object;

a metadata engine configured to receive requests to access the metadata attribute from the authorization system and to transmit the metadata attribute to the authorization system;

a metadata storage system configured to store the metadata attribute corresponding to content objects; and

a media database configured to store content objects, the media database being external to and separate from the metadata storage system.

14. The system of claim 13, further comprising a harvester configured to analyze the content object to obtain the metadata attribute.

15. The system of claim 13, further comprising a filter configured to extract the metadata attribute from the content object.

16. The system of claim 13, further comprising a search tool configured to search the metadata storage system for the metadata attribute.

17. The system of claim 13, wherein the authorization system, the metadata engine, the metadata storage system, and the media database are software components.

18. The system of claim 13, wherein the system is a terminal device.

19. The system of claim 13, wherein the system is a server.

20. The system of claim 13, further comprising a terminal device including an application configured to request access to metadata attributes corresponding to content objects.

21. The system of claim 20, wherein the terminal device includes the authorization system.

22. The system of claim 13, wherein the metadata storage subsystem and the media storage subsystem are stored separately in a common storage subsystem.

23. A user interface in a computer for reviewing a relationship of objects, comprising:

a first portion configured to indicate the existence of at least one new relationship between a content object and another object; and

a second portion configured to indicate a type of the at least one new relationship.

24. The user interface of claim 23, further comprising a third portion configured to indicate the number of the at least one new relationship.

25. The user interface of claim 23, further comprising a third portion configured to change in appearance and to indicate a whether the at least one new relationship has been accessed.

26. The user interface of claim 23, wherein the first portion is further configured to receive a user input to open the at least one new relationship.

27. The user interface of claim 23, wherein the type of at least one new relationship is at least one of:

a media file and a text file.

28. A method for associating data, the method comprising steps of:

detecting the occurrence of an event;

collecting content data;

automatically collecting context data;

associating the context data, the content data, and the event; and

storing the association of the content data, the context data, and the event,

wherein the step of associating includes a step of creating a variable corresponding to a common value between the content data, the context data, and the event.

29. The method of claim 28, wherein the step of detecting includes a step of storing the event in a superlog.

30. The method of claim 28, wherein the step of collecting content data includes a step of capturing the content data with an electronic device.

31. The method of claim 28, wherein the context data is predefined contextual metadata.

32. The method of claim 28, wherein the method of storing includes a step of storing the association of the content data, context data, and the event as metadata.

33. The method of claim 28, further comprising a step of accessing the content data, wherein the step of accessing the content data includes a step of determining the content data based upon the context data.

34. The method of claim 28, further comprising a step of accessing the content data, wherein the step of accessing the content data includes a step of determining the content data based upon the event.

35. The method of claim 28, further comprising a step of accessing the content data, wherein the step of accessing the content data includes a step of searching for the content data.

36. The method of claim 35, wherein the step of searching for the content data includes a step of searching for the content data based upon at least one of the context data and the event.

37. A computer-readable medium storing computer-executable instructions for performing the steps recited in claim 28.

38. A system for managing data, comprising:

a database manager configured to detect the occurrence of an event;

a database configured to store content data associated with the event;

a context engine configured automatically to collect context data;

a database component configured to store an association between the event, the content data, and the context data, the database manager being configured to create a variable corresponding to a common value between the content data, the context data, and the event.

39. The system of claim 38, further comprising an electronic device configured to initiate the event.

40. The system of claim 38, wherein the database manager is configured to request context data from the context engine to associate with the event.

41. The system of claim 38, wherein the database manager is configured to request content data from the database to associate with the event.

42. The system of claim 38, wherein the stored association includes metadata.

43. The system of claim 38, wherein the database manager is configured to receive a request to access the content data.

44. The system of claim 43, wherein the database manager is configured to request the content data based upon the event.

45. The system of claim 43, wherein the database manager is configured to request the content data based upon the context data.

46. The system of claim 43, wherein the request to access the content data is a request to search for the content data.

47. The system of claim 46, wherein the request to search for the content data is based upon at least one of the context data and the event.

48. A method of associating data, the method comprising steps of:

initiating a multi-media call session;

obtaining metadata directly associated with the multi-media call session;

initiating an application independent of the multi-media call session;

obtaining metadata associated with the application; and

automatically associating the metadata directly associated with the multi-media call session and the metadata associated with the application.

49. The method of claim 48, wherein the multi-media call session is a Rich Call session.

50. The method of claim 48, wherein the metadata associated with the application includes a filename of a file saved by the application.

51. The method of claim 48, further comprising a step of storing the association of the metadata directly associated with the multi-media call session and the metadata associated with the application.

52. The method of claim 51, wherein the step of storing includes storing in a database directly associated with the multi-media call session.

53. The method of claim 52, further comprising steps of:

accessing the database; and

providing the metadata associated with the application and the metadata directly associated with the multi-media call session.

54. The method of claim 52, further comprising a step of ending the multi-media call session, wherein the step of ending occurs prior to the step of accessing.

55. The method of claim 48, further comprising steps of:

initiating a second application independent of the multi-media call session;

obtaining metadata associated with the second application; and

automatically associating the metadata directly associated with the multi-media call session and the metadata associated with the second application.

56. The method of claim 55, further comprising steps of:

receiving a request to initiate the application from a first source; and

receiving a request to initiate the second application from a second source.

57. A computer-readable medium storing computer-executable instructions for performing the steps recited in claim 48.

58. A system for managing data, comprising:

a multi-media call session manager configured to obtain metadata directly associated with the multi-media call session, to obtain metadata associated with an application, and to create an association between the metadata directly associated with the multi-media call session and the metadata associated with the application; and

a database component configured to store the association.

59. The system of claim 58, wherein the multi-media call session is a Rich Call session.

60. The system of claim 58, wherein the metadata associated with the application includes a filename of a file saved by the application.

61. The system of claim 58, further comprising a database directly associated with the multi-media call session, wherein the database includes the database component.

62. The system of claim 58, wherein the multi-media call session manager further is configured to receive requests to access the database.

63. The system of claim 62, wherein the multi-media call session manager further is configured to provide the metadata associated with the application and the metadata directly associated with the multi-media call session.

64. The system of claim 58, wherein the multi-media call session manager further is configured to obtain metadata associated with a second application and to create an association between the metadata directly associated with the multi-media call session and the metadata associated with the second application.

65. The system of claim 64, wherein the multi-media call session manager further is configured to receive a request to initiate the application from a first source and to receive a request to initiate the second application from a second source.

66. The system of claim 58, further comprising a user interface, coupled to the multi-media call session manager, configured to provide the metadata directly associated with the multi-media call session and the metadata associated with the application.

67. The system of claim 58, further comprising a user interface, coupled to the multi-media call session manager, configured to provide the association between the metadata directly associated with the multi-media call session and the metadata associated with the application.

68. A method of associating data, the method comprising steps of:

receiving a request to initiate a multi-media call session;

initiating the multi-media call session;

collecting metadata directly associated with the multi-media call session;

receiving a request to initiate an application;

initiating the application, wherein the application is independent of the multi-media call session and allows for notations to be saved;

collecting metadata associated with the application;

automatically associating the metadata directly associated with the multi-media call session and the metadata associated with the application;

storing the association;

receiving a request to end the multi-media call session;

ending the multi-media call session;

receiving a request to access the association; and

providing the metadata associated with the application and the metadata directly associated with the multi-media call session.