MXPA01001195A - Resource and project management system. - Google Patents

Abstract

The present invention relates to a deployment system for maintaining access and archiving of digital assets. The system integrates administrative functions of image and file with storage of information about files and images. In addition to providing access to the graphic assets themselves, the system also associates all assets with other information where the user can track completed work and define new projects. Later information of the system is stored in hierarchy of data that is complementary to the natural business processes

Description

SYSTEM OF ADMINISTRATION OF RESOURCES AND PROJECTS The present invention relates in general to the administration of projects in the development of graphic images and in particular in the monitoring and administration of projects of brand identification in the development of graphic images for the packaging of products within the industry of pre-press Background of the Invention There are a variety of software products designed specifically to manage a wide range of file formats. Aldus Fetch was the first product of this type to appear and was to be used on an Apple MACINTOSH computer. It was designed to catalog a variety of images and file formats such as EPS, TIFF, Adobe ILLUSTRATO, and other proprietary and non-proprietary file formats. Another previous product is Kudos Image Browser. This product was much easier to use, but it did not have as many applications as Aldus Fetch. Both products could manage files for an individual user or for a small group of users, but they did not expand to a work group or to a company adequately, much less to a company.

CUMULUS was a product designed to solve the inefficiencies of Aldus Fetch and Kudos Image Browser and represented the beginning of a new generation of image management products. Cumulus used a client / server architecture to expand the management of images within a workgroup and a company. Instead of opening a file on a local hard drive that stored all the image management information, the Cumulus software client connected to a database hosted by the Cumulus software server. Cumulus also provided a hierarchical structure of keywords to facilitate the organization and management of keywords used to describe images. Although Cumulus made it easy to share this image information with a complete company, its execution was degraded as the number of images in the database increased.

All the aforementioned products use their own database strategies. This makes these products very difficult to integrate with other products due to the inability of a user to obtain the information stored directly. These products also concentrate too much on the archives. In other words, these products can only catalog files, generate previews and extract specific data from files, such as creation date, file type, file size, etc. The products had no way of storing production information relating to such files such as: information regarding the jobs in which the files were used, or what fonts, faces and images were used to create the application files. In practice, this information or information is the most important.

The next generation of image management products incorporated pre-press workflow management tools. This class of products included: Architype Media Bank and Media Assets. These products continued to use proprietary database technologies, but incorporated workflow improvements to facilitate pre-press production, especially in the catalog market. These products, however, were very expensive. Additionally, these products were aimed at the catalog production market that does not use the same software tools as the packaging market.

Another unfavorable aspect of such products is that they must be consistent with the pre-press workflow management. This offers very little flexibility for an industry that is so strongly influenced by rapid changes in technology.

Finally, the last class of image management products is based on open standards technologies. North Plaines Systems Telescope and Imation's Media Manager are two products that fall into this category. The main characteristic that differentiates these products is that in addition to storing information of the file such as the name of the file, the size of the file, the type of file, the creation date, etc. They also have fourteen areas of information that can be adapted to personal needs. Both prts store the file information and personal fields in an SQL database such as Microsoft SQL Server or Oracle. This allows direct access to the database with custom applications or database reporting tools such as Crystal Reports or Microsoft Query. This also allows the delivery of the file information from a Network browser.

Despite the opening of the Media Manager and Telescope standards, these products are still limited in one area. All are products focused on the files. In other words, to be able to put data in the database, you must first catalog a file. Unfortunately, there is a substantial amount of information about the information that exists before the creation of a file and independent of the file.

The invention in question is aimed at solving the problems of the previous products. The present invention uses a standard "relational" database but increases the functionality of existing programs by creating database structures that can store information information without requiring the presence of a file or image. This invention also provides an advanced security model. Additionally, it allows the use of APIs (Interphase Programming Applications) that allow third parties to carry out personalized searches or functions that act on the contents of a shopping cart.

The present invention also allows an unlimited number of personalized information, in the areas of brand, product, work, project, file, event, and user areas of each one within the database. The invention also implements a distributed file management approach. This means that the files are not stored in the database but the database keeps a record of the file on the server where the file resides. As a result, the files can be located on a computer or on a computer network anywhere in the world.

Finally, the invention is a workflow tool designed to manage a complete production process from the conceptualization of the product and design to the production of pre-press, and the conversion of printed packages and promotions using common terminology. These advantages, and others contained within the specifications indicated here, solve this and other problems.

Description of the Figures.

FIGURE 1 is a functional diagram of the entirety of an operative structure suitable for implementing the present invention and having a demonstration; FIGURE 2 is an illustration of a screen provided in the FIGURE 1 demonstration with an access to navigate; FIGURE 3 is an illustration of a brand hierarchical structure for organizing asset information related to brands, products, jobs and files; FIGURE 4 is an illustration of a hierarchical project structure for organizing production information associated with projects, jobs and events; FIGURE 5 is an illustration showing a work-level intersection between the hierarchies of FIGURES 3 and 4; FIGURE 6 shows a page of a leading brand provided in the demonstration of FIGURE 1 and with connections to sub-brands for a "Consumer Brand" and an "Institutional Brand"; FIGURE 7 shows a page with a list of brands that has connections to sub-brands and that is displayed when the sub-brand connection is selected for the "Consumer Brand" in FIGURE 6; FIGURE 8 shows a page with a list of marks that has connections to submarkets and that is displayed when the connection of sub-brands of FIGURE 7 is selected; FIGURE 9 shows a Product List page with connections to subproducts that is displayed when selecting any of the connections to products in FIGURE 8: FIGURE 10 shows a Product List page with job connections that is displayed when you select any of the the connections to byproducts of FIGURE 9; FIGURE 11 shows a Job List page with connections to events and files that are displayed in response to selecting one of the connections to jobs in FIGURE 10; FIGURE 12 shows a File List page that is displayed as a response to select one of the file connections in FIGURE 11; FIGURE 13 is a High Level Navigation page containing a plurality of objects that is displayed in response to the user selecting the "Navigate" connection of FIGURE 6; FIGURE 14 is a Navigation page in which an object of FIGURE 13 has been expanded in response to the user selecting that object; FIGURE 15 is a Navigation page that shows an expansion of an object of FIGURE 14 in response to a user's choice; FIGURE 16 is a Navigation page that shows the expansion of an object in FIGURE 15 in response to a user's choice; FIGURE 17 is a Navigation page that shows the expansion of an object in FIGURE 16 in response to a user's choice; FIGURE 18 is a Navigation page that shows the reduction of an object of FIGURE 17 in response to the choice of a user; FIGURE 19 is a Navigation page that shows the expansion of an object of FIGURE 18 in response to the choice of a user; FIGURE 20 is a Search page for accepting a plurality of search criteria that are displayed in response to the user's choice of the "Products" connection of FIGURE 6; FIGURE 22 through 24 illustrate the search criteria based on the Search page of FIGURE 20; FIGURE 25 through 26 illustrate the sample criteria supported by the Search page of FIGURE 22; FIGURE 27 illustrate an example of a search using the Search Page in FIGURE 20; FIGURE 28 shows a List of Searched Products that are displayed as a result of selecting a "Search" connection within the Search page of FIGURE 27; FIGURE 29 through 34 are Advanced Search pages that are displayed at least in part, in response to selecting an "Advanced" connection within the Search page of FIGURE 20; FIGURE 35 is a Detail page that is displayed as a result of a user's choice of an object shown on another page; FIGURE 36 is a Brand Edition page that is displayed as a result of a user's choice of the "Edit" connection within the Details page of FIGURE 35; FIGURE 37 is an Attributes List page that is displayed as a result of choosing a user of the "Asset Attributes" connection; FIGURE 38 is an Attributes Details page that is displayed as a result of the user choosing an attribute from the Attribute List on the page in FIGURE 37; FIGURE 39 is an Attributes Edit page that is displayed in response to a user's choice of the "Edit Attributes" connection on the Details page of the Attributes of FIGURE 38; FIGURE 40 is a Add Properties page that is displayed as a response to a user's choice of the "Add Properties" connection on the Details page of the Attributes of Figure 38; FIGURE 41 is a Delete Properties page that is displayed in response to the user's choice of the "Delete Property" connection on the Details page of the Attributes of FIGURE 38; FIGURE 42 is an Add Attributes page that is displayed as a user response when selecting a "Add Attributes" connection on the Assets Attributes page of FIGURE 37; FIGURE 43 is another Add Attributes page that is displayed in response to the user's choice of the "Search" connection in FIGURE 42; FIGURE 44 is a "Add New Attribute" page that is displayed in response to the user's choice of the "New Attribute" connection in any of FIGURES 42 or 43; FIGURE 45 is a "Delete Attribute" page that is displayed in response to the user's choice of the "Remove Attribute" connection on the Attributes page of the Assets of FIGURE 37; FIGURE 46 is a "Contact List" page that is displayed in response to the user's choice of the "Contact" connection on the Details Page of FIGURE 35; FIGURE 47 is a data table provided by the "File List" page of FIGURE 12 in which selections were made by the user; FIGURE 48 illustrates a "Primary Car Contents" page displayed in response to the user's choice of the "Shopping Cart" connection in FIGURE 12; FIGURE 49 is a "Carriage List" page that is displayed in response to the user's choice of the "Carriages" connection in FIGURE 48; FIGURE 50 is a "Add to Cart" page that is displayed in response to the user's choice of the "Add to Cart" connection in FIGURE 49; FIGURE 51 is an illustrative page of the "Car List" that is displayed in response to the user's choice of the "Add Car" connection of FIGURE 50; FIGURE 52 is a "User's Car Content" page that is displayed in response to the user's choice of a user's car connection in FIGURE 51; FIGURE 53 is a "Upload the Files in a User's Car" page that is displayed in response to the user's selection of the "Upload" connection in FIGURE 52; FIGURE 54 is a "User's Car Content" page that is displayed in response to the user's selection of a "Upload Files to User's Car" connection in FIGURE, 53; FIGURE 55 is a "Project List" page that is displayed in response to a user's choice of the "Projects" connection in FIGURE 6; FIGURE 56 is a "Add Project" page that is displayed in response to the user's choice of the "Add Project" connection on the "Project List" page of FIGURE 55; FIGURE 57 is a "Project Details" page that is displayed in response to the user's choice of connection details of the project on the "Project List" page in FIGURE 55; FIGURE 58 is a "List of Events" page displayed in response to the user's choice of the "Events" connection on the "Project Details" page in FIGURE 55; FIGURE 59 is a "Project Edition" page that is displayed in response to the user's choice of the "Edit" connection on the "Project Details" page FIGURE 57; FIGURE 60 is a "Contact List" page that is displayed in response to the user's choice of the "Contacts" connection on the "Project Details" page of FIGURE 57; FIGURE 61 is an "Event Details" page that is displayed in response to the user's choice of a connection to the name of an event on the "Event List" page of FIGURE 58; FIGURE 62 is an "Input" page that is provided in the sample of FIGURE 1 when the user wants to enter the system; FIGURE 63 is an "Administration" page provided in response to the user's choice of the "Admin" connection. which can be provided on the "Highest Level" page of FIGURE 6; FIGURE 64 is a "Company List" page provided in response to the user selection of the "Companies" connection on the "Administration" page of FIGURE 63; FIGURE 65 is a "Add Company" page that is provided in response to a user's selection of the "Add Company" connection on the "Company List" page of FIGURE 64; FIGURE 66 is a "Company Details" page provided in response to the user's selection of a connection with the name of a company from the "Company List" page of FIGURE 64; FIGURE 67 is a "Edit Company" page provided in response to the user's selection of the "Edit" connection on the "Company Details" page of FIGURE 66; FIGURE 68 is a "Company Contact List" page provided in response to the user's selection of the "Contacts" connection on the "Company Details" page of FIGURE 66; FIGURE 69 is a "Contact Details" page provided in response to the user's selection of the contact's name on the "Company Contact List" page of FIGURE 68; FIGURE 70a and 70b is a "Edit Contacts" page provided in response to the user's selection of the "Edit" connection on the "Contacts Details" page of FIGURE 69; FIGURE 71a and 71b is a "Add Contacts" page provided in response to the user's selection of the "Add User" connection on the "Company User List" page of FIGURE 72; FIGURE 72 is a "Company User List" page provided in response to user selection of the "Users" connection on the "Company Details" page of FIGURE 66; FIGURE 73 is a "Group List" page provided in response to the user selection of the "Groups" connection on the "Administration" page of FIGURE 63; FIGURE 74 is a "Group Details" page provided in response to the user's selection of the connection group details from the "Group List" page of FIGURE 73; FIGURE 75 is a "Edit Group" page provided in response to user selection of the "Edit" connection on the "Group Details" page of FIGURE 74; FIGURE 76 is a "Table of Codes" page provided in response to the user selection of the "Code Table" connection err on the "Administration" page of FIGURE 63; and FIGURE 77 is an "Entry List" page provided in response to the user's selection of the "Inputs" connection on the "Administration" page of FIGURE 63; FIGURE 78 is a "Insurance List" page provided in response to the user's selection of the "Insurance" connection on the "Administration" page of FIGURE 63.

