System and method for collaborative data sharing and analysis

• US 20080059500A1
• Filed: 09/05/2006
• Published: 03/06/2008
• Est. Priority Date: 09/05/2006
• Status: Abandoned Application

• Current Assignee: Chad Symens
• Original Assignee: Chad Symens
• Inventors: Symens, Chad
• Application Number:
  US11/516,009
• Publication Number:
  US 20080059500A1
• Time in Patent Office: Days
• US Class Current: 707/101
• CPC Class Codes: G06F 16/283 Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising

Abstract

A collaborative data sharing and analysis system comprises a primary database utilizing a plurality of tables, and a user client that provides an interface that displays a retail and supplier data perspective. The primary database utilizes a recursive load function to load data recursively from the database tables so that a hierarchical organization of the data is presented via the interface. Once the data has been loaded, the user interface allows a user to manipulate the stored data according to one or more permissions, thus allowing a retailer and a supplier to collaborate with each other in real-time.

Claims

1. A database comprising:

a reports table maintaining a reportID field;

a files table maintaining a fileID field;

a users table;

a folders table maintaining a folderID field, wherein said folders table is self-referential;

a parentgroups table maintaining a groupID field and a parent groupID field;

a groups table; and

a permissions table maintaining permissions associated with each said folder in said folders table;

wherein said folders table is related to said files table, said reports table, said users table, said groups table, and said permissions table by said folder ID field.

2. The database of claim 1, wherein said users table maintains a username field and is related to said reports table, said files table, said folders table, said permissions table by said username field.

3. The database of claim 2, wherein said groups table also maintains said groupID field and is related to said parentgroups table, said users table, and said permissions table by said groupID field.

4. A method for organizing data retrieved from a database for presentation as a user interface for user interaction comprising:

loading a group associated with a user, wherein said user group has at least one parent subfolder and at least one child subfolder which are also loaded;

loading a group root folder associated with said user group, and loading any user group subfolders contained therein; and

loading a user root folder associated with the user, and loading any user group subfolders contained therein.

5. The method of claim 4 further comprising:

loading the contents of said group root folder and said user group subfolders.

6. The method of claim 5, wherein said contents comprises at least one report and a file.

7. The method of claim 4 further comprising:

loading the contents of said user root folder and said user group subfolders.

8. The method of claim 7, wherein said contents comprises at least one report and a file.

9. The method of claim 4 further comprising:

loading permissions associated with said group root folder and said user group subfolders.

10. The method of claim 4 further comprising:

loading permissions associated with said user root folder and said user group subfolders.

11. The method of claim 4 further comprising:

displaying said group root folder and said user group subfolders hierarchically via an interface.

12. The method of claim 4 further comprising:

displaying said user root folder and said user group subfolders hierarchically via an interface.

13. The method of claim 4, wherein at said first loading step, said parent and child subfolders are loaded recursively using the same software function.

14. The method of claim 4, wherein at said second loading step, said user group subfolders are loaded recursively using the same software function.

15. The method of claim 4, wherein at said third loading step, said user group subfolders are loaded recursively using the same software function.

16. A computer-readable medium having computer-executable instructions for performing a method comprising:

creating a database structure comprising;

a reports table to store one or more reports;

a files table to store one or more files;

a users table to identify individual users;

a folders table to identify where each said report and said file is located, wherein said folders table is self-referential;

a parentgroups table;

a groups table; and

a permissions table, wherein said folders table is related to said files table, said reports table, said users table, said groups table, and said permissions table, and wherein said users table is related to said reports table, said files table, said folders table, and said permissions table, and wherein said groups table is related to said parentgroups table, said users table, and said permissions table;

loading a user-client on a computer, said-user client providing an interactive interface to a user;

executing a recursive load function to organize the folders and subfolders of said database in a hierarchical manner, said recursive load function also loading the contents of each said folder; and

displaying said hierarchically organized folders via said user client, such that the user of said user client is able to navigate said folders with an input device.

17. The recitation of claim 16, further comprising:

limiting access to the folders according to one or more preferences associated with said folders stored in said permissions table.

18. A database comprising:

a first table maintaining a first username field, said first table being self-referential;

a second table maintaining a second username field, and first groupID field;

a third table maintaining a second groupID field;

wherein said first and said second tables are related to each other by said first and second username fields, and said second and third tables are related to each other by said first and second group ID fields.