Template-Based Management and Organization of Events and Projects

• US 20110179045A1
• Filed: 06/18/2010
• Published: 07/21/2011
• Est. Priority Date: 01/19/2010
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sharma, Ashish, Phan, Tu Huy, Chilakamarri, Venkat Pradeep, Powell, Kevin, Manis, Kimberly, Azzam, Saliha, Caldwell, Nicholas, Shah, Jignesh, Childs, Benjamin Edward, Perez Del Carpio, Diego, O'Keefe, Courtney Anne, Ludwig, Jonathan C., Kohlmeier, Bernhard SJ
• Application Number:
  US12/818,746
• Publication Number:
  US 20110179045A1
• Time in Patent Office: Days
• US Class Current: 707/754
• CPC Class Codes: G06Q 10/00 Administration; Management

Abstract

A space in which a user may organize data and collaborate with other users is provided. Project data and metadata may be saved into a reusable template and stored in a repository, wherein other users may discover and download the template for use as a resource for a related project type. A template may contain various document types that may expose a breadth of applications and application functionalities that may be utilized for a given task or project. Questions and answers, task templates, and terminology may also be provided. Project templates may allow for collaboration on projects, wherein business and/or social groups may collaborate quickly, easily, and more completely.

Claims

1. A method of providing a reusable package of project data and metadata, the method comprising:

storing project data and metadata associated with a given project in a project data store;

filtering project data and metadata for project data and metadata associated with a given project;

packaging filtered project data and metadata into a template; and

storing the template in a template repository.

2. The method of claim 1, wherein storing project data and metadata associated with a given project in a project data store includes storing one or more data types from one or more data sources associated with the given project.

3. The method of claim 2, wherein storing one or more data types from one or more data sources associated with the given project includes storing one or more of a project title, a project description, an identification of one or more project team members, one or more links to other data stores, one or more identifications to information entities, one or more features of interest extracted from information entities, and one or more identifications and links to one or more software applications.

4. The method of claim 1, wherein filtering project data and metadata for project data and metadata associated with a given project includes filtering out project data that should not be packaged into a template and stored in a template repository.

5. The method of claim 4, wherein filtering out project data that should not be packaged into the template and stored in the template repository includes withholding from the project data packaged into the template and stored in the template repository any project data designated as private project data.

6. The method of claim 1, wherein packaging filtered project data and metadata into a template includes packaging the metadata into a template in association with one or more software applications, the one or more software applications being operative to utilize the project data and metadata.

7. The method of claim 1, wherein the template repository is a shared repository.

8. A method of downloading a template for providing a reusable package of project data and metadata, the method comprising:

suggesting use of a given template based on metadata associated with a given project;

receiving an indication of a selection of a suggested template; and

copying project data and metadata stored within the template into a local data repository.

9. The method of claim 8, prior to suggesting use of a given template based on metadata associated with a given project,

storing project data and metadata associated with a given project in a project data store;

filtering project data and metadata for project data and metadata associated with the given project;

packaging filtered project data and metadata into a template; and

storing the template in a template repository.

10. The method of claim 8, wherein receiving an indication of a selection of a template includes receiving an indication of a selection of a template stored in a shared template repository.

11. The method of claim 8, wherein copying project data and metadata stored within the template into a local data repository includes copying project data and metadata of one or more data types from one or more data sources associated with the given project.

12. The method of claim 8, wherein the template is not associated with a particular application.

13. A computer-readable medium which stores a set of instructions which when executed performs a method for providing a reusable package of project data and metadata, the method comprising:

storing project data and metadata associated with a given project in a project data store;

filtering project data and metadata for project data and metadata associated with a given project;

packaging filtered project data and metadata into a template;

storing the template in a template repository;

receiving an indication of a selection of the template associated with the given project; and

copying project data and metadata stored within the template into a local data repository.

14. The computer-readable medium of claim 13, wherein storing project data and metadata associated with a given project in a project data store includes storing one or more data types from one or more data sources associated with the given project.

15. The computer-readable medium of claim 14, wherein storing one or more data types from one or more data sources associated with the given project includes storing one or more of a project title, a project description, an identification of one or more project team members, one or more links to other data stores, one or more identifications to information entities, one or more features of interest extracted from information entities, and one or more identifications and links to one or more software applications.

16. The computer-readable medium of claim 13, wherein filtering project data and metadata for project data and metadata associated with a given project includes filtering out project data that should not be packaged into a template and stored in a template repository.

17. The computer-readable medium of claim 16, wherein filtering out project data that should not be packaged into the template and stored in the template repository includes withholding from the project data packaged into the template and stored in the template repository any project data designated as private project data.

18. The computer-readable medium of claim 13, wherein packaging filtered project data and metadata into a template includes packaging the metadata into a template in association with one or more software applications, the one or more software applications being operative to utilize the project data and metadata.

19. The computer-readable medium of claim 18, wherein the template is software application agnostic.

20. The computer-readable medium of claim 13, wherein the template repository is a shared repository.