Description of the invention Although the present invention can be presented in many different forms, the preferred form of presenting the invention has been shown in the drawings and will be described in detail with the understanding that the present disclosure should be considered as an example of the principles of the invention. invention and is not intended to limit the broad aspect of the invention only in the illustrated embodiment.

The present invention provides a system for keeping track of and managing projects for the development of graphic images for the packaging of products within the pre-press industry. The present invention also provides a system for asset management used in the development of graphic images for the packaging of products.

A sample of the present invention can be described in the form of a system employing a server with a communication software 11, client software system 12, and an SQL database 13 each operating on computers 15, 16 , 17 in a computer network 19, as shown in FIGURE 1. The server with communication software of the preferred presentation can be any server that is capable of an http (hypertext protocol transfer) connection, such as the server with software for communication sold by Microsoft, Inc. or Netscape, Inc., The client software of the preferred presentation can be any software capable of an http connection. However, since the presentation incorporates frames and codes written in JavaScript, a client software capable of displaying HTML (language with hypertext marks) that incorporates frames and JavaScript such as Microsoft Internet Explorer v.4.0 and higher or Netscape Navigator v3 is required. 0 or higher The client computer 15 includes conventional connection mechanisms 14 and a screen 18. The connection mechanisms 14 can include a conventional keyboard and a mouse to allow the user to select the objects that appear on the screen 18. The screen 18 can be a screen conventional with cathode ray tube or any other suitable mechanism that provides the user with a visual sample.

The presentation that we are considering allows flexibility in the installation options. The user of the present system could operate and maintain the communication server and the SQL database on its own or could use the communication server and the SQL database of a specialist who has the training and resources necessary to maintain the system .

Additionally, and as the computer code of this presentation resides on a communications server, the software is easily updated when improvements are made to the system. This eliminates the need to update the software on each computer running the system. Also, due to the high level of availability of the client's software, the system can be operated from any computer in almost any place in the world without installing the client's special software as long as the communications server is located in a wide network such as the Internet. However, the computer code can be loaded onto the platform of a removable media such as a compact disc (CD) or similar.

The present invention preferably stores user data in a hierarchical manner. This means that instead of placing all the information (images, attributes, lists of events) within a single large container, the information is organized and stored in a tree structure whose complexity varies with the complexity of the stored products. Preferably, two hierarchies of simultaneous data work - a hierarchy of brands and a hierarchy of products - each of which offers a different point of view of the information. This structure not only provides an efficient method for organizing information but also mimics the relationships found in standard business cycles.

With respect to FIGURE 2, the illustration of a screen that provides an interface for a user is shown. In the presentation, all screens selected by the user are displayed in visual form 18 (FIGURE 1) and have the same basic structure within the present invention with each screen 20 including a search frame 21, a control frame 22, a data frame 23. Accordingly, frames 20, 21, 22 are displayed together on screen 18 by client software 12. The words "screen" and "page" as used throughout this application are they will understand referred to frames 20, 21, 22.

Underlining the words in FIGURE 2 indicates that the word is a hypertext. Hypertexts can be selected by using mechanisms 14 (FIGURE 1) such as the mouse or keyboard connected to the computer running the client's software. In this disclosure, the terms "selecting" and "selecting" will mean selecting a hypertext with the mouse or keyboard. When selecting a hypertext, the user activates some function of the system. The search frame 21 of the screen 20 provides access to search functions that can be performed by selecting one of the buttons 24. The search frame 21 also provides context to the application by indicating the area in which it is located. working the user. For example, the area can be indicated by shading a button.

The control frame 22 contains links or connections 26 that represent the operations to be performed. The control framework 22 is sensitive to the context accordingly the changes are based on the area of the application in which the user works. In the upper part there are connections 26 that depend on the contents of the data frame 23. Below these, there are connections that can be shown in different colors and that apply to the entire application. These connections are not context sensitive and are preferably available at all times. As shown in FIGURE 2, the control frame 22 may include a connection 29 which when selected shows all the images associated with the selected objects shown in the data frame 23.

The data frame 23 is the main body of the page 20. The data frame 23 contains information with which a user works at that time. Consequently, the results of any operation performed are shown in the data frame 23.

Preferably, each user of the system has an account through which he or she can access the applications of the system. The account of a user preferably contains information about the user including the connection identity, secret key and email address. This information can be obtained by selecting the "User Information" button 49 on the control screen 22.

In the presentation, users can modify at least some information of their account. For example, users can update their email address or phone number when that information changes. Preferably the only values of the user's account that the user can not change are the connection identity and the name of the company. However, it is desirable that the asset manager can modify these values.

As can be appreciated by those with knowledge in the area, the brand hierarchy is asset-oriented. Its purpose is to create a structure to logically organize the asset data associated with the brands, products, jobs and files shown in FIGURE 3. In this example, the "Krunchy" brand 31 has two product lines 32a, 32b: " Pretzels "and" Papas ". As there is a variety of "Pretzels" the hierarchy goes directly from the 31 mark to the 32a product to the 34a job (ie "Work 206") · However, since there are three varieties of "Popes", the hierarchy goes from brand 31 to product 32b to subproduct 33a to work 34b (ie "Work 226"). A brand hierarchy 30 can have as many levels of brands 31, sub-brands, products 32 and sub-products 33 as are necessary to properly organize their content.

Returning to see the example of FIGURE 3 and descending in the hierarchy 30, both the product "Pretzels" 32a and "Popes" 32b have jobs 34 associated with them. Each job 34 has a series of files 35 associated with them that are used to produce the work.

The product hierarchy is production oriented. Its purpose is to create a structure that organizes the production information associated with the projects, jobs and events as shown in FIGURE 4. In this example, the "Winter Promotion" project 37 contains two jobs 34b, 34c, each of which contains a series of events 38 that must be done before the job is finished The project also contains a series of events 39 that belong to the project itself. Like the brand hierarchy 30, the product hierarchy 36 can be divided into as many levels of organization as necessary. Each project can contain different levels of sub-projects before specifying the list of required jobs and events.

As shown in FIGURES 3 and 4, the "Krunchy" brand hierarchy 30 and the "Winter Promotion" hierarchy 36 contain "Work 226" (i.e. reference number 34b). This is because the two hierarchies are interrelated at the work level.

The works can be located both from an asset perspective and from the production perspective. From the perspective of assets, a job is the set of data -elements- required- the files. From the perspective of production, a work contains a series of steps that must be carried out from the beginning to the end - the events. As papers have this double perspective, they are included in both hierarchies and present a place to move from one hierarchy to another. FIGURE 5 shows the interconnection at the work level between the hierarchies of FIGURES 3 and 4. "Work 226" (ie, reference number 34b) is part of both "Winter Promotion" project 37 and the "Krunchy" brand. 31. When looking at the events associated with "Work 226" 34b, a user observes the work from the perspective of the project; when looking at the files associated with the work, a user observes the work from the perspective of the project. The user can access "Work 226" 34b by descending in any of the two hierarchies. And the user can have access to both events and the files associated with the work regardless of the hierarchy he or she uses to descend. This double hierarchy, which is interrelated at the work level, is represented by the buttons in the Search frame 21 in the user interface 20 as explained in more detail below.

As mentioned above, the present invention utilizes three main functional areas: 1) brand management or assets, 2) project management, and 3) file exchange. In the presentation, this invention also provides an administrative function for configuring system parameters and security.

Brand management allows the user to maintain and organize the files associated with specific brands and products. As indicated previously, a brand is a family of products. A brand can contain more brands that are distinctive within a family of products. Eventually, a brand or sub-brand may contain at least one product. Within a particular product there may be more products. Eventually, however, a product or by-product may contain at least one job. Jobs contain files that must be associated with a job and / or event that must occur during the job. The files are the design elements of the packaging of a product. A file can be an image, a type of letter, a document or any other design element. The events are associated with the process of designing the packaging of a product and will be explained in more detail in conjunction with the product management function. Brands, products, works, archives and events are generally referred to as assets or objects. As for example within a brand there may be different types of assets, such as sub-brands or a product, the contents of an asset will sometimes be referred to in general as a sub-asset.

The marga administration section organizes and displays four main types of information: 1) list of sub-assets, 2) contact maintenance functions, 3) brand and asset search functions, 4) asset maintenance functions. The brand management section also provides a simple connection to the events associated with a particular asset.

Preferably, there are three methods to locate information in the database system: view, browse and search. The method selected depends both on the type of data to be located and on the knowledge the user has of the data.

The method of seeing allows the user to proceed level by level either through the brand hierarchy or the project hierarchy to observe the contents of the hierarchy in each level. Seeing is conceptually similar to using a network browser. Just as one would choose a site and then focus on the desired information by selecting the appropriate links, see or search allows the user to choose a part, then a product under it, then a job and finally a file or event when selecting the links to reduce the field. Each time the user selects a link to navigate further in the hierarchy the contents of the data frame 23 are replaced with new information. Search or view is context-oriented and is a desirable method if the user determines that it is useful to observe detailed descriptions of the objects while the user descends in the hierarchy.

The method of navigating allows the user to observe an overview of a complete brand hierarchy and then focus on a particular level of objects. Browsing is conceptually similar to using the MACINTOSH SEARCHER OR THE MICROSOFT WINDOWS EXPLORER. In any of these applications, the user selects the expansion icon next to any folder to see the list of its contents. Likewise, when navigating using this invention, the user selects an icon to view the content of the brands, sub-brands, products, sub-products, and works in a summary format. Each time a user selects, the summary expands while the content of the previous summary is maintained in the data frame 23. Browsing is relationship oriented and is a desirable method if the user does not need graphic information or if the user wants Understand the general structure of the system database and observe how the different objects relate to each other.

The search method allows the user to locate an object or a series of objects that satisfy a particular set of criteria. Searching is conceptually similar to using a web-based search tool.

Just as a user would use a network search tool to locate "pages containing information on digital prepress" the search in the present invention allows the user to locate "the files associated with the works on the X Mark that were made in January of this year. " Search is criterion-oriented and is a desirable method if a user does not remember in which part of the data hierarchy an object is stored or if the user wants to locate multiple objects that are not stored together in any data hierarchy.

As mentioned previously, viewing allows the user to locate an object when descending on a particular brand or in a brand or project hierarchy when examining its content. At each level, the user can choose to continue further or examine detailed information about the objects. Each time a user requests new information, the data frame is updated.

The following shows steps to see the brand hierarchy in a database entitled - the "Junk Food" database. Of course the user database will contain different information and the following is only for illustrative purposes to show the capacity of a search tool.

After entering the system, a high-level page of marks 40 as shown in FIGURE 6 is provided by the system. At the top of page 40 is the search frame 21. In addition to providing access to the search tools, the search frame 21 shows the context of the application, indicating the area of the data hierarchy that is currently used by the user. For example, the "Marks" buttons 25 are shaded in FIGURE 6 whenever the marks are being viewed.

At the top of the data frame 23, the title on page 41 indicates the type of objects that are being viewed. For example, the "Brand List" is indicated in FIGURE 6. The "Junk Food" database used in this description is designed in such a way that high-level brands are categories instead of real brands. This allows the information of brands and products to be organized by the sectors of the industry or products that exist. For illustrative purposes, there are two high-level brands in the "Scrap Food" database: "Consumer" and "Institutional".

Below heading 41 is the road search 42. The road search shows levels of the hierarchy that form a path to the current objects and allow the user to return to any level by selecting a link or connection. The route finder 42 is described in detail below.

Below the way finder 42 is the sample register 43. The sample record allows the user to display the next group of records if more records are obtained than can be displayed on the screen at one time. The number of records displayed is defined by a system format and may vary for the list, and contact sheet views. For example, if the list sample format is programmed for "5 records" and the database contains 20 marks, the sample record would initially indicate "Show records 1 to 5 of 20 records found." Using register 43, a user can see the records from 6 to 10 and from 11 to 15 and so on.

At the bottom of the page is the data table 44. The data table lists all the objects in the hierarchy at this level and provides columns 46 of information about each object. When selecting the header of a column of data table 47, the table is displayed, alphabetically or numerically by column. The arrow 48 next to the name of the column indicates whether the column has been revised in ascending order "i" or descending "!".

The content of the data table 44 varies depending on the type of object that is being searched. For example, a brand shows a series of columns and a job shows a different series of columns. However, the name of object 50, administrator 51 and list 52 are common columns to many objects in the data table. The column with the name of the object 50 (in the case of FIGURE 6, the "Mark") contains connections 54 denoting the names of the objects. Selecting the name of object 54 shows the detail page of the object, which is explained in detail here, and which provides in-depth information about the object.

The administrator column 51 contains connections 56 denoting the names of persons who can be contacted in reference to the object. When you select the administrator connection 56, contact details are displayed and information about the administrator is provided, including a connection that allows you to send them an email message.

The list column 52 contains connections of sub-assets 58 that represent the sub-assets in the data hierarchy (in the case of FIGURE 6, sub-brands) that are below the current assets. Consequently, selecting the connection list 58 is lowered to the next level in the hierarchy for the selected sub-asset.

Preferably each list connection 58 is a word meaning the type of sub-asset or object that contains the asset, such as "sub-brand", "sub-product" or "product". Accordingly, upon selecting the connection list 58, the data frame 23 is changed to display a screen with assets or objects within the selected sub-asset. For example, by selecting the list 58 of FIGURE 6 for the "Consumer" mark the data frame 23 is changed to that shown in FIGURE 7. The resulting page shows the associated marks (ie sub-marks) below the Consumer brand, for example "Cyber Scrap", cereal "Krispy", and vegetables "Youbetcha". It should be noted that the present invention facilitates that data hierarchies have different levels of brands, sub-brands, products and sub-products. To descend into the hierarchy, within the "Youbetcha" mark you must select the "Sub-marks" list 58 in the list column 52 in the bottom row of FIGURE 7. Select the "Sub-marks" list 58 and the sub -brand "Youbetcha" results in the data frame 23 that changes to show the sub-assets (ie) sub-brands of "Youbetcha" as shown in FIGURE 8. As shown in the list 52 column, "Youbetcha" It has another level that consists of four sub-brands: Super Beans, Super Carrots, Super Maize and Super Chícharos. Depending on the sub-brand that is selected, descending the hierarchy will require the user to use another level of sub-brands or a product level.

When selecting the "Products" list 58 of the sub-brand "Super Maize", next to the bottom row of the table 44, the sub-assets (ie products) of "Super Maize" are shown in the data frame 23 as is shown in FIGURE 9. Title 41 is now shown as a "Product List" and the data frame provides the user with access to the high level "Super Maize" products. In addition, such as the "Trademark List" page (i.e. FIGURES 6-8), the "Product List" contains a data table 44 that lists its content - the available by-products. There are four sub-products under the "Super Maize" mark that contains connections to additional by-products that are shown in the List 52 column of a Product List page.

As shown in FIGURE 10, selecting the "By-products" list connection 58 of FIGURE 9 in the list column 52 of the "Super Mexican Corn" product shows the by-products. This page lists three sub-products under the product Super Maíz Mexicano. Additionally, the products become more specific insofar as they correspond to physical products that may be for sale. Since the products at this level are specific, they no longer have sub-products under them. Instead, they have jobs.

Moreover, some products have product formats in addition to the work. These product formats are used to provide storage for the design of formats associated with the product.

As shown in FIGURE 11, select the "Jobs" list 58 associated with the product "Super Mexican Corn 15 oz." From FIGURE 10 shows a list of jobs under the product. These three jobs are associated with the product "Super Maiz Mexicano 15 oz.". Each work represents a sample of the product label "Super Mexican corn 15 oz.".

In FIGURE 11, title 41 of data frame 23 is suitably changed to "List of Jobs". The data table 44 contains different types of information in addition to brands or products. Instead, the data table includes: job number, job name, job manager, job language, job delivery date, job completion date, and job status.

As shown in FIGURE 11, the work "Super Maíz Mexicano Línea Basic "contains two lists - one that indicates the" events "and one that indicates the" files. "Consequently, in column list 52 a user can select a connection to see either files or events related to a job. "62 takes us one level down in the hierarchy of marks and displays a File List FIGURE 12. Selecting" Events "64 intersects the project hierarchy and the Events List page is displayed.

It should be noted that the intersection of the hierarchy of marks and projects is provided in FIGURE 11 by means of the connection "Files" 62 and "Events" 64. Consequently, a user can move between the two hierarchy at the work level.

As shown in FIGURE 12, select the "Files" list 62 associated with the work "Super Maize Mexican Basic Line 15 oz." FIGURE 11 shows a list of files contained in the work. Title 41 on this page is "File List" and the page lists the files associated with the job and shows the associated software applications, file types, creation dates, and sizes. The work shown in FIGURE 12 has nine files associated with it but only 4 are shown initially in the data table. Using the sample record 43, the user can see the remaining files in the list, first files 5 to 8 and finally file 9.

The first column 66 of data table 44, Car, provides a reference to the user's shopping cart that contains a storage area so that the user can gather files. The icon 68 on the left side of the Car column 66 indicates whether the file is inside or outside the shopping cart. The 70 icon on the right allows the user to move a file in or out of the shopping cart.

It should be noted that the files are in the lower part of the data hierarchy. Since there are no objects or assets in the hierarchy below the files, there is no List column in data table 44 or in the File List FIGURE 12.

As indicated previously, the road finder 42 allows jumping to a different level of the hierarchy. The road search 42 shows the hierarchy of marks from the top of the database (designed by Food Scrap, Inc.) to the current location. Each level is displayed below the previous level, indented and preceded by one of three icons such as the trademark symbol, a cylinder, or a file folder to designate a brand, a product or a job, respectively.

Selecting a connection in the way finder 42 takes us to the page that represents the content of the selected object. When selecting a connection that represents the top level (shown in bold) the Details page, which is explained in detail in the present, for the parent object is displayed.

When selecting the "Consumer" connection in the road search engine, the marks contained in the Consumer category are shown as shown in FIGURE 7 where another brand can be selected to continue to see the brand hierarchy.

As shown above, the present invention allows the user to see the brand hierarchy. The user simply selects the highest level mark to examine and then descends in the hierarchy by selecting the connections in the List columns of the displayed data tables. When you select a brand, product or job name instead of a connection in the List column, the Details page is displayed, which is explained below in detail, at the selected level instead of going down in the hierarchy. The road search can be used to support any level in the hierarchy.

When working in the project hierarchy, the search tool operates in the same way. The user can see the project hierarchy when selecting the Project connection in the Control frame. Once inside the project hierarchy, the user can select a high-level project and then descend from project to sub-project, to work and finally to events by selecting connections from the List column of the resulting data tables. As in the trademark hierarchy, a user can examine the Details page, which is explained later, by selecting the project, sub-project or job name connections.

Navigation allows the user to examine the complete system of the hierarchy of marks on a page, in summary format. By expanding and collapsing the summary the user can examine the relationships between various objects. In the whole, the navigation tool can be used to see the brand hierarchy only and not the project hierarchy.

Again, an explanation regarding navigation in the brand hierarchy is given using the present invention using the same "Junk Food" database. Although the user database will contain different information, this example illustrates the possibilities of the system's navigation tool.

Returning to FIGURE 6, selecting the 74"Browse" button in the frame Control 22 starts the navigation tool and displays the high-level marks as shown in FIGURE 13. At the top of the page is the name of the system database 76 (ie, "Scrap Food, Inc." ). Below the name of the database 76 is a list of all the objects 78 at the top of the mark hierarchy - the high-level marks. Each object 78 shown is represented by a row containing three elements: the sample or expansion icon 80, the object cone 82 and the name of the object 84. The first element in each row is the sample icon 80. If the cone 80 points to the right, the row contracts and no levels are shown below object 78. If cone 80 points down, the row expands to one or more levels below object 78. If it contracts, the The user can select the icon 80 to show a level below the selected object 78. If it is expanded, the user can select the icon 80 to collapse all the levels below the selected object 78.

After the sample cone 80 is the object cone 82. The object icon is used to designate, when looking, the type of object 78 that represents the row in which: the trademark symbol designates a mark, a cylinder designates a product, and a file folder designates a job.

After the cone object 82 is the name of the object 84 that identifies the object. If the name of the object 84 is shown as a hyperlink, then the object's Details page is displayed when the connection is selected.If you select the sample icon 80 that precedes the brand "Consumer" shows the sub-brands below the Consumer category as shown in FIGURE 14. In this example, there are three brands shown below the Consumer category: "Cybernetic Snacks", "Krispy" cereals and "Youbetcha" vegetables .

Selecting the sample cone 80 that precedes the "Youbetcha" mark shows the sub-marks below it as shown in FIGURE 15. In this example, there are four sub-marks shown below the " Youbetcha ":" Super Frijoles "," Super Carrots "," Super Maiz "and" Super Chícharos ".

Selecting the sample cone 80 that precedes the "Krispy" mark allows the user to examine that part of the mark hierarchy as well. As shown in FIGURE 16, the summary expands to reveal two sub-brands below the "Krispy" brand. The "Krispy Flakes" brand can continue to expand to reveal its content because there is a sample cone. However, since the "Krispy Puffs" brand has no objects below it in the hierarchy, no sample cone precedes it.

By expanding and collapsing several objects, the user can examine more of the objects in the hierarchy below the "Youbetc a" mark. Consequently, browsing presents a different image of the brand hierarchy than looking. On a single page, a user can not only locate a particular object but also compare objects. For example, as shown in FIGURE 17, the product "Super Corn Cheese" has a single size but "Super Mexican Corn" has three and "Super Mexican Corn" is the only product with a coupon work of $ 0.20.

Upon contracting the sample icon that precedes the product "Super Mexican Maize" all levels below it are hidden as shown in FIGURE 18. As such, said contents of both the product "Super Maiz Mexicano 15 oz." And "Super Maíz Mexicano" are hidden.

As shown in FIGURE 19, if the product "Super Maíz Mexicano" is expanded again, only one level is shown below it, although two levels were shown before it was contracted. As such, it is preferable that when contracting an object the levels below it contract, but when expanding an object, only one level is displayed below it.

It should be noted that while browsing, the present invention preferably allows the user to jump to the look mode at any level of the data hierarchy when selecting the name of an object. As a result, doing so opens the Details page for the selected object, which is explained later.

The above shows the navigation in the brand hierarchy. In summary, navigation starts when you select the Browse button in the Control frame. Once the Navigation page is displayed, the user can expand or collapse the object summary by selecting the sample icons - to expand, to contract. Objects that are not preceded by a sample icon do not have objects below them in the hierarchy. By expanding e! summary an additional level is displayed below the selected object. When the summary is collapsed, all levels are hidden below the selected object.

Preferably, the first time the user chooses the Browse button, high-level marks are displayed in the data frame. If the user expands various objects, leaves the Navigation page without disconnecting and then returns to it, the system remembers the status of the data frame when the user last navigated and displays it in that state. Consequently, if a user has expanded multiple objects, choosing to see another object on the Details page does not mean that the user will have to re-expand everything when they stop browsing.

Search allows the user to locate an object or set of objects that meet a certain description. By specifying the search criteria - a set of attributes and properties that characterizes these objects, makes up the description. A user can search for any type of object (brand, product, work, file, event or project).

Search provides a method to use when: the user does not remember where in the data hierarchy an object was stored, when the user knows where the object is stored and wants to find it quickly, or when the user wants to locate multiple objects that are not stored together.

The following example shows how to search for a product in the system database illustrated above - the "Junk Food" database. Although the user database may contain different information, the following illustrates the possibilities of the system search tool.

Returning to FIGURE 6, if the "Products" button 90 is selected in the Search 21 frame, the Product Search form 92 shown in FIGURE 20 is shown. The search form contains controls that allow the user to define the search of the user - both the criteria to search and the way in which the search results will be displayed.

The search criterion 94 includes a set of projections 96 and text boxes 98 with which the user can specify the characteristics of the objects to be located. The projections 96 are shown when a selection of a set of valid options must be made. Text boxes 98 are displayed when any value can be entered.

The sample criteria 100 includes a series of projections 102 with which the user can indicate how to display the search results. A user can sort out the results by various attributes in ascending or descending order and the user can display the results in several ways depending on the type of object the user is looking for. For example, products can be displayed as lists (similar to the Search data table page) or brands (small graphic representations).

When a Search page is opened, the "Search" button 104, the "Advanced" button, and the "Restart" button 108 are added to the Control 22 frame. By selecting the "Search" button 104 a search is performed using the search criteria shown 94. Selecting the "Reset" button 108 replaces all modified criteria with their preset values. Selecting the "Advanced" button 106 displays the "Advanced Search" page in which more complex search criteria can be defined. In a presentation, if the Advanced Search page is displayed, the button on the Control frame 106 can read "Simple" instead of "Advanced".

The search criteria are defined by an attribute (value to be reviewed), an operator (type of comparison to be performed) and a limit value (value against which the attribute is checked). If a criterion is unnecessary, the user can select the operator ("Any"). This causes the entire criterion, including any value integrated into the text box of limiting value, to be ignored.

The search criteria 94 includes a "Product" criterion 110 that allows the user to search by product name or product number. As shown in FIGURE 21 a user may select either "Name" or "Number" of the first projection 96. The user then selects an operator of the second projection such as ("Any"), "Is", or "Start With". Finally, a user enters a limiting text box of value 98. By using these options the user can define several criteria of product types, for example, "Product Name contains corn" or "Product Number starts with 3".

The search criteria 94 of FIGURE 20 also includes the criterion "Mother Product" 112 that allows the user to specify the type of mother objects that the found objects must have. Preferably, only the types of mother objects that are valid for the type of object that the user is locating are shown. As shown in FIGURE 22, a user can select the type of mother object (ie, Brand or Product) and attribute (ie, Name or Number) of the first two projections 96. Then, the user selects an operator of the Third projection 96 such as ("Any"), "Is", or "Start with". Finally, the user enters a text box of value limitation 98. Using these options, the user can define several types of mother criteria, for example, "The Mother Mark is Youbetcha", or the "Product Name Father contains botana " The search criterion 94 of FIGURE 20 further includes a "Market" criterion 114 that allows the user to specify products of certain markets that must be included or excluded from a search. As shown in FIGURE 23, a user may select an operator of the first outgoing 96, either Is "to include" Is Not. "Then the user selects a market of the second outgoing 96 such as (" Any ") , "Northwest", "Southeast." Using these options, the user can define several types of market criteria, for example, "The Market is Southeast" or "The Market is not Northwest".

Returning to FIGURE 20, the search criteria 94 also includes a "Text Note" criterion 116 that allows the user to search for products that have a specific word or phrase in their notes. Returning to FIGURE 24, a user may select an operator of projection 96 such as "(Any)", "Starts With" or "contains". Then, the user enters the text to be searched in the text box 98. Using these options a user can define several types of criteria of text notes, for example, "Text Note contains modifications" or "Text Note Ends with end " The sample criterion 110 of FIGURE 20 includes a "See" criterion 120. The "View" criterion has no effect on the determination of the objects to be found. However, if a value is specified for the "View" criterion 120, the way in which the results are displayed at the end of the search is determined. As shown in FIGURE 25, a user can select "List" from projection 96 to display the search results as a simple list of object names. In addition, a user can select "Graphic Representation" of the outgoing 96 to include graphic representations of the results.

Preferably, if a user is looking for the objects in a file, the value of the Contacts Sheet is added to the outgoing criterion, allowing the user to view the files as part of the contact sheet.

The criterion of sample 110 of FIGURE 20 also includes a criterion "Circumventing By" 122. As shown in FIGURE 26, the first protrusion 96 of the criterion "Circumventing By" 122 allows the user to select the value for which the results will be drawn such as "Product No." "Product Name" "Administrator" or "State". The user can also select the draw order either ascending or descending from the second outgoing 96. Using these options a user can sort out the results in various ways, for example, "Sort By Administrator in ascending order" or "Sort by Number of Product in descending order. " As shown in FIGURE 27, a user can specify the criteria to find all the products under the "Youbetcha" brand that contain the word "Mexican" showing the results listed in alphabetical order, by name. This is achieved, first, in the "Product" criterion 110, by selecting a "Name" of the outgoing attribute, by selecting "Contains" from the outgoing operator 96, and writing "Mexican" in the text box. Then, in the "Mother Product" criterion 112, the user selects "Brand" and "Name" of the attribute projections, selects "Starts With" from the outgoing operator and writes "Youbetcha" in the text box. Then in the criterion "Sort by" 122 the user selects "Product Name" and "Ascending" of the outgoing.

It should be noted that by selecting the operator "(Anyone)" in the "Market" and criteria "Text Note", a user indicates that the products to be located can be in any market and have any text in their notes.

