Content sharing using metadata

• US 8,161,069 B1
• Filed: 01/25/2008
• Issued: 04/17/2012
• Est. Priority Date: 02/01/2007
• Status: Active Grant

• Current Assignee: Eighty-Three Degrees Incorporated
• Original Assignee: Eighty-Three Degrees Incorporated
• Inventors: Wilder, Nicholas, Rocherolle, Narendra, Davidson Rocherolle, Julie
• Primary Examiner(s): ALAM, SHAHID AL
• Application Number:
  US12/020,446
• Time in Patent Office: 1,544 Days
• Field of Search: 707/951, 707/705, 707/769, 707/770, 715/753, 716/6, 345/853
• US Class Current: 707/783
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/24573 using data annotations, e.g. user-defined metadata
• CPC Class Codes: G06F 16/2477 Temporal data queries
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06Q 10/109 Time management, e.g. calendars, reminders, meetings or time accounting
• CPC Class Codes: G06Q 50/01 Social networking

Abstract

Disclosed are embodiments of systems and methods that allow for the robust, flexible, and efficient sharing of content. In embodiments, content items may be associated with metadata, third parties may be associated with metadata, and sharing with the third party may be based upon comparisons of the metadata associated with the content items and the metadata associated with the third parties.

Claims

1. A method for sharing calendar events with one or more third parties, the method comprising:

receiving from a user one or more user-created tags associated with a calendar event;

receiving from the user one or more user-created tags associated with a third party;

storing in one or more storage media the one or more user-created tags associated with the calendar event and the one or more user-created tags associated with the third party;

using an access rule to determine access to the calendar event for the third party by comparing, using at least one processor unit, the one or more user-created tags associated with the calendar event with the one or more user-created tags associated with the third party; and

responsive to the one or more user-created tags associated with the calendar event and the one or more user-created tags associated with the third party satisfying the access rule, granting the third party access to the calendar event.

2. The method of claim 1 wherein the access rule comprises the one or more user-created tags associated with the third party.

3. The method of claim 1 wherein the one or more user-created tags associated with the calendar event are descriptive of the calendar event.

4. The method of claim 1 wherein the one or more user-created tags associated with the third party are descriptive of a relationship or relationships between the user and the third party.

5. The method of claim 1 further comprising:

allowing the third party to alter data associated with the calendar event.

6. The method of claim 1 further comprising:

receiving from the third party one or more third-party-created tags associated with a third-party calendar event;

receiving from the third party one or more third-party-created tags associated with the user; and

granting the user access to the third-party calendar event based upon the one or more third-party-created tags associated with the third-party calendar event and the one or more third-party-created tags associated with the user.

7. The method of claim 6 further comprising:

generating a calendar view comprising calendar events to which both the user and the third party have access.

8. The method of claim 1 wherein the access rule is a default rule in which a third party is granted access if at least one user-created tag is common between the one or more user-created tags associated with the calendar event and the one or more user-created tags associated with the third party.

9. The method of claim 1 wherein the access rule is defined by the user.

10. The method of claim 9 wherein the access rule comprises one or more logical operations.

11. A system for facilitating the sharing of calendar events, the system comprising:

a calendaring application that receives from a user a first set of one or more user-created metadata associated with a calendar event, and that receives from the user one or more user-created metadata associated with a third party;

an access rights module, coupled to receive user-created metadata associated with the calendar event and the one or more user-created metadata associated with a third party, that compares the one or more user-created metadata associated with the calendar event with the one or more user-created metadata associated with the third party using an access rule and grants the third party access to the calendar event responsive to the access rule being satisfied; and

data storage, coupled to receive information from the calendaring application, that stores the calendar event and associated metadata.

12. The system of claim 11 wherein:

the calendaring application receives from the user a second set of one or more user-created metadata to associate with the calendar event wherein the first and second sets of user-created metadata are concurrently associated with the calendar event; and

the access rights module grants the third party access to the calendar event based upon at least one of the first and second sets of user-created metadata associated with the calendar event and the one or more user-created metadata associated with the third party satisfying an access rule.

13. The system of claim 11 wherein the access rule is defined by the user.

14. At least one non-transitory computer-readable medium comprising one or more sets of instructions which, when executed by one or more processors, causes a method for sharing calendar events with one or more third parties to be performed, the method comprising:

receiving from a user one or more user-created tags associated with a calendar event;

receiving from the user one or more user-created tags associated with a third party;

storing in one or more storage media the one or more user-created tags associated with the calendar event and the one or more user-created tags associated with the third party;

using an access rule to determine access to the calendar event for the third party by comparing, using at least one processor unit, the one or more user-created tags associated with the calendar event with the one or more user-created tags associated with the third party; and

responsive to the one or more user-created tags associated with the calendar event and the one or more user-created tags associated with the third party satisfying the access rule, granting the third party access to the calendar event.

15. The at least one non-transitory computer-readable medium of claim 14 wherein the access rule is a default rule in which a third party is granted access if at least one user-created tag is common between the one or more user-created tags of the calendar event and the one or more user-created tags associated with the third party.

16. The at least one non-transitory computer-readable medium of claim 14 wherein the access rule is defined by the user.

17. The at least one non-transitory computer-readable medium of claim 16 wherein the access rule comprises one or more logical operations.

18. The at least one non-transitory computer-readable medium of claim 14 wherein the one or more user-created tags associated with the calendar event are descriptive of the calendar event.

19. The at least one non-transitory computer-readable medium of claim 14, wherein the method further comprises:

receiving from the third party one or more third-party-created tags associated with a third-party calendar event;

receiving from the third party one or more third-party-created tags associated with the user; and

granting the user access to the third-party calendar event based upon the one or more third-party-created tags associated with the third-party calendar event and the one or more third-party-created tags associated with the user.

20. The at least one non-transitory computer-readable medium of claim 14, wherein the method further comprises:

generating a calendar view comprising calendar events to which both the user and the third party have access.