Creating and viewing private events in an events repository
Techniques for accessing an events information repository are provided. An events repository contains event records defining real world events. A programmatic interface is exposed to third-party applications for accessing the event records within the repository. Specifically, the programmatic interface provides a set of routines that perform operations on the repository. Using the programmatic interface, third-party applications may call the set of routines to cause operations to be executed on the repository. Further, techniques are provided for creating and viewing private events within an events repository and also for associating user-defined tags with events using the events repository.
1. A computer-implemented method comprising:
providing an event repository that maintains event information for members of an online community, wherein the event information includes one or more event records that correspond to real world private events, wherein at least one of the one or more event records has an event id that is associated with a tag id, wherein each tag id is associated with a tag, and wherein each event record comprises structured information that: (i) identifies a first user of the online community as an event-author of a private event, and (ii) is restricted to only a group of one or more friends of the event-author in the online community;
receiving from a second user of the online community, who is in the group of one or more friends of the first user, a user-designated tag of unstructured metadata, wherein the user-designed tag provides information about a first event record;
without modifying the first event record, storing in the event repository, separate from the first event record: (i) the user-designated tag; (ii) an association between the user-designated tag and a tag id; and (iii) an association between the tag id and an event id;
receiving from the second user of the online community, a request for retrieving event information, wherein the request specifies a term that matches the user-designated tag;
as a result of the request, performing the steps of:
searching the event repository for a plurality of event records that are associated with any user-designed tags that match the term, wherein the plurality of records includes the first event record; and
returning event information extracted from the plurality of event records to the second user of the online community;
wherein the computer-implemented method is performed by one or more computing devices.
2. The computer-implemented method of claim 1 , further comprising:
after the association between the tag id and the event id has been established, receiving from a third user of the online community, who is not in the group of one or more friends of the first user, a second request for retrieving event information, wherein the second request specifies a second term that matches the user-designated tag;
as a result of the second request, performing the steps of:
searching the event repository for a second plurality of event records that are associated with any user-designed tags that match the term, wherein the second plurality of records does not include the first event record; and
returning second event information extracted from the second plurality of event records to the third user of the online community.
3. The computer-implemented method of claim 1 , wherein:
the request is associated with one or more event conditions; and
wherein the computer-implemented method further comprises the step of determining that the private event satisfies the one or more event conditions.
4. The computer-implemented method of claim 3 , wherein the one or more conditions include at least one of:
a time range;
an event-author; and
a geographic location.
5. The computer-implemented method of claim 3 wherein:
the private event is one of a plurality of private events authored by said event-author;
the plurality of private events include a second private event that satisfies said one or more event conditions, wherein stored authorization viewer information specifies that the second private event is viewable to one or more third friends of said event-author and wherein the second user is not one of the one or more third friends of said event-author;
the computer-implemented method further comprising determining, based on the stored authorized-viewer information, that the second user is not authorized to view the second private event; and
the information transmitted to the second user in response to the request does not include information about the second private event.
6. The computer-implemented method of claim 3 wherein the information from the plurality of event records includes information about events that are not identified as private events and that otherwise satisfy the one or more conditions.
7. The computer-implemented method of claim 1 , wherein the information from the plurality of event includes information about private events from additional event-authors who have authorized the second user to view their private events.
8. A volatile or non-volatile computer readable medium storing one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform:
providing an event repository that maintains event information for members of an online community, wherein the event information includes one or more event records that correspond to real world private events, wherein at least one of the one or more event records has an event id that is associated with a tag id, wherein each tag id is associated with a tag, and wherein each event record comprises structured information that: (i) identifies a first user of the online community as an event-author of a private event, and (ii) is restricted to only a group of one or more friends of the event-author in the online community;
receiving from a second user of the online community, who is in the group of one or more friends of the first user, a user-designated tag of unstructured metadata, wherein the user-designed tag provides information about a first event record;
without modifying the first event record, storing in the event repository, separate from the first event record: (i) the user-designated tag; (ii) an association between the user-designated tag and a tag id; and (iii) an association between the tag id and an event id;
receiving from the second user of the online community, a request for retrieving event information, wherein the request specifies a term that matches the user-designated tag;
as a result of the request, performing the steps of:
searching the event repository for a plurality of event records that are associated with any user-designed tags that match the term, wherein the plurality of records includes the first event record; and
returning event information extracted from the plurality of event records to the second user of the online community;
wherein the computer-implemented method is performed by one or more computing devices.
9. The medium of claim 8 , wherein the one or more sequences of instructions further comprise instructions which, when executed by one or more processors, causes the one or more processors to perform:
after the association between the tag id and the event id has been established, receiving from a third user of the online community, who is not in the group of one or more friends of the first user, a second request for retrieving event information, wherein the second request specifies a second term that matches the user-designated tag;
as a result of the second request, performing the steps of:
searching the event repository for a second plurality of event records that are associated with any user-designed tags that match the term, wherein the second plurality of records does not include the first event record; and
returning second event information extracted from the second plurality of event records to the third user of the online community.
10. The medium of claim 8 , wherein:
the request is associated with one or more event conditions; and
wherein the one or more sequences of instructions further comprise instructions which, when executed by one or more processors, causes the one or more processors to perform determining that the private event satisfies the one or more event conditions.
11. The medium of claim 10 , wherein the one or more conditions include at least one of:
a time range;
an event-author; and
a geographic location.
12. The medium of claim 10 wherein:
the private event is one of a plurality of private events authored by said event-author;
the plurality of private events include a second private event that satisfies said one or more event conditions, wherein stored authorization viewer information specifies that the second private event is viewable to one or more third friends of said event-author and wherein the second user is not one of the one or more third friends of said event-author;
wherein the one or more sequences of instructions further comprise instructions which, when executed by one or more processors, causes the one or more processors to perform determining, based on the stored authorized-viewer information, that the second user is not authorized to view the second private event; and
the information transmitted to the second user in response to the request does not include information about the second private event.
13. The medium of claim 10 wherein the information from the plurality of event records includes information about events that are not identified as private events and that otherwise satisfy the one or more conditions.
14. The medium of claim 8 , wherein the information from the plurality of event includes information about private events from additional event-authors who have authorized the second user to view their private events.