Once the criteria are defined, a search is performed by selecting the "Search" button 104 in the control frame 22. The system searches the database for products that meet the criteria and then displays the results. The time required to perform the search depends on the complexity of the search criteria and the amount of information stored in the System's database. The results of the search are displayed on the Product Search List page 124 as shown in FIGURE 28. If no objects meet the search criteria, the page contains a message indicating that no objects were found. Otherwise the page contains the resulting objects, If more objects are found than can be displayed at one time, the sample record 43 can be used to view additional records. For example, if the user's criteria is applied to 60 products, the page may say "Display records from 1 to 10 of 60 records found." Using the projection 43, the user can see each group of 10 subsequent objects.

Data table 44 lists all found objects. When selecting the header in the data table column 47, draw the table by that column 46. The arrow 48 next to the name of the column indicates if it is drawn in ascending or descending order.

Within the Product Search List, if the column is selected "Product Name" 126 shows the Product Details page, which is explained in detail below. Additionally, if a connection is selected in the Administrator 51 column, the Contact Details page for the administrator is displayed. Also, if a connection is selected in the List 52 column, it takes us one level further down the hierarchy of marks and the objects under the product are shown in case of jobs FIGURE 28. If the user is not satisfied with the search results - whether you obtained too few or too many records - the user can perform a new search by refining the search criteria as described in the next step.

In its entirety, the previously defined search criteria can be modified by selecting the "Products" button 90 in the search frame 21 to reopen the Product Search page of FIGURE 27. The Product Search page contains e! criteria previously selected by the user because the system remembers preferably the last selected search criteria for each type of object. Even if a user exits and re-enters, the system displays the user's previous criteria each time the user reopens a Search page.

Modifying the search criteria allows the user to expand or reduce the scope of the search. If a user's previous search yields too many results, the user can reduce the search by adding more criteria - a user can specify Market criteria or specify the name of the product (for example Frozen Mexican). If a user's previous search yields very few results, the user can expand the search by eliminating or making the criteria less specific - the user can eliminate the Mother Product criterion. If the user's previous search yields erroneous results, the user can use the Restart button to clear the criteria and start over.

The above describes the way to locate an object using the search tool system. In summary, a user can start searching by selecting the button of the Search frame that corresponds to the type of object that the user wants to locate, for example a project or a job. As a result, the Search page opens with criteria that are appropriate for the type of objects selected. On the Search page, a user defines the search criteria that distinguishes the objects that the user wants to find. The criteria are defined by specifying an attribute, an operator, and a limiting value. If a user does not want to search by a particular type of criteria, the user selects the operator ("Any") and the criteria is ignored. A user can also define the sample criteria to control how the results should be displayed. Once the criteria are defined, the user selects the Search button in the Control frame to perform the search and display the results. If a user wants to refine the search just made, the user selects the same search button again. The system remembers the previously defined search criteria. The system can also include an Advanced Search feature that contains more complex search criteria.

In one example, the Advanced Search can be activated by selecting the "Advanced Search" button 106 whereby the search format 88 FIGURES 29 and 30 is shown providing a more advanced search for brand data. Although the format 88 of advanced brand search, contact data, modification data, and sample options can be made to find brands that meet the search criteria rsted by the user. Also, an advanced job search form 93 (FIGURARS 31, 32, 33 and 34) that is provided to search for job information, job codes, contact information and modification information.

As indicated above, each object of the system - brands, products, jobs, files, projects and events - can be seen on the Details page that provides in-depth information about the object. However, because the information stored for each type of object is different, the contents of the Details page vary depending on the type of object. An Details page is displayed when selecting the connection that represents the name of the object. The path a user takes to get to the connection does not matter. For example, a user can display a Product Details page: by viewing a Product List page, then selecting the name of a product listed in the data table; expanding the navigation summary to show the desired product and then selecting the connection with the name of the product; search for a particular type of product, and then selecting the connection with the product name on the Search Results List page.

FIGURE 35 shows for example a page of Work Details 132 that shows detailed information about an object. AND! number, type and contents of the areas on a Details page varies with each type of object examined.

Preferably any value shown as a connection can be selected to see more details. For example, on the Work Details page displayed, if the user's name is selected, their Contact Details page is displayed; if the Coloring connection is selected, a Coloring Detail page is displayed. Selecting the connection (more ...) next to the name of a Letter Typography shows a list of types of letters. If the user has * the appropriate security permissions, then the user can modify the 'contents of the areas on the Details page of an object.

When a Details page is displayed, buttons are added to the Control 22 frame that correspond to the operations that the user can perform with the objects. The available operations and consntly the buttons shown differ according to the type of object.

Once a user has finished examining the Details page, the user can jump to another level in the data hierarchy using the path finder or by selecting a button in the Control frame to perform a new operation.

With the appropriate security permission, a user can edit the areas on the Details page. In one example, the control frame 22 of the Details page 132 may include the "Edit" button 133. When an asset is displayed in the data frame 23, selecting the "Edit" button 133 causes the system to display a format of editing assets 109 in the data frame 23 as shown in FIGURE 36. In the form of editing assets 109, the number of assets, the name of the assets, type of assets, status of the assets and notes of the assets It can be changed. After editing all or part of the asset data, a user can choose to save the changes by selecting the hypertext. Although the asset shown in FIGURE 36 is a brand, it is understood that any asset can have its associated data edited in this way.

The control frame of the Details page can also include a hypertext of asset attributes that allows the system to display an attribute list screen 140 as shown in Figure 37. The attribute list screen 140 allows the user to create and edit attributes that will be associated with an asset. As shown in Figure 37, the attribute list screen 140 includes information about associated attributes, such as names and attribute types. The attribute list screen 140 also provides a hypertext of details of the attributes 142, and of adding attributes 144, and deleting attributes 146. When selecting the details hypertext of the attributes 142, the data format 23 is changed to display a screen of details of the attributes 148 as shown in FIGURE 38.

The attributes details screen 148 contains information about the details of the attributes such as: name of the attribute, type of the attribute and value of the attribute. The details screen of the attribute also includes a hypertext edit attributes 150, and add properties to attributes 152 and delete properties to attributes 154. When selecting the hypertext edit attributes 150, the data frame 23 is changed to a screen of editing attributes 156 , as shown in FIGURE 39. The screen of editing attributes 156 shows information about the attribute such as: name of the attribute, type of attribute, sequence of the attribute within the listed attributes that can be edited. This is achieved by an area of attribute names 158, a list of attributes 160 and a hypertext of saving changes 162. To change the name of the attribute and / or the sequence of the attribute, to the area name of attribute 158 and / or list of attributes. sequence of attribute 160 must be modified and the hypertext save selected changes 162.

Returning to FIGURE 38, by selecting the hypertext add properties 152, the data frame 23 is changed to display the add properties screen 164, as shown in FIGURE 40. The add properties screen 164 provides an area of property value 166 , as shown in FIGURE 40. The add property screen 164 provides an area of property value 166 and a hypertext of sending 168. When writing an additional value in the property value area 166 that will be associated with the selected attribute and when selecting the hypertext to send 168, the written value will be saved as property of the attribute.

Returning to FIGURE 38, upon selecting the hypertext delete property 154, the data frame 23 is changed to display the delete property 170 screen, as shown in FIGURE 41. The delete property 170 screen provides a property list 172 associated with the attribute in particular. Each property within property list 172 has a property hypertext 174. Each property hypertext 174 is represented by the name of the property. When selecting the hypertext of a property 174, the selected property is separated from the attribute.

With respect to FIGURE 37, when selecting the hypertext add attribute 144, the data frame 23 is changed to display a screen of adding attribute 176 as shown in FIGURE 42. The add attribute screen 176 provides an attribute search format 178, a search hypertext 180, a hypertext to cancel 182, and a hypertext of new attribute 184. When writing the name of an attribute that is already associated with another asset, but is not currently associated with any current asset in the form of attribute search 178 and select search hypertext 180, the add attribute 176 screen is changed to include the searched attribute in a table 181, if it exists in the system as shown in FIGURE 43. When establishing a sample sequence 186 of the searched attribute and selecting the hypertext of the searched attribute 188 in Figure 43, the searched attribute will be associated with the particular asset. Upon selecting the hypertext to cancel 182 of FIGURES 42 or 43, the data frame 23 is changed to display the attribute list screen 140 of FIGURE 37.

Alternatively, by selecting the hypertext of a new attribute 184 in FIGURES 42 or 43, the data frame 23 is changed to display a new attribute screen 190 as shown in FIGURE 44. The new attribute screen 190 contains a attribute name area 192, a list of attribute types 194, and a hypertext to add new attribute 196. When typing the name of a new attribute in the name area of attribute 192, select a new attribute type from the list of new attributes 194, and selecting the hypertext of adding new attribute 196, the new written attribute appears on the screen adding attribute 176 of Figure 43 instead of the searched attribute where it can be associated with the asset described above. Some types of possible attributes are: value, list and collection. All attributes associated with a particular asset are shown in the asset details screen for the particular asset.

With respect to FIGURE 37, when selecting the hypertext delete attribute 146, the data frame 23 is changed to display the delete attribute screen 198 as shown in FIGURE 45. The delete attribute screen 198 provides a list of attributes 200 that displays information about the attributes associated with the particular asset, such as : the name of the attribute and the type of attribute. Each attribute is associated with a hypertext to delete attribute 202 that is represented by the name of the attribute. When selecting the hypertext attribute 202, the name of the selected attribute is separated from the particular asset.

With respect to FIGURE 35, by selecting the hypertext contacts of the asset 134, the data frame 23 is changed to display a contact list screen of the asset 204 as shown in FIGURE 46. The active contact list screen 204 provides information regarding the administrator in charge of a particular asset, such as contact type and contact name. The contact list of the asset 204 provides a hypertext of editing contacts 206 and a hypertext of details of the contact 208. By selecting the details hypertext of the contact 208, the data frame 23 is changed to display the details screen of the contacts. When selecting the hypertext edit contacts 206, the data frame 23 is changed to display a screen for editing administrator contacts. It is envisaged that from the administrator's contacts edit screen it is possible to associate more than one contact with a particular asset, new contacts can be entered into the system, current contacts can be edited and existing contacts not associated with the present asset can be associated in a similar way to that previously explained in the case of attributes.

With respect to FIGURE 35, when selecting the file hypertext of an asset 135, the data frame 23 is changed to display a window with the list of sub-assets as shown in FIGURE 12.

In one example, the control frame 22 may include an add mark screen that appears and operates in a manner similar to the edit mark screen 109 of FIGURE 36.

As indicated above, at the bottom of the data hierarchy are the files - objects that represent specific digital assets, such as images, logos or other documents. The shopping cart provides the user with a method to gather all these files in one area.

