Associating user-defined tags with event records in an events repository

• US 20070239761A1
• Filed: 03/28/2006
• Published: 10/11/2007
• Est. Priority Date: 03/28/2006
• Status: Abandoned Application

• Current Assignee: Oath Inc. (Verizon Communications Inc.)
• Original Assignee: Oath Inc. (Verizon Communications Inc.)
• Inventors: Lin, Leonard, Baio, Andrew, Luk, Gordon
• Application Number:
  US11/392,425
• Publication Number:
  US 20070239761A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/38 Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually

Abstract

Techniques for accessing an events information repository are provided. An event information 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 event application and also for associating user-defined tags with events using the events information repository.

Claims

1. A method comprising performing a machine-executed operation involving instructions, wherein the machine-executed operation is at least one of:

A) sending said instructions over transmission media;

B) receiving said instructions over transmission media;

C) storing said instructions onto a machine-readable storage medium; and

D) executing the instructions;

wherein said instructions are instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of;

storing event records in the repository, each event record containing data defining one or more real world events;

storing user-designated tags in tag data maintained within the repository;

wherein the user-designated tags are associated with event records and reflect attributes of the real world events represented by the event records;

wherein the step of storing user-designated tags includes;

receiving user input from a first user, wherein the user input specifies a user-designated tag for a particular event represented by a particular event record within the repository; and

in response to said input, updating the tag data by storing the user-designated tag in association with the particular event record;

using the user-specified tags in said tag data to locate information about real-world events represented in the event records within the repository;

wherein the step of using the user-specified tags-includes;

receiving a request from a second user to retrieve events associated with a particular user-specified attribute;

responding to the request by comparing the particular user-specified attribute against user-specified tags in said tag data to identify a set of event records within the repository that are associated with tags that match said particular user-specified attribute, and providing to the second user information from the set of event records.

2. The method of claim 1, wherein the particular event record is associated with a plurality of user-designated tags.

3. The method of claim 2, wherein each of a plurality of users has associated one or more user-designated tags with said particular event record.

4. The method of claim 1, wherein a particular user-designated tag is associated with a plurality of event records

5. The method of claim 1, wherein each of the event records corresponds to an event and specifies:

when the event will occur;

an author of the event; and

a geographic location of the event.

6. The method of claim 1, where the instructions include instructions for:

storing tag-event data that identifies the frequency of a tag among event-records;

receiving a request from a user to view tag frequency information among event-records information;

inspecting the tag-event data; and

sending tag-event data to the user.

7. The method of claim 6, wherein sending tag-event data to the user includes sending a web page to the user, wherein the web page identifies the tag frequency information by changing the display characteristic of a representation of tags based on the frequency of the tags.

8. The method of claim 7 wherein the display characteristic is the display size.

9. The method of claim 1, wherein the user-specified attribute is an attribute that is not specified within the event-record.

10. The method of claim 1 wherein:

the request from the second user includes parameters that specify one or more event conditions; and

comparing the particular user-specified attribute against user-specified tags in said tag data to identify a set of event records further includes identifying a set of event records for which the one or more conditions are satisfied.

11. The method 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 method of claim 1, wherein the instructions further comprise instructions for:

allowing users to store event records in the repository;

when an event record is stored in the repository by a user, storing event-author information that identifies the user as the event-author of the event record;

allowing event authors to designate their events as private events;

storing event-type information that indicates which event records within the repository have been designated by their event authors as private events;

allowing event authors to designate one or more users as being authorized to view their private events; and

storing authorized-viewer information that indicates which users have been designated, by event authors of private events, as being authorized to view their private events.

13. The method of claim 12, wherein responding to the request includes, based on the authorized-viewer information, determining a set of event-records for which the user is authorized to view private events by and providing to the second user information from the set of event records.

14. The method of claim 1, wherein the repository further comprises group records defining one or more user-groups, and wherein the method further comprises:

allowing users to store user-group records in the repository;

storing group member information that indicates which users are members of the user-group;

wherein the user-designated tags are associated with user-group records and reflect attributes of the user-group represented by the event records;

wherein the step of storing user-designated tags includes;

receiving user input from a first user, wherein the user input specifies a user-designated tag for a particular user-group represented by a particular user-group record within the repository; and

in response to said input, updating the tag data by storing the user-designated tag in association with the particular user-group record.

15. The method of claim 1, wherein the instructions include instructions for:

providing to users a user interface that allows only the user that created each user-designated tag to delete the user-designated tag.

16. The method of claim 1, wherein the instructions include instructions for:

providing to users a user interface that allows a user-designated tag to be deleted by only

the user that created each user-designated tag to delete the user-designated tag;

or

the user that created the event record with which the user-designated tag is associated.