When a user finds a file that he wants, the user can put it in the shopping cart and then move to other locations, accumulating additional files. For example, adding a file to the shopping cart does not move the file from its location to the system's data hierarchy. Instead, simply place a reference to the file in the shopping cart.

In an example there are two types of shopping carts: the primary car and the designated cars. Each user has a single primary shopping cart, but can create any number of designated shopping carts. Preferably, files can be added to the primary shopping cart only. The designated shopping carts are filled with the contents of the primary shopping cart or some other designated cart.

In one example, a user can put their company logos on a shopping cart and colorings for packaging the product on the other. First, a user creates two designated shopping carts: "Logos" and "Colorants." Then he accumulates the files with logos in the primary shopping cart, loads the contents of the primary car in the "Logos" car and then empties the primary car. Subsequently, the user accumulates the coloring files for the packages in the empty primary car, then loads the new content in the "Colorants" car. In one example, a user can even create another shopping cart called "Logos and Colorants," and then load the contents of both carts designated on that cart.

What the user finally does with the files accumulated in the shopping cart may depend on the installation options during the installation of the system and may vary from portal to portal. For example, the installation of the system may allow the user to download the files or transfer them to another computer.

By exemplifying the operation of the shopping cart in the preferred example, the illustrative database of the system - the database "Junk Food" is unified again.

Although the database of a user will contain different information, these examples illustrate the possibilities of the shopping carts.

The files stored in the system data hierarchy can be added to the user's primary shopping cart. Once in the primary car, they can be transferred to a designated shopping cart. To add files to the primary shopping cart, it is preferable that the user first locate the desired files by browsing, browsing or searching.

As mentioned previously, the File List page of FIGURE 12 can be opened using the "View" button 65 or the search tool. The File List page contains files that the user can add to the primary shopping cart. The first column 66 in the data table 44 is entitled "Carriage". The column "Car" 66 contains icons 68 that show the files that are in the shopping cart and icons 70 that allow the user to move a file inside or outside the shopping cart. The icon 68 on the left side of the column, the State cone, indicates whether or not a file is in the primary shopping cart (the file is in the primary shopping cart, the file is not in the primary shopping cart ). The icon 70 on the right side of the column, the Action icon, identifies the action that will occur if the radio button 71 that precedes the icon is selected (move the file inside the primary shopping cart; move the file outside the primary shopping cart). purchases).

For example, the pinata.eps and redpeps.eps files can be selected to be included in the primary shopping cart by selecting the radio buttons 71 that precede their Action 70 cones resulting in the data table 44 shown in the FIGURE 47. If a user selects the Action cone of a file and then decides otherwise, then the radio button 69 that precedes the Status 68 icon is selected to restore the original status of the file in the shopping cart. Additionally, if the Reset button is selected (FIGURE 12) in the Control frame, all files are restored to their original state.

Preferably, selecting the radio button 71 that precedes the Action Cone 70 does not immediately move a file inside or outside the shopping cart. Instead, the user must select the Save button (FIGURE 12) in the Control 22 frame for the action to take place.

As a result, the user can select the Action and State icons and the radio buttons again and again without making visible changes to the shopping cart.

Returning to FIGURE 48, opening the primary shopping cart shows the files that are currently in the car and allow the user to operate the contents of the car. The "Contents of the Primary Cart" page illustrated in FIGURE 48 is opened by selecting the Purchase Cart button 97 (FIGURE 12) in the Control frame. For each object in the car, a graphic representation, the name of the files and shopping cart cones are shown. The graphic representation provides a graphic preview of the contents of the files. The file name connection is shown below the graphic representation. Opening this connection opens the File Details page that allows the user to browse detailed information about the file.

Under the links with the names of the files are the icons of shopping carts. To remove an object from the shopping cart, the user selects the radio button that precedes his or her Action. To return an object to the shopping cart, the user selects the radio button that precedes the State cone. Preferably, selecting the Action icon does not immediately remove an object from the shopping cart. Instead, the user is required to select the Save button in the Control frame for the action to take place.

At the bottom of the page is the outgoing files per row that can be used to change e! number of files that are displayed in each row of the page. For example, in FIGURE 48, selecting "2" from the projection would show two files per row instead of four.

When the Contents page of the Primary Cart is displayed, the following buttons can be added to the Control frame, if appropriate for the contents of the cart (for example, if the cart contains no objects, the Empty button is not shown): 1) the "Cars" button when selected shows a page that lists the shopping carts that the user can use, including both the user's primary car and the designated carts and the user can see the contents of the cars listed by selecting the name of the cart. car; 2) by selecting the "Load" button the user can load the contents of any shopping cart in the displayed car and preferably, load adds the files in the selected car origin to the displayed car; 3) by selecting the "Replace" button, the user can replace the content of the shopping cart shown with the content of another car and unlike the load operation, replace removes the contents of the displayed car before adding new files; 4) by selecting the "Delete" button, all files in the displayed car are deleted; 5) the "Remove All" button select the Remove All icon in the displayed cart (including those not shown on the page) and mark them to be deleted, but preferably, these files are not deleted from the cart until the Save button is selected; 6) the "Restart" button returns the shopping cart to the state it was in when the user first opened the page; and 8) the "Save" button permanently saves all changes made to the contents of the shopping cart.

Preferably, when the Contents of the Designated Cart page is displayed, the following buttons are added if convenient: 1) "Delete" that when selected eliminates the designated carts with a dialog box to confirm before the cart is deleted; and 2) the "Edit" button that allows the user to change the name of the shopping cart to a unique name that is not assigned to another shopping cart.

As mentioned previously, designated shopping carts are used to accumulate a group of files and organize them under a descriptive title. The current invention enables the user to create and save multiple designated shopping carts. The designated shopping carts that the user creates belong exclusively to the user in such a way that no other user can see them or have access to their content. Additionally, the names of the designated carts of a user remain even if the user leaves the system and until the user expressly removes them.

In one example, a user can create a designated shopping cart to include the necessary files to design the Super Maiz Mexicano product. Returning to FIGURE 12, the usu: go: o first select the "Shopping Cart" button 97 and the contents of the primary shopping cart is shown, for example FIGURE 48. In the frame of counter '22, the user selects the "Cars" button and a list containing the name of all the shopping carts of the user is shown as in FIGURE 49. The user then selects the "Add Cart" button in the Control 22 frame to specify a name for the user. new shopping cart. As a result, the Add Car sample in FIGURE 50 is presented so that the user can specify a name for the new car, such as "MexMaiz Redesign". Afterwards, the user selects the "Add Car" button and the page with the Car List is displayed again, but now e! new car as shown in FIGURE 51.

Once e! user has created a designated shopping cart, the user can add files. Preferably, however, the user can not add files directly to the designated car. The user first places the files in the primary car and then loads the contents of the primary car into the designated car. If desired, a user can empty the primary car before accumulating the files to ensure that only the desired files will be added.

Below is an illustrative example with respect to loading files of a primary shopping cart in the "Redesign of MexMaíz" cart to exemplify the present invention. First, the user selects the Shopping Cart button 97 in the Control 22 frame as is shown in FIGURE 48, and the contents of the primary shopping cart are shown. The user can then verify that only the files that he wants to load in the cart "Redesign of MexMaíz" are in the primary shopping cart. If the primary car contains files that should not be uploaded, the user selects the radio button that precedes the Delete Action icon and then selects the "Save" button in the Control 22 frame to remove them from the car.

Subsequently, the user selects the button "Cars in the Control 22 frame where the page of FIGURE 51 and a list of the shopping carts of the user is shown." In FIGURE 51, the shopping cart "Rediseño MexMaíz" has no As a result, the user opens the shopping cart "Rediseño MexMaíz" to add files.

The user then selects the "Redesign MexMaiz" connection to display the "Redesign MexMaiz" page as shown in FIGURE 52 with a message that indicates that the "Rediseño MexMaíz" shopping cart is empty. The user then selects the "Load" button of the control frame 22 and the page of FIGURE 53 that allows the user to select the shopping cart containing the files that will be loaded in the shopping cart "Redesign MexMaiz" is displayed.

The user then selects the "Primary Carriage" connection, which causes the primary car files to be loaded into the "Redesign MexMaiz" shopping cart and the content of the "Redesign MexMaiz" cart is shown as shown in FIGURE 54. preference the files remain in the primary shopping cart even if they have been loaded in another shopping cart. Although the above illustration transfers files from the primary car to the "Redesign MexMaíz" car, the present invention includes transferring files from any shopping cart to any other car.

As indicated previously, each user of the system has a primary shopping cart and can create additional carts designed to better organize the files he or she wishes to accumulate. Files displayed on a File List page can only be added to the primary shopping cart. To place files within a designated shopping cart, it is desired that the user add them to the primary shopping cart and then use the Load or Replace function to move them to a designated car.

Additionally, as indicated above, when a Shopping Cart page is displayed, buttons are added to the control frame 22 providing access to the operations that the user can perform in a shopping cart. The portal of a particular system can have operations for the personalized shopping cart - for example, operations that allow the user to transfer files from the shopping cart to another computer.

The files stored inside a user's designated shopping cart can be subject to operations such as changing the file size, file format, or even more advanced functions based on whether the file is a typeface, image or other design element . Additionally, the files stored in a user's designated shopping cart can be channeled through a local or wide-ranging network in order to send files to another user or to another database.

As mentioned above, the present invention provides project management functions that allow the user to establish projects, manage work groups related to particular projects, and assign tasks or events that must be completed within a period of time to complete the project. draft. A project is a specific campaign or promotion for a particular brand. A job is a print sample for a promotion.

With respect to FIGURE 6, by selecting the hypertext "Projects" 300 in the control frame 22, the data frame 23 is changed to display a project list screen 302 as shown in FIGURE 55. The screen list of 302 projects shown in FIGURE 55 shows information on projects for the manufacturer "Food Scrap, Inc." as shown in the route finder 20. The project list screen 302 also provides a hypertext of project details 304 and a hypertext list of jobs 306. Additionally, control frame 22 includes a hypertext add project 308. When selecting the hypertext add project 308, data frame 23 is changed to show the add project 310 screen as indicated in FIGURE 56. The add project screen 310 includes areas 312 to enter project data such as: project number, project name , date, start date, delivery date, actual termination date and notes; change state list 314; and a hypertext to save changes 316. When entering the project information in the 312 formats, select the project status from the 314 status list and select the hypertext save changes 315 new projects are created.

With respect to FIGURE 55, when selecting the hypertext details of the project 304, the data frame 16 is changed to display the project details screen 318 as shown in Figure 57. The project details screen 318 includes the same information as the 302 project list screen on the particular project. The control frame 22 of the project details screen 318 Includes a hypertext of sub-projects 320, a hypertext of works 322, a hypertext of events 324, a hypertext of contacts 326 and a security hypertext 328. When selecting the hypertext subprojects 320, the data frame 23 is changed to show a new project details screen 318 for any sub-project. By selecting the hypertext events 324, the data frame 23 changes to display the event list screen 336 associated with the project, as shown in FIGURE 58. The event list screen 336 is explained in more detail below.

Returning to FIGURE 57, when selecting the edit hypertext 326, the data frame 23 is changed to show the edit project screen 334 as shown in FIGURE 59. Within the edit project 334 screen, all the information about the project can be displayed. be edited and saved as previously explained in accordance with other types of data. By selecting the contact hypertext 328, the data frame 23 changes to display the contact list screen 284, as shown in FIGURE 60. By selecting the security hypertext 330, the data frame 23 is changed to display a screen of security as will be explained below with respect to the administrative function.

Returning to FIGURE 55, when selecting the hypertext works 308, the data frame 23 is changed to show the list window of sub-assets containing jobs as shown in FIGURE 11.

With respect to FIGURE 11, by selecting the sub-active hypertext 64 indicating events, the data frame 23 is changed to display an event list window 336 as shown in FIGURE 58. The event list window 336 contains information regarding the events agreed for a job 5 such as: name of the event, contacts of the event, date of delivery of the event, deadline of the event, and status of the event. The event list window 336 also provides a hypertext event name 338 and a hypertext contacts event 340, and a hypertext add event 342. A! select the hypertext name of the event 338, the data frame 23 is changed to show ! 0 the event details screen 344 as shown in FIGURE 61. The event details screen 344 provides a hypertext edit 346 in the control frame 22, a hypertext contacts 348 and a hypertext e-mail 350.

In a representation, administrative functions are provided.

Returning to FIGURE 62, in order to provide security to the system and prevent unauthorized access, a login screen 400 having an entry name area 402, secret key area 404 and a connect hypertext 406 is provided. To connect, a user must enter a valid connection name in the format of connect 402 and write his secret key in the format 20 of secret key 404, and then select connect 406. If the name or secret key is invalid, the list of sub-assets 40 screen of FIGURE 6 appears for the company with which the user is associated. When selecting the hypertext, exit 408 of the control frame 22 of FIGURE 6, the user automatically disconnects and returns to the connect 400 screen. In a representation, the screen 40 of FIGURE 6 may include a hypertext "Admon." (such as the reference number 407 in FIGURE, 57) and upon selecting said connection, the data frame 23 is changed to display the screen with a management title 410, as indicated in FIGURE 53. In the: frame of control 22 there are circe hioertsxtos administrative: hypertext companies 412, hypertext groups 414, hypertext code table 416, hypertext connect 418, and a safe hypertext 420. When selecting the hypertext companies 412, a screen with the list of companies 422 is shown in the data frame 23, as indicated in FIGURE 64. Additionally, a hypertext add company 424 is displayed in control frame 22. The company list screen 422 provides information about any company associated with the present system. The company list screen 422 also provides a hypertext company name 426 and a hypertext email 428, and a hypertext contacts 429.

By selecting the hypertext add companies 424, data frame 23 is changed to show a screen add 430 companies as indicated in FIGURE 65. The add 430 companies screen contains 432 formats for company name, address, city, state, code postal, telephone, fax, e-mail and list to choose cities 434, a list to choose state 436 and a hypertext to save changes 438. After writing the relevant information within the areas 432, select the correct country and the state of the lists 434, 436, and select the hypertext save changes 438, the information of the new company is added to the system.

By selecting the hypertext name of the company 426 of FIGURE 64, the data frame 23 is changed to include a detail screen of the company 440 which contains relevant information about the company's customers, company name, address, telephone, fax, company status as in FIGURE 66. The details screen of the company 440 also includes a hypertext edit company '442 and a hypertext contacts company 444. When selecting the hypertext edit company 442, the data frame 23 is changed to display a 446 company edit screen as indicated in FIGURE 67. By changing the information in the areas of the edit company 446 screen and selecting the save hypertext 448, the company's information is updated.

With respect to FIGURE 66, by selecting the company's hypertext contacts 444, the data frame 23 is changed to display the contact list screen of company 450 as indicated in FIGURE 68. The contact list screen 450 provides Information about each contact associated with the company. The contact list screen 450 contains a hypertext contact name 452, a contact email hypertext 454, and a contact add hypertext 456. By selecting the hypertext name of the contact 452, the data frame 23 changes to display a screen details of contacts 458 as indicated in FIGURE 69. The contact details screen 458 contains relevant information about the particular contact such as contact name, contact company, contact address, contact email and contact status. The contact details screen 458 includes a hypertext company 460, a hypertext email 462 and a hypertext edit contact details.

When selecting the hypertext to edit contact details, the data frame 23 is changed to display the edit contact details screen 466 as indicated in FIGURES 70a and 70b. The edit contact details screen 466 allows the details of the contacts to be edited and then saved by selecting the hypertext to save contact details 468.

With respect to FIGURE 69. when selecting the hypertext company 460, the data frame is changed to display the details screen of the company 440 of FIGURE 66. By selecting the hypertext e-mail 462 of FIGURE 69 an e-mail message It can be sent to the contact.

With respect to FIGURE 68, when selecting the hypertext add contacts 456, the data frame 23 is changed to display the add contacts screen 470 as shown in FIGURES 71a and 71b. When changing the areas of the screen add contact 464 and select the hypertext to save changes 472.

With respect to FIGURE 64, by selecting the hypertext email 428 an email message can be sent to the company. By selecting the hypertext contacts 429, the data frame 23 is changed to display a list of contacts 450 of FIGURE 68.

With respect to FIGURE 66, when selecting the user hypertext 474, the data frame 23 is changed to display the user screen 476 as indicated in FIGURE 72, which shows the current users of the company. The display users screen also provides a hypertext add user 478. When selecting the add hypertext user 478, the data frame 23 is changed to display the add contacts screen 470 of FIGURES 71a and 71b.

With respect to FIGURE 63, when selecting the hypertext groups 414, the data frame 23 is changed to display the group list screen 480 as shown in FIGURE 73. The group list screen 480 shows the current user groups , status of user groups, and number of users in the group. The group list screen 480 also contains a hypertext group details 482, hypertext group number 484, and add group 486. When selecting the hypertext group details, the data frame 23 is changed to display the group details screen 488, as shown in FIGURE 74. The details screen of group 488 also includes a hypertext edit group 490. When selecting the hypertext edit group 490, the data frame 23 is changed to display the edit group 492 screen as indicated in the FIGURE 75. When editing the areas on the screen edit groups 492 and select the hypertext to save changes 494, the group information of changed. When associating users with groups, the rights for a particular user to perform certain functions with brand management, project management and file sharing can be edited. The rights of certain users to view and not be able to edit or add data may be restricted.

With respect to FIGURE 63 when selecting the hypertext code tables 498, the data frame 23 is changed to display a code table screen 500 as shown in FIGURE 76. The code table screen 500 is displayed to allow the Personalization of this presentation for each user of the system.

With respect to FIGURE 63, when selecting the connect hypertext 502, the data frame 23 is changed to show the connect screen 506, as indicated in FIGURE 77. The connect screen 506 shows the list of users currently connected to the system.

With respect to FIGURE 63, when selecting the secure hypertext 504, the data frame 23 is changed to display the secure screen 508 as indicated in FIGURE 78. The secure screen 508 shows the list of records currently in the system.

Although this specific representation has illustrated and described numerous modifications that come to mind without significantly separating us from the spirit of the invention and the scope of its protection, they are limited only by the scope of the appended Claims.

Claims (97)

1. REYVINDICATIONS 1. A system "for managing the development of a package of graphic samples that includes: a portion of the brand to accept and maintain an identification of one or more brands, the brand portion is at a first level of relationship, a portion of the product to accept and maintain an identification of one or more products, the product portion is at a second level of relationship that is directly related to the first level of relationship, and a portion of work to accept and maintain identification of one or more jobs , the work portion is at a third level of relationship that is directly related to the second level of relationship 2. The system of claim 1 in which the first level of relationship is in one to several relationship with respect to the second relationship level 3. The system of claims 1 or 2 wherein the second level of relationship is in one to several relationship with respect to the third relationship level. 4. The claim 1 system includes a brand publisher, brand finder, company identification portion, company publisher, brand contact identification portion, brand market portion, brand file portion, ownership portion of brand and portion of brand attributes. 5. The system of claim 1 further contains a product editor, product searcher, product contact identification portion, content product portion, product file portion, product ownership portion, and product attribute portion. 6. The system of claim 1 further contains a work editor, a job seeker, a contact identification portion of the job, property portion of! work, portion of the labor market, portion of 7. The system of claim 1 wherein the brand portion also includes a sub-brand portion and has a sub-brand publisher, sub-brand finder, sub-brand contact identification portion, market portion. sub-brand, portion of sub-brand files, sub-brand property portion, sub-brand attribute portion, the brand portion stores at least one brand and the sub-brand portion has at least a portion of sub-brand in which at least one brand has at least one related sub-brand. The system of claim 1 wherein the product portion further includes a sub-product portion and has a sub-product editor, a sub-product searcher, a by-product contact identification portion, a portion of sub-product content, a sub-product file portion, a subproduct property portion, a subproduct attribute portion, the product portion contains at least one product, and the subproduct portion it contains at least a portion of its product and a product has at least one related by-product. The system of claim 1 wherein the first relationship level is directly related to the second relationship level directly connects the brand portion with the product portion, respectively, and at least one product is related to at least one brand being the product related to the brand and is accessible from the brand portion. The system of claim 1 wherein the second level of relationship is directly related to the third level of relationship directly connects the product portion with the working portion, respectively and at least one job is related to at least a product in such a way that being related the work with the product is accessible from the portion of the product. 11. The system of claim 1 wherein e! Brand finder can search for a brand at least for a property value of the property portion of the brand. 12. He The system of claim 1 wherein the product searcher can search for a product at least for a property value of the product's property portion. The system of claim 1 wherein the job seeker can search for a job at least for a property value of the work property portion. The system of claim 1 wherein the value of a property of the property portion of the mark can be used to search for a file within the mark file portion. The system of claim 1 wherein the property value of the product's property portion can be used to search for a file within the file portion of the product. The system of claim 1 wherein the value of the property of the job's property portion can be used to search for a file within the job's file portion. 17. The system of claim 1 further includes: a project portion that has a project search engine, a project editor, a portion of project contact identification, a portion of project properties, a portion of project events, a portion of project work, and the portion of the project is directly related to the portion of the work; and, a portion of events that has an event finder, an event editor, a portion of event properties; the portion of the event is directly related to the portion of the work. 18. The system of claim 17 wherein at least one job is related to at least one project and in which the work thus related to the project is accessible from the project portion. 19. The system of claim 17 wherein e! work is related to at least one event and e! Work like this is accessible from the portion of! event. 20. The system of claim 17 in which the project seeker can search a project at least for. a property value of the project properties portion. 21. The system of claim 17 wherein the event searcher can search for an event at least by a value of the properties of the event properties portion. 22. The system of claim 1 further includes: a collector for collecting one or more files selected from one or more of the portions of the mark file, the file portion of the product, and the file portion of the work within a portion of files collected. 23. The system of claim 22 wherein the collector can delete one or more of the files from the portion of collected files. 24. The system of claim 1 further includes: a trademark partner to associate at least one file with the trademark introduced to the trademark portion. 25. The system of claim 1 further includes: a product partner to associate at least one file with the product entered in the product portion. 26. The system of claim 1 further includes: a work associator to associate at least one file with the work entered in the work portion. 27. A system for managing the development of graphic packaging representations that includes: a brand portion that has a brand editor, a brand finder, a company identification portion, a company publisher, a contact identification portion brand, a portion of brand file, the brand portion is in a first level of relationship; a product portion that has a product editor, a product search engine, a product file portion, a product portion that is in a second relationship level that is directly related to the first relationship level; and a portion of work that has a job editor, a job seeker, a work file portion, the work portion is at a third level of relationship that is directly related to the second level of relationship. The system of claim 27 wherein the brand portion further includes a brand market portion to accept and maintain identification of one or more markets for one or more brands. 29. The system of claim 27 wherein the brand portion further includes a portion of the brand's properties to accept and maintain identification of one or more properties for one or more brands. 30. The system of claim 27 wherein the brand portion further includes a portion of brand attributes to accept and maintain identification of one or more attributes for one or more brands. The system of claim 27 wherein the portion of the product further includes a contact identification portion of the product for accepting and maintaining the identification of one or more contacts for one or more products. 32. The system of claim 27 wherein the portion of the product further includes a portion of product content to accept and maintain the identification of one or more contents of the products for one or more products. 33. The system of claim 27 wherein the product portion further includes a portion of product properties to accept and maintain the identification of one or more properties for one or more products. 34. The system of claim 27 wherein the portion of the product further includes the attributes portion of the product to accept and maintain identification of one or more attributes for one or more products. 35. The system of claim 27 wherein the portion of the work further includes a contact identification portion of the work to accept and maintain one or more contacts for one or more jobs. 36. The system of claim 27 wherein the portion of the work further includes a portion of work properties to accept and maintain the identification of one or more properties for one or more jobs. 37. The system of claim 27 wherein the portion of the work also includes a portion of the labor market to accept and maintain the identification of one or more markets for one or more jobs. 38. The system of claim 27 wherein the work portion further includes a portion of work events to accept and maintain the identification of one or more events for one or more jobs. 39. A system for resource and project management that includes: at least one program stored on a removable compact media that is readable by the system, the program has: code to create a hierarchy of multiple asset levels with a plurality of objects that includes jobs and files; code to create a hierarchy of multiple levels of projects with a plurality of objects that include jobs in the hierarchy of assets and events; code to create a visual sample of the objects within the asset hierarchy and the project hierarchy; code to allow the editing of objects within the asset hierarchy and the project hierarchy; and code for the creation of a visual sample of the objects within the asset hierarchy and the project hierarchy. 40. The system of claim 39 further includes a code to enable the user to view the asset hierarchy by visually observing the objects at the same level per level. 41. The system of claim 39 further includes a code to allow the user to see the hierarchy of projects by visually observing the objects therein, level by level. 42. The system of claim 39 includes a code to allow the user to navigate the asset hierarchy by visually observing an overview of the asset hierarchy. 43. The system of claim 41 further includes a code to allow the user to focus on a particular level of the objects. 44. The system of claim 39 further includes a code to allow the user to navigate the project hierarchy to visually observe an overview of the project hierarchy. 45. The system of claim 44 further includes a code to allow the user to focus on a particular level of the objects. 46. The system of claim 39 further includes a code to enable the user to search the asset hierarchy to locate an object that satisfies a user-defined criteria. 47. The system of claim 39 further includes a code to enable the user to search the project hierarchy to locate an object that satisfies a particular criterion defined by the user. 48. The system of claim 39 further includes a code for providing a shopping cart to the user that allows him to collect at least one of the files. 49. The system of claim 48 further includes a code that allows the user to perform operations on the files included in the shopping cart. 50. The system of claim 49 further includes a code that allows the user to channel the files contained in the shopping cart to another database. 51. The system of claim 39 further includes a code to allow the user to edit cbietcs within the asset hierarchy. 55 52. The system of claim 7 further includes a code to allow the user to edit objects within the project hierarchy. 53. A method for managing resources and projects that includes the following steps: create a multi-level asset hierarchy with a plurality of objects including jobs and files; store said hierarchy of assets in the system memory; create a hierarchy of multi-level projects with a plurality of objects including jobs in the asset and event hierarchy; store said project hierarchy in the system memory; create and provide a visual frugar of the objects within the hierarchy of assets and projects; edit the objects within r < hierarchy of assets and the hierarchy of projects; and create and provide a visual display of the jobs within both the asset hierarchy and the project hierarchy. 54. The claim method further includes the step of allowing the user to visually observe the objections within the asset hierarchy level by level. 55. The method of claim 53 further includes the step of allowing the user to visually observe the objects within the project hierarchy, level by level. 56. The method of claim 53 further includes the step of allowing the user to visually observe an overview of the asset hierarchy. 57. The method of claim 56 further includes the step of allowing the user to focus on a particular level of the objects. 58. The method of claim 53 further includes the step of allowing the user to view an overview of the project hierarchy. 59. The method of claim 58 further includes the step of allowing the user to focus on a particular level of the objects. 60. The method of claim 53 further includes the step of allowing the user to search the asset hierarchy to locate an object that satisfies a series of user-defined criteria. 61. The method of claim 53 also includes the step of allowing the user to search the project hierarchy to locate an object that satisfies the criteria established by the user. 62. The method of claim 53 further includes e! case to provide a shopping cart that allows the user to obtain at least one of the files. 63. The method of claim 62 further includes the step of allowing the user to perform operations with at least one of the files contained in the shopping cart. 64. The method of claim 62 further includes the step of allowing the user to channel at least one of the files contained in the shopping cart to another database. 65. The method of claim 53 further includes the step of allowing the user to edit objects within the asset hierarchy. 66. The method of claim 53 further includes the step of allowing the user to edit objects within the project hierarchy. 67. A system for managing resources and projects that includes: a multi-level asset hierarchy stored in the system's memory with a plurality of objects including files and jobs; a multi-level project hierarchy stored in the system memory with a plurality of objects including jobs in the asset and event hierarchy; a program code to create a visual sample of the objects within the asset and project hierarchy; Y 68. The system of claim 67 further includes a code to allow the editing of objects within the asset and project hierarchy. 69. The system of claim 67 further includes a code to enable the user to visualize the objects within the asset hierarchy, level by level. 70. The system of claim 67 further includes a code to allow the user to visualize the objects within the hierarchy of projects level by level. 71. The system of claim 67 further includes a code to allow the user to have an overview of the asset hierarchy. 72. The system of claim 72 further includes a code to allow the user to focus on a particular level of the objects. 73. The system of claim 67 further includes a code to allow the user to view an overview of the project hierarchy. 74. The system of claim 73 further includes a code to allow the user to focus on a particular level of objects. 75. The system of claim 67 further includes a code to enable the user to locate an object in the asset hierarchy that satisfies the criteria established by the user. 76. The system of claim 67 further includes a code to enable the user to locate an object in the project hierarchy that satisfies the criteria established by the user. 77. The system of claim 67 further includes a shopping cart that allows the user to obtain at least one of the files. 78. The system of claim 77 further includes a code that allows the user to perform operations on the files contained in the shopping cart. 79. The system of claim 77 further includes a code to allow the user to channel the files contained in the shopping cart to another database. 80. The system of claim 67 also includes a code to allow the user to edit objects within the asset hierarchy. 81. The system of claim 67 further includes a code that allows the user to edit objects within the project hierarchy. 82. A method for managing resources and projects that includes the following steps: store a multi-level asset hierarchy in the system's memory, the asset hierarchy has a plurality of objects including jobs and files; store a hierarchy of multi-level projects in the system memory, the project hierarchy has a plurality of objects including jobs in the asset and event hierarchy; create and display a graphic representation of the objects within the asset hierarchy and the project hierarchy; and create and display a graphic representation of the works in both the asset hierarchy and the project hierarchy. 83. The method of claim 82 further includes a step to edit the objects within the asset hierarchy. 84. The method of claim 82 further includes the step of editing the objects within the project hierarchy. 85. The method of claim 82 further includes the step of allowing the user to visualize a graphic representation of the objects within the asset hierarchy level by level. 86. The method of claim 82 further includes the step of allowing the user to observe a graphic representation of the objects within the project hierarchy, level by level. 87. The method of claim 82 further includes the step of allowing the user to observe a graphical representation of an overview of the asset hierarchy. 88. The method of claim 87 further includes the step of allowing the user to focus on a particular level of the objects. 89. The method of claim 87 further includes the step of allowing the user to observe a graphic representation of an overview of the project hierarchy. 90 The method of claim 89 further includes the step of allowing the user to focus on a particular level of objects. 91. The method of claim 82 further includes the step to allow the user to locate an object in the asset hierarchy that satisfies the criteria set by the user. 92. The method of claim 82 further includes the step of allowing the user to locate an object in the project hierarchy that satisfies the criteria set by the user. 93. The method of claim 82 further includes the step of providing a shopping cart that allows the user to obtain at least one of the files. 94. The method of claim 93 further includes the step of allowing the user to perform operations on the files contained in the shopping cart. 95. The method of claim 94 includes the step of allowing the user to channel the files contained in the shopping cart to another database. 96. The method of claim 82 includes the step of allowing the user to edit objects within the asset hierarchy. 97. The method of claim 82 includes the step of allowing the user to edit objects within the project hierarchy.