JP2002521768A - Resource and project management system - Google Patents

Abstract

(57) Summary One system for maintaining, accessing, and storing digital assets in a repository is disclosed. This system integrates the functions of file and video management with the storage of information about files and videos. In addition to providing access to the image asset itself, the system also works with the asset in coordination with other information, allowing the user (16) to track completed work and define new plans. . In addition, system information is stored in a data hierarchy that is complementary to the natural task.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001] RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 60 / 094,912 which is incorporated herein by reference, filed on July 31, 1998.

[0002] The present invention relates to management of the project (project) in the development of the graphic images, and more specifically, prepress industry (pre-press industry) products of packaging in the (product packaging) for Projects and brand identity in the development of graphic images
Tracking and managing.

[0003] There are a variety of software products that are designed to manage the background, especially a variety of file format of the invention. Aldus Fetch seems to be the first product of this type, and Apple MACINTOSH
Used in computers. It was designed to catalog various image and application file formats, such as EPS, TIFF, Adobe ILLUSTRATOR files and other proprietary and non-proprietary file formats. Other prior art products include Kudos Image Browser
It is. This product was easy to use, but not as rich in features as Aldus Fetch. Both of these products managed files for individual users or small groups of users, but did not spread much to workgroups or companies, as well as companies.

[0004] CUMULUS, a product designed to address the shortcomings of Aldus Fetch and Kudos Image Browser, marks the beginning of the next generation of image management products. Cumulus,
Image management was extended to workgroups and companies using a client / server architecture. Instead of opening a file on the local hard drive that stores all image management information, the Cumulus client software uses C
Connected to a database managed by umulus server software. Cumulu
s also facilitates the organization and management of each keyword used to describe each image by providing a hierarchical keyword structure. Cumulus made it easy to share this image information throughout the company, but its performance degraded as the number of images in the database increased.

[0005] All of the products described above use proprietary database usage. This makes it difficult to integrate these products with other products, since the user cannot directly obtain the stored information. These products are also very file centric. In other words, these products can only list each file, generate a preview, and extract file-specific data such as creation date, file format, file size, and the like. These products have no means of storing the production information associated with each file, such production information being:
Which jobs were used for the file and / or which fonts / glyphs and images were used in creating the application file;
Information about. In practice, this information or metadata is of paramount importance.

[0006] The next generation of image management products is the management of prepress workflows.
rkflow management) tools. Products in this category include Archtype
Media Bank and Media Assets. These products still used proprietary database technology, but improved workflows helped to accelerate prepress production, especially in the catalog arena. However, these products were extremely expensive. Moreover, although these products are adapted to the field of catalog production, they do not use basically the same software tools as the packaging field.

[0007] Another downside of these products is the prepress work flow.
It is necessary to follow the approach of these products to manage flow). this is,
There is little flexibility in areas that are significantly affected by rapid technology changes.

Finally, the latest category of image management products is based on open reference-based technology. North Plaines Systems Telescope and Imation Media Man
ager is two products that fall into this category. The key feature that distinguishes these products is that in addition to storing file information such as file name, file size, file format, creation date, etc., they also have 14 customizable information fields. Both of these products are SQs such as Microsoft SQL Server or Oracle.
Store file information and custom fields in the L conformance database. This allows custom applications such as Crystal Report and Microsoft Query or database reporting tools to have direct access to the database. It also allows the supply of file information from within a web browser.

[0009] However, despite the open reference characteristics of Media Manager and Telescope, these products are still inadequate in one area. They are all file-oriented products. In other words, to enter any data in the database, the files must first be listed. Unfortunately, there is a significant amount of metadata prior to file creation and independent of the file.

The present invention seeks to solve the problems in the prior art. The present invention increases functionality over the prior art by creating a database structure that can store metadata without requiring the presence of files or images, while using a standard relational database. The present invention also provides an updated security model. The present invention further allows the use of APIs (Application Programming Interfaces) that allow third parties to create custom searches or functions that operate on the contents of a shopping cart.

The present invention also allows for an unlimited number of customizable data fields in the database for brands, products, jobs, projects, files, events, jobs and each user area. The present invention also achieves a distributed file management approach. This means that each file is not stored in the database, but the database tracks which file server each file is on. Thus, each file can be located on one computer, or on a computer network at any point in the world.

Finally, the present invention is a workflow tool designed to manage the entire production process from product conception and design for prepress production to conversion and promotion of print packages, using common terminology. These advantages, as well as others provided herein, solve the above and other problems.

SUMMARY OF THE INVENTION The present invention provides a system for maintaining and accessing and archiving digital assets. In an embodiment, the system integrates file and image management functions with storage of information about the files and images. In addition to providing access to graphic assets, the system associates each asset with other information,
Users can track completed work and define new projects. Further, the system information is stored in a data hierarchy complementary to the original business process.

DETAILED DESCRIPTION The present invention is capable of many different forms of embodiment, and preferred embodiments of the present invention are shown in detail in the drawings and specification, but the disclosure is not limited thereto. It is to be understood that this is merely an example of the principles of the invention, and is not intended to limit the broad aspects of the invention to the illustrated embodiments.

The present invention provides a system for tracking and managing projects in developing graphic images for product packages in the prepress field. The present invention also provides a system for managing assets used in developing a graphical image for a product package.

One embodiment of the present invention, as shown in FIG.
It may be described in the form of a system employing software 11 of a communication server running on computers 15, 16, 17 on 19, software 12 of a client system and an engine 13 of a SQL database. The communication server software of the preferred embodiment can be any server capable of making an HTTP (Hyper-text transfer protocol) connection, such as communication server software sold by Microsoft or Netscape. Further, the client software of the preferred embodiment can be any software that can make an HTTP connection. However, since this embodiment incorporates a frame and script code described in a Java script, client software capable of displaying HTML (Hypertext markup Language) incorporating the frame and the Java script is required.
V. 4.0 or higher or Netscape Navigator V. 3.0 or higher.

The client computer 15 includes a training input device 14 and a display 18. Input device 14 may include a conventional keyboard and mouse to allow a user to select items on display 18. Display 18 may be a conventional cathode ray tube display or any other suitable device that provides a visual indication to a user.

This embodiment allows for the flexibility of the setup options. Users of the system may operate and maintain the communication server and SQL database engine themselves, or use a trained and knowledgeable communication server and SQL database engine to maintain the system. obtain.

In addition, since the computer code of this embodiment exists on the communication server, the software is easily updated when the product is improved. Therefore, there is no need to update software on each computer operating on the system.
Also, depending on the high level of applicability of the client software, as long as the communication server is located on a wide area network such as the Internet, the system can be installed around the world without installing special client software. It can be operated from a computer almost anywhere. However, if desired, the system can be stored and operated on a single computer platform. Further, the computer code can be loaded onto a platform from a removable transfer medium such as a compact disk (CD).

The present invention preferably stores user data hierarchically. This means that instead of putting all the data (images, attributes, event lists) in a single large container, the data is a tree-like structure whose complexity varies with the complexity of the product being stored. That is, it is organized and stored in a structure. Preferably, there are actually two concurrent data hierarchies when working, a brand hierarchy and a project hierarchy, each providing a different view of the data. This structure not only provides an efficient way of organizing data, but also mimics the relationships found in a standard business cycle.

Referring to FIG. 2, a screen providing a user interface is shown.
In one embodiment, all of the screens selected by the user are displayed on the visual display 18 (
As shown in FIG. 1) and having the same basic structure in the present invention, each screen 20 includes a search frame 21, a control frame 22, and a data frame 23. Therefore, the frames 20, 21, 22 are displayed together on the display 18 by the client software 12. “Screen (scree) used throughout this application
The terms "n)" and "page" shall be construed to refer to frames 20, 21, and 22 above.

The underline of each phrase in FIG. 2 indicates that the phrase is a hyperlink. Each hyperlink may be selected using an input device 14 (FIG. 1) such as a mouse or keyboard attached to a computer running the client software. In the present disclosure, the terms 'click' and 'clicking' shall mean selecting a hyperlink with a mouse or keyboard. The user clicks on the hyperlink to activate the functionality of the system.

The search frame 21 of the screen 20 provides access to search functions that can be performed by clicking one of the buttons 24. The search frame 21 also provides application status by indicating the area where the user is currently working. For example, the area may be indicated by highlighting a button.

The control frame 22 includes links 26 that represent each operation to be performed. Since the control frame 22 is context-sensitive, it changes based on the application area in which the user is working. At the top is each link 26 that depends on the contents of the data frame 23. It is each link corresponding to the entire application described above that can be displayed in various colors under the above. These links are not context sensitive and are preferably always available. As shown in FIG. 2, the control frame 22 may include a thumbnail link 29, which, when clicked, causes any thumbnail images associated with the selected object to be displayed on the data frame 23. Will be displayed.

The data frame 23 is the main body of the screen 20. The data frame 23 contains data on which the user is currently working. Therefore, all of the operations performed are
Will be displayed within

Preferably, all system users have accounts for the user to log in and access system applications. Thus, a user account includes information about the user, such as a login ID, password, and email address. This information is referred to as “user information” in the control screen 22.
It can be accessed by clicking button 49.

In one embodiment, each user may modify at least some of his account information. For example, each user may update his or her email address or telephone number each time the information changes. Preferably, the only user account values that the user cannot change are the login ID and the company name. However, it is desirable to change these values to allow asset management.

As will be appreciated by those skilled in the art, the brand hierarchy is asset-oriented. Its purpose is to create a structure that logically organizes the asset data associated with brands, products, jobs and files as shown in FIG. In this example, the "Krunchy" brand 31 has two product lines 32a, 32b or "Pre
tzels ”and“ Chips. ”Because there is one variety of“ Pretzels ”,
The hierarchy leads from brand 31 to product 32a to job 34a (ie, "job 206"). However, since there are three varieties of “Chips”, the hierarchy is from the brand 31 to the product 32b to the job 34b (that is, the job 226). Brand Tier 30
May have as many levels of brands 31, sub-brands, products 32, and sub-products 33 as necessary to properly organize their content.

Referring again to the example of FIG. 3, and further down the hierarchy 30, a “Pretzels” product 32a and a “Potate” product 32b are associated with a job 34. For each job 34,
A group of files 35 used when generating the job is associated.

The project hierarchy is production-oriented. Its purpose is to create a structure that organizes the production data associated with projects, jobs and events, as shown in FIG. In this example, the "Winter Promo" project 37 includes two jobs 34b, 34c, each of which includes a group of events 38 to be performed before the job is completed. The project also includes a group of events 39 relating to the project itself. Like Brand Tier 30,
The project hierarchy 36 can be broken down into as many systematic levels as needed. Each project may include several levels of subprojects before identifying the list of required jobs and events.

As shown in FIGS. 3 and 4, the “Krunchy” brand hierarchy 30 and “Winter
The Promo hierarchy 36 contains “Job 226” (ie, reference numeral 34b), which
This is because the above two layers intersect at the job level.

Each job can be arranged from both an asset perspective and a production perspective. From an asset perspective, a job is a collection of required data elements, ie, files. From a production point of view, a job includes a series of steps or events to occur from start to finish. Because jobs have this dual perspective, each job is included in both tiers and presents a place to intersect from one tier to the other.

FIG. 5 shows the intersection at the job level between the layers in FIGS. 3 and 4. “Job 226” (ie, reference numeral 34b) is part of both the “Winter Promo” project 37 and the “Krunchy” brand 31. Looking at each event associated with "job 226" 34b, the user sees the job from a production point of view; looking at each file associated with that job causes the user to view the job from a production point of view. The user moves down one of the layers to “job 22
6 "34b. Further, the user can access each event and each file associated with that job, regardless of which level down the hierarchy. This double-crossing at the job level The hierarchy is represented by the layout of each button in the search frame 21 in the user interface 20, which is described in further detail herein below.

As mentioned above, the present invention employs three main functional areas: 1) brand or asset management, 2) project management, and 3) file exchange. In one embodiment, the present invention also provides management functions for establishing system parameters and security.

With brand management, users can maintain and organize files associated with particular brands and products. As indicated above, a brand is a product line. Brands may include additional brands that are separate brands within the product line. However, in the end, a brand or sub-brand will include at least one product. There may also be additional products within a particular product. However, in the end, a product or a sub-product includes at least one job. Each job includes a file to be associated with the job and / or an event that occurs within the job. Thus, each file is a design element of a product package. The file can be an image, font, document, or any other design element. Each event is associated with a product package design process and is further described with respect to project management functions. Brands, products, jobs, files and events are collectively referred to as assets or objects. For example, since there may be different types of assets such as sub-brands or products within one brand, the content of the assets may be collectively referred to as sub-assets.

The brand management part mainly organizes and displays the following four main information items: 1)
List of subordinate assets, 2) contact maintenance function, 3) brand asset search function, 4) asset maintenance function. The brand management portion also provides a simple link to each event associated with a particular asset.

Preferably, there are three ways to find information in the system database:
Browsing, navigating, and searching. The method chosen depends both on the type of data to be discovered and where the user is known about the data.

[0038] The browse method allows a user to proceed level by level through either the brand hierarchy or the project hierarchy and observe the contents of the hierarchy at each level.
Browsing is conceptually similar to using a web browser. Just as selecting a website and clicking on the appropriate link to focus on the desired information, browsing allows users to select a brand by clicking on each link to narrow its scope. To select a sub-product, then a job, and finally a file or event. Each time the user clicks a link to move to a deeper level, the contents of data frame 23 are replaced with new information. Browsing is context-focused, and should be adopted if it is determined that it is useful to observe detailed descriptions and visual cues of objects as the user moves down the hierarchy. It is.

According to the navigating method, the user can observe the entire outline of the brand hierarchy, and then focus on a specific level of object. Navigating is conceptually similar to using MACINTOSH FINDER or MICROSOFT WINDOWS EXPLORER. In any application, the user clicks on the extended icon following any folder to view a list of its contents. Similarly, when navigating using the present invention, the user clicks on the icon to view the contents of the brand, sub-brand, product, sub-product and job in outline form. Each time the user clicks, the outline is expanded, while the contents of the previous outline remain in the data frame 23. Navigating is relationship-focused, and when the user does not need graphical cues or wants to understand the overall structure of the system database and observe how the various objects relate to each other. This is the preferred method.

According to the search method, the user can find one or a group of objects satisfying a specific group of criteria. Search is conceptually similar to a web-based search tool. Just as a user would use a web search tool to find “pages containing information about digital prepress,” a search in the present invention would allow a user to “brand X jobs completed in January this year. All associated files "can be found. The search is criterion focused and the user does not remember where the objects were stored in the data hierarchy, or requested that the user find multiple objects that were not stored together in each data hierarchy. This is the preferred method to take when you want.

As described above, browsing allows a user to find an object by moving down a particular branch of the brand or project hierarchy and verifying its contents. At each level, the user may choose to further focus or verify detailed information about the object. Each time a user requests new information, the data frame is updated.

In the following, representative steps for browsing the brand hierarchy in a database called the “Whacky Foods” database are shown. Of course, the user's database will contain various information, and in the following the functions of the embodiment of the browse tool are described for illustrative purposes.

After logging on to the system, a top-level brand page 40 is provided on the system display as shown in FIG. At the top of page 40 is a search frame 21. In addition to providing access to search tools, search frame 21 indicates which area of the data hierarchy the user is currently browsing by indicating application status. For example, since a brand is being browsed, the "Brand" button 25 is highlighted in FIG.

At the top of the data frame 23, a page title 41 indicates the type of object being browsed. For example, FIG. 6 shows a “brand list”. The representative "Whacky Foods" database used in this description is set up so that the top brand is a category instead of the actual brand name brand. This allows brand and product information to be organized by business units or product groups already in place. In the "Whacky Foods" database above, there are two top brands for illustrative purposes: "Consumer" and "Organization".

Below the title 41, there is a route confirmation window (wayfinder) 42. This route confirmation window
Displays the level of the hierarchy that forms the path to the current object and allows the user to click the link and return to any level. The route confirmation window 42 is described in further detail herein.

A display record popup 43 is displayed below the route confirmation window 42.
There is. The display record popup allows the user to display the next group of records when more records are read than can be displayed on the screen at one time. The number of records displayed is defined by system settings and may vary for list, thumbnail, and contact sheet views. For example, if the list display setting is set to "5 records" and the database contains 20 brands, the display record pop-up will initially display "Records 1-20 of the 20 records found. Show 5 ". Using the pop-up 43, the user can then record 6-10, then record 11-1
5 and so on can be displayed.

At the bottom of the page is a data table 44. The data table lists all the objects in the hierarchy at this level and provides a column 46 of information about each object. By clicking on the data table column title 47, the table is sorted alphabetically or numerically by column. An arrow 48 following the column name indicates whether the column was sorted in ascending order “↑” or descending order “↓”.

The contents of the data table 44 change depending on the type of object being browsed. For example, a brand may display one group of columns and a job may display another group of columns. However, the object name 50, the manager 51, and the list 52 are columns common to the data tables of many objects. Object name column 50
(“Brand name” in FIG. 6) includes a link 54 representing the name of each object. Clicking on the object name link 54 displays a detail page for the object, which is described in more detail herein and provides in-depth information about the object. .

The manager column 51 includes a link 56 representing the name of the person to be contacted for the object. Clicking on manager link 56 displays a contact details page that provides information about the manager, such as a link that can send an email message to the manager.

The list column 52 includes a lower asset hyperlink 58, which represents a lower asset in the data hierarchy (lower brand in FIG. 6) that is lower than the current asset. Thus, by clicking on the list link 58, the selected lower asset is drilled down to the next level in the hierarchy.

Preferably, each list link 58 is a phrase that indicates what type of sub-assets or objects the asset includes, such as “sub-brand”, “sub-product” or “product”. Therefore, when the list link 58 is clicked, the data frame 23 changes, and a screen displaying each asset or object in the clicked lower-level asset is displayed. For example, by clicking the list link 58 in FIG. 6 for the brand “consumer”, the data frame 23 is changed to the content displayed in FIG. The resulting page displays the associated name brand (ie, sub-brand) below the consumer brand, such as “Cyber Snacks”
, "Krispy" food and "Youbetcha" vegetables. It should be noted that the present invention supports a data hierarchy having many levels of brands, sub-brands, products and sub-products.

Moving further down in the hierarchy to the “Youbetcha” brand is done by clicking the “lower brand” list link 58 in the list column 52 in the bottom row of FIG. By clicking on the "lower brand" list link 58 for the lower brand "Youbetcha", the data frame 23 becomes "Youbetcha" as shown in FIG.
"Youbetcha" as shown in the list column 52 has another level below it, consisting of the next four sub-brands. : Super Beans, Super Carrots, Super Corn and Su
per Peas. By clicking further down the hierarchy, depending on which sub-brand is selected, the user reaches another level of sub-brand or product level.

By clicking on the “Products” list link 58 for the next sub-brand “Super Corn” in the bottom row of table 44, the “Super Corn” sub-assets (ie, products) are displayed as data in FIG. Shown in frame 23. Title 41 is now shown as a "product list" and the data frame is at the top "Super"
Provide user access to Corn ”products.
Just like the "brand list" page, the "product list" page includes a data table 44 listing its contents, ie, available sub-products. “Su
There are four sub-products under the "per Corn" brand, all of which include additional sub-product links or job links that appear in the list column 52 of the product list page.

Clicking on the “lower products” list link 58 in the “Mexican Super Corn” product list column 52 of FIG. 9 displays the lower products as shown in FIG. This page lists the three sub-products below the Mexican Super Corn product. Furthermore, these products are more detailed and probably correspond to the actual products that are sold. Since each product at this level is so detailed, there are no more sub-products below them. Instead, they have jobs.

In addition, certain products include a product template in addition to the job. These product templates are used to provide storage for design templates associated with the product.

The “Job” associated with the “15 oz, Mexican Super Corn” product in FIG.
When the list link 58 is clicked, a list of each lower-level job of the product is displayed as shown in FIG. These three jobs are “15 oz, Mexican Su
per corn ”product. Each job is“ 15 oz, Mexican Super Co
rn "indicates a single iteration of the product label.

In FIG. 11, the title 41 of the data frame 23 has been appropriately changed to “job list”. Further, data table 44 includes other types of information other than brands or products. Instead, the data table includes a job number, a job name, a job manager, a job language, a job due date, a job last date, and a job status.

As shown in FIG. 11, the job “15 oz, Mexican Super Corn Baseline” includes two list links, one indicating “event” and the other indicating “file”. Thus, in list column 52, the user may select a link to view either each file or each event associated with the job. Clicking on the "file" link 62 will bring the file list page of FIG. 12 down one level further to the bottom of the brand hierarchy. Clicking on the "Events" link 64 will cross over to the project hierarchy and display the event list page.

In FIG. 11, the intersection of the brand hierarchy and the project hierarchy is “file”.
Note that list link 62 and “event” list link 64 provide. Thus, the user can switch between the two tiers at the job level.

Clicking on the “Files” list link 62 associated with “15 oz, Mexican Super Corn Baseline” in FIG. 11, a list of files included in the job is displayed as shown in FIG. The title 41 of this page is "File List", and this page lists the files associated with the job and displays the software application, file format, creation date and size associated with them. Although nine files are associated with the job shown in FIG. 12, initially only four are displayed in the data table.
By using the display record pop-up 43, the user may first view files 5-8 and then finally file 9 for the remaining files in the list.

The first column 66 of the data table 44, the cart, provides a reference to the user's shopping cart, which comprises a storage area from which the user can collect files. Cart row
An icon 68 to the left of 66 indicates whether the file is in the shopping cart or outside the shopping cart. The icon 70 on the right allows the user to move the file into or out of the shopping cart.

Note that each file is at the bottom of the data hierarchy. Since there are no objects or assets under each file in the hierarchy, there is no list column in the data table 44 on the file list page in FIG.

As indicated above, the route confirmation window 42 provides a jump to another level of the hierarchy. The route confirmation window 42 displays the brand hierarchy from the top of the database (specified by the Whacky Foods company link) to the current location. Each level is displayed below the preceding level and is preceded by one of three icons, such as a registered trademark symbol that designates a brand, product or job respectively, a cylinder or a file folder.

When a link in the route confirmation window 42 is clicked, a jump is made to a page showing the contents of the selected object. Clicking on the parent level link (displayed in bold) will display a detail page for that parent object, which is described in further detail herein.

When the “consumer” link in the route confirmation window is clicked, each brand included in the consumer category as shown in FIG. 7 is displayed again, and another brand for continuing to browse the brand hierarchy is displayed. Can be selected.

As indicated above, according to the present invention, a user can browse a brand hierarchy. The user simply selects and verifies the top brand and then moves further up the hierarchy by clicking on each link in each list column of each displayed data table. Clicking on a brand, product or job name, instead of a list column link, will display a detail page, described in more detail herein, instead of digging deeper into the hierarchy. Thus, the route confirmation window can be used to return to any level in the hierarchy.

When working in the project hierarchy, the browse tools operate in the same manner. The user may browse the project hierarchy by clicking on the project link in the control frame. Once in the project hierarchy, the user selects the top-level project, and then clicks on each link in the list column of the resulting data table to ultimately move from project to subordinate project to job. You can dig into events. As in the brand hierarchy above, the user may verify the details page described in more detail herein by clicking on the project, sub-project or job name link.

By navigating, the user can verify the overall system brand hierarchy in outline form on a single page. By expanding and contracting the outline, the user can verify the relationships between the various objects. In one embodiment, the navigation tool can be used to view only the brand hierarchy, not the project hierarchy.

The description of navigating the brand hierarchy using the present invention will again be made using the same representative “Whacky Foods” database. Although the user's database will contain different information, this example illustrates the functionality of the system navigation tool.

Returning to FIG. 6, when the “Navigate” button 74 in the control frame 22 is clicked, the navigation tool starts, and the top brand as shown in FIG. 13 is displayed. At the top of the page is the system database name 76 (ie, “Whacky Foods
Under the database name 76 is a list of all objects 78 at the top of the brand hierarchy, ie, a list of top brands. All displayed objects 78 have the following three elements: Indicated by the row containing: display icon or extended icon 80, object icon 82, and object name 84.

The first element in each row is a display icon 80. If the icon 80 points to the right, the line has been collapsed and no level is displayed below the object 78.
If the icon 80 points down, the line has been expanded and the object 78
One or more levels below are displayed. If deflated, the user may click one of the icons 80 to display one level below the selected object 78. If expanded, the user may contract all levels below the selected object 78 by clicking on the icon 80.

The display icon 80 is followed by an object icon 82. The object icon simply specifies the type of object 78 that the line indicates; the trademark symbol specifies the brand, the cylinder specifies the product, and the file folder symbol specifies the job. .

The object icon 82 is followed by an object name 84 for identifying the object. If the object name 84 is displayed as a hyperlink, clicking on the link will display the detail page for that object.

When the display icon 80 at the top of the “consumer” brand is clicked, lower-level brands in the consumer category are displayed as shown in FIG. In this example, three brands are displayed under the consumer category: "Cyber Snacks", "Kris
py ”food and“ Youbetcha ”vegetables.

When the display icon 80 at the head of the “Youbetcha” brand is clicked, a lower brand under the brand is displayed as shown in FIG. In this example,
Under the “Youbetcha” brand there are four sub-brands: “Super Beans”, “Su”
per Carrots "," Super Corn "and" Super Peas ".

Clicking on the display icon 80 at the top of the “Krispy” brand allows the user to verify that part of the brand hierarchy as well. As shown in FIG. 16, the outline is expanded to show two sub-brands under the “Krispy” brand. “Krispy Flake
The "s" brand can be further expanded to reveal its content, because display icons have been deployed, since the "Krispy Puffs" brand has no lower-level objects in the hierarchy, No icon is displayed at the beginning.

By expanding and contracting various objects, the user can enter “Youbetcha”
The object hierarchy below the brand may be further verified. Navigating therefore takes on a different brand hierarchy aspect than is done by browsing. On a single page, the user can not only find a particular job, but also compare each object. For example, as shown in FIG. 17, the "Cheese Super Corn" product is one size, the "Mexican Super Corn" is three sizes, and the "Mexican Super Corn"
"Is the only product with a $ 0.20 coupon.

When the top display icon of the “Mexican Super Corn” product is contracted, FIG.
As shown in FIG. 8, all lower levels are hidden. Hence, “15 oz, Mexican
The contents of both the "Super Corn" and "Mexican Super Corn" products are hidden.

As shown in FIG. 19, when the “Mexican Super Corn” product is expanded, the lower three products are displayed again. Note that when the "Mexican Super Corn" product is expanded again, two levels were displayed before it was contracted, but only the lower one level is displayed. Therefore, when the object is contracted, all lower levels are contracted. However, even when the object is expanded, it is preferable that only one lower level is displayed.

During navigation, according to the present invention, the user can preferably jump to the browse mode at any level of the data hierarchy by clicking on the object name link. Thus, doing so opens a detail page for the selected object, which is described in more detail herein.

The above is illustrative of navigating the brand hierarchy. In summary, navigating is initiated by clicking on a navigating button in the control frame. Once the navigating page is displayed, the user can expand or contract the object outline by clicking to expand or contract the display icon. An object without a display icon at the top does not have a lower object in the hierarchy. Expanding the outline also displays one additional level below the selected object. Shrinking the outline hides all levels below the selected object.

Preferably, when the user first clicks the navigate button, the top brand is displayed in the data frame. If the user expands some objects, leaves the navigate page without logging out, and then returns there, the system remembers the state of the data frame that the user last navigated to and that state Is displayed. Thus, even if the user expands multiple objects, selecting to view the detail page for one object does not mean that the user should re-expand all when resuming navigation.

On the other hand, according to the search, the user can find one or a group of objects satisfying a certain description. This description is created by identifying the search criteria, i.e., the group of attributes and properties that characterize these objects. The user may search for any type of object (brand, product, job, file, event or project).

The search can be performed when the user does not remember where the object is stored in the data hierarchy, when the user wants to recognize and quickly aim where the object is stored, or together. A method is provided that is used when a user desires to find a plurality of objects that are not stored.

The following example illustrates how to search for products in the exemplary system database described above, the “Whacky Foods” database. Although the user database will contain different information, the following is illustrative of the functionality of the system search tool.

Returning to FIG. 6, when the “product” button 90 in the search frame 21 is clicked, a product search form 92 is displayed as shown in FIG. Although the search form includes controls, these controls allow the user to define both the user search, that is, the criteria for performing the search and the manner in which the results of the search are displayed. .

The search criteria 94 includes a group of pop-ups 96 and text boxes 98 that allow the user to specify the characteristics of each object to be found. Pop-up 96 is displayed when a selection should be made from a group of available options. Text box 98 is displayed when any value can be entered.

The display criterion 100 includes a group of pop-ups 102 that the user can indicate how to display the results of the search. Depending on the type of object for which the user is searching, the user may sort the results by various attributes in ascending or descending order,
The results can be displayed in various ways. For example, products may be displayed as a list (similar to a browse page data table) or as thumbnails (small graphical displays).

When the search page is opened, a “search” button 104, a “detailed setting” button 106 and a “reset” button 108 are added to the control frame 22. “Search” button 10
When 4 is clicked, a search is performed using the displayed search criteria 94.
Clicking the "Reset" button 108 replaces all of the modified criteria with default values. Clicking on the "Detailed Settings" button 106 displays a "Detailed Search Settings" page where more complex search criteria can be defined. In one embodiment, when the advanced search setting page is displayed, the “
“Simple” may be indicated instead of “Advanced”.

The search criterion is defined by attributes (values to be checked), operators (type of comparison to be performed) and limit values (values for which the attributes are to be checked). If no criterion is required, the user may select the "(all)" operator. As a result, all criteria are ignored, including any values entered in the limit text box.

The search criterion 94 allows the user to search by product name or product number.
21 includes a “product” criterion 110. The user may select either “name” or “number” from the first pop-up 96, as shown in FIG.
You can select an operator from the second popup, such as "(all)", "is" or "starts with". Finally, the user enters a limit value in text box 98.
Using these options, the user may define various types of product criteria, such as "product name including corn" or "product number starting with 3."

The search criterion 94 in FIG. 20 also includes a “parent product” criterion 112 that allows the user to specify the type of parent object that the found object should have. Preferably, only parent object types that are valid for the type of object the user is looking for are displayed. As shown in FIG. 22, the user may select a parent object type (ie, brand or product) and an attribute (ie, name or number) from the first two pop-ups 96. Next, the user selects an operator such as “(all)”, “is” or “begins with” from the third pop-up 96. Finally, the user enters a limit value in text box 98. Using these options, the user may define various types of parent criteria, such as "the parent brand name is Youbetcha" or "the parent product name includes snack".

The search criteria 94 of FIG. 20 further includes a “market” criterion 114 that allows a user to specify products from certain markets that should be included or excluded from the search. . As shown in FIG. 23, the user can select an operator including “is” or “not” from the first pop-up 96. Next, the user
2 From the pop-up 96, select a market such as "(All)", "Northwest", "Southeast". Using these options, the user can say, for example, "market is southeast"
Market is not northwest "may define various types of market criteria.

Returning to FIG. 20, the search criteria 94 also includes a “note” criterion 116 that allows the user to search for products that have the specified phrase or expression in the note. Returning to FIG. 24, the user may select an operator from the pop-up 96, such as "(all)", "starts with" or "includes". Next, the user inputs text to be searched into text box 98. Using these options, the user may define various types of annotation criteria, such as "an annotation includes modified" or "an annotation ends with final".

The display criteria 110 of FIG. 20 includes a “view” criteria 120. The "view" criteria has no effect on determining which objects are found. However, "
Specifying a value for the "view" criterion 120 determines how the results will be displayed upon completion of the search. The user selects "list" from the pop-up 96 as shown in FIG. The search results may be displayed as a simple list of object names, and the user may select "thumbnail" from pop-up 96 to include a graphical display of the results.

[0096] Preferably, if the user is searching for a file object, a contact sheet value is added to the view criteria pop-up so that each file found by the user is part of the contact sheet. Is allowed to be visually recognized.

The display criterion 110 of FIG. 20 also includes a “sort by” criterion 122. FIG.
According to the first pop-up 96 of the "sort by" criterion 122, as shown in FIG. 6, the user may select a "product number", "product name", "manager" or "status"
You can select a value to sort the results. The user also sees from the second popup 96
You can select ascending or descending sort order. Using these options, the user may sort the results in various manners, such as, for example, "sort by manager in ascending order" or "sort by product number in descending order."

As shown in FIG. 27, the user may specify criteria to find all products of the “Youbetcha” brand that include the phrase “Mexican” and return them in the alphabetical listing by name. This means that the user first selects “name” from the attribute popup in the “product” criteria 110 and “includes” from the operator popup 96.
And typing "Mexican" in the text box. Next, within the "parent product" criteria 112, the user selects "brand" and "name" from the attribute popup, selects "starts with" from the operator popup, and types "Youbetcha" in the text box. I do. Further, within the "sort by" criteria 122, the user selects "product name" and "ascending" from the pop-up.

By selecting the “(all)” operator in the “Market” and “Note” criteria, the user is notified that the product to be discovered is any market and any It may indicate that it may have text.

When each criterion is defined, a search is performed when the user clicks a “search” button 104 in the control frame 22. The system searches the database for each product that matches the criteria and then displays the results. The time required to perform a search depends on the complexity of the search criteria and the amount of information stored in the system database. As shown in FIG. 28, the result of the search is displayed on the product search list page 124. If no object matches the search criteria, the page includes a message indicating that the object was not found. Otherwise, the page contains the resulting object.

If more objects are found than can be displayed at one time, additional records may be viewed using the display record pop-up 43. For example, if the user criterion matches 60 products, the page may be described as "display records 1-10 of 60 found records". Using the pop-up 43, the user may display each of the ten subsequent product groups.

The data table 44 lists all the found objects. Clicking on a data table column title 47 sorts the table by that column 46. An arrow 48 following the column name indicates whether the sort was performed in ascending or descending order.

Clicking on a link in the “Product Name” column 126 in the product search list will display a product detail page for that product, which will be described in more detail herein. Further, when a link in the manager column 51 is clicked, a contact details page for the manager is displayed. When a link in the list column 52 is clicked, one level in the brand hierarchy is dug down, and a lower object of the product, that is, a job in FIG. 28 is displayed. If too few or too many records are returned and the search results are unsatisfactory for the user, the user may perform a new search by refining the search criteria as described in the next step.

In one embodiment, previously defined search criteria can be modified by clicking the “Product” button 90 in the search frame 21 and reopening the product search page of FIG. 27. The product search page includes the criteria previously entered by the user, because the system preferably stores the last entered search criteria for each type of object. . Even if the user logs out and logs in again, when the user reopens the search page, the system displays the user's previous criteria.

By modifying the search criteria, the user can narrow or broaden the search. If a user's previous search returns too many results, the user can narrow the search by adding additional criteria, such as specifying market criteria or product names (e.g., Frozen Mexican). ) May also be specified. If the user's previous search returned too few results, the user can extend the search by deleting previous criteria or with less detail, and the user can remove parent product criteria Sometimes. If the user's previous search returned incorrect results, the user can click the reset button to clear the criteria and start the search again.

The above describes an embodiment of finding an object using a system search tool. In summary, a user may initiate a search by clicking a button in a search frame that corresponds to the type of object the user desires, such as a project or a job. Thus, a search page opens, displaying criteria appropriate for the type of object selected. On the search page, the user defines search criteria for distinguishing objects that the user wants to find. The criteria are defined by specifying attributes, operators, and limit values. If the user does not want to search by a particular type of criterion, the user selects the "(all)" operator and the criterion is ignored. The user also defines the display criteria,
You can control how the results are displayed. Once the criteria are defined, the user performs a search by clicking the search button in the control frame and displays the results. If the user wants to refine the search just performed, the user clicks on the same search button again. The system stores previously defined search criteria. The system may also include an advanced search function that includes more complex search criteria.

In one embodiment, the advanced setting search can be started by clicking a “detailed setting search” button 106, and the search form shown in FIGS. 29 and 30 is used.
88 is displayed, providing a comprehensive search for brand data. Through the advanced brand search form 88, all brand data, contact data, modification data and display options can be searched to find brands that match the search criteria provided by the user. Similarly, the detailed setting job search form 93 (FIG. 31,
32, 33, and 34) are provided for searching for job information, job code, contact information, and modification information.

As indicated above, all system objects, ie, brands, products,
Jobs, files, projects and events can be viewed on a details page that provides detailed information about the object. However, since the information stored for each object type is different, the content of the detail page changes for each object type. The detail page is displayed by clicking a link indicating the name of the object. The path followed by the user to obtain the link is not important. In one embodiment, the user may display the product detail page by the following procedure: browse to the product list page and then click on the product name listed in the data table; expand the navigation outline to the desired Display a product and click the product name link; search for a specific type of product, and then click the product name link from the search result list page.

FIG. 35 shows a job detail page 132 displaying a lot of information about an object.
1 shows an embodiment. The number, type and content of the fields on the detail page will vary depending on the type of object being verified. Preferably, any value displayed as a link can be clicked to see more details. For example, clicking on a user name on the displayed job details page will display the contact details page for that user; clicking on the Die link will display the "type" details page. Click [More ...] after the font name to display the extended list of fonts. If the user has the appropriate security permissions, the user can modify the contents of each field on the object details page.

When the detail page is displayed, a button corresponding to an operation that can be performed by the user on the object is added to the control frame 22. Each of the available operations and therefore each of the displayed buttons is different for each object type.

When the user has finished verifying the detail page, the user can jump to another level in the data hierarchy using the path confirmation window or click a button in the control frame to perform a new operation. Can be implemented.

With the appropriate security permissions, the user can edit each field on the detail page. In one embodiment, the control frame 22 on the details page 132 includes an “edit” button 133
May be included. "Edit" button 133 when an asset is displayed in data frame 23
Upon clicking, the system displays the asset edit form 109 in the data frame 23 as shown in FIG. Within the asset edit form 109, the asset number, asset name, asset type, and asset note can be changed. After editing any or all asset data, the user may click the save changes hyperlink 118 to save the changes. While the assets shown in FIG. 36 are brands, it should be understood that all assets may have associated data that is compiled in this manner.

The control frame of the detail page includes an attribute list screen 140 as shown in FIG.
May be included as well as an asset attribute hyperlink to cause the system to display. According to the attribute list screen 140, the user can create and edit attributes associated with the asset. As shown in FIG. 37, the attribute list screen 140 includes information related to the associated attribute, such as the name and type of the attribute. The attribute list screen 140 also provides an attribute details hyperlink 142, an attribute addition hyperlink 144, and an attribute removal hyperlink 146. By clicking on the attribute details hyperlink 142, the data frame 23 is changed to display the attribute details screen 148 as shown in FIG.

The attribute details screen 148 shows information related to details of attributes such as an attribute name, an attribute type, and an attribute value. The attribute details screen also displays the attribute edit hyperlink 150
, An attribute property addition hyperlink 152 and an attribute property removal hyperlink 154. By clicking on the attribute edit hyperlink 150,
The data frame 23 is changed to an attribute edit screen 156 as shown in FIG. The attribute edit screen 156 shows information on attributes such as an attribute name, an attribute type, and an attribute sequence in a list attribute that can be edited. This is the attribute name field
158, attribute sequence drop-down list 160 and save changes hyperlink 16
Achieved by two. To change attribute names and / or attribute sequences,
Attribute name field 158 and / or attribute sequence drop-down list 160
Is changed, and the save changes hyperlink 162 is clicked.

Returning to FIG. 38, by clicking the property addition hyperlink 152, the data frame 23 is changed to display the property addition screen 164 as shown in FIG. The add property screen 164 provides a property value field 166 and a submission hyperlink 168. By typing in the property value field 166 an additional value to be associated with the selected attribute and clicking on the submit hyperlink 168, the typed value is saved as a property of that attribute.

By dancing to FIG. 38 and clicking on the property removal hyperlink 154, the data frame 23 is changed to display the property removal screen 170 as shown in FIG. Property removal screen 170 provides a property list 172 associated with a particular attribute. Each property in the property list 172 has a property hyperlink 174. Each property hyperlink 174 is indicated by a property name. By clicking on property hyperlink 174, the clicked property is removed from the attribute.

Referring to FIG. 37, by clicking on the attribute addition hyperlink 144, the data frame 23 is changed to display the attribute addition screen 176 as shown in FIG. The attribute addition screen 176 includes an attribute search form 178, a search hyperlink 180,
Provide a cancel hyperlink 182 and a new attribute hyperlink 184. If you type in the attribute search form 178 an attribute name that is already associated with another asset, but not currently associated with that asset, then click the search hyperlink 180 to search in that system If the searched attribute exists, the attribute addition screen 176 is changed to include the searched attribute in the table 181 as shown in FIG. In FIG. 43, the display sequence 18 of the searched attribute is shown.
By setting 6 and clicking the searched attribute hyperlink 188, the searched attribute is associated with the specific asset. By clicking the cancel hyperlink 182 in FIG. 42 or FIG. 43, the data frame 23 is displayed in FIG.
Is changed to display the attribute list screen 140.

Alternatively, by clicking the new attribute hyperlink 184 in FIG. 42 or FIG. 43, the data frame 23 is displayed on the new attribute screen 19 as shown in FIG.
Changed to display 0. The new attribute screen 190 includes an attribute name field 192, an attribute type drop-down list 194, and a new attribute addition hyperlink 196.
If you type a new attribute name in the attribute name field 192, select a new attribute type from the new attribute type drop-down list 194, and click the new attribute addition hyperlink 196, the typed new attribute 43, the typed new attribute appears in the attribute addition screen 176 in FIG. 43 instead of the searched attribute. Possible attribute types are
Values, lists and sets. Next, all attributes associated with a particular asset are shown in the asset detail screen for that particular asset.

Referring to FIG. 37, by clicking on the attribute removal hyperlink 146, the data frame 23 is changed to display the attribute removal screen 198 as shown in FIG. The attribute removal screen 198 provides an attribute list 200 that displays information about attributes associated with the specific asset, such as an attribute name and an attribute type. An attribute removal hyperlink 202 indicated by an attribute name is associated with each attribute. By clicking the attribute removal hyperlink 202, the clicked attribute name is removed from the specific asset.

Returning to FIG. 35, by clicking on the asset contact hyperlink 134,
Data frame 23 is modified to show an asset contact list screen 204 as shown in FIG. The asset contact list screen 204 provides information such as a contact type and a contact name regarding a manager in charge of a specific asset. Asset contact list screen
204 provides a contact edit hyperlink 206 and a contact details hyperlink 208. By clicking on the contact details hyperlink 208, the data frame 23 is changed to display the contact details screen. Edit contact hyperlink 20
By clicking 6, the data frame 23 is changed to display the manager contact edit screen. Note that, as described above, in the case of attributes, one or more contacts can be associated with a specific asset from the manager contact edit screen, and a new contact can be input to the system. It is contemplated that the current contact can be edited and that existing contacts that are not associated with the current asset can be associated.

Returning to FIG. 35, by making the asset file hyperlink 135, the data frame 23 is changed to display the lower asset list screen as shown in FIG. In one embodiment, control frame 22 may include a branding screen that appears and operates similar to brand editing screen 109 of FIG.

As indicated above, at the bottom layer of the data hierarchy are files, ie, objects that represent a particular digital asset, such as an image, logo, or other document. The shopping cart provides the user with a way to collect these files together in one area.

When the user finds the desired file, the user can load it into the shopping cart and then move it to another location to stack additional files. In one embodiment, adding a file to the shopping cart does not move the file from its location in the system data hierarchy. Instead, it simply places a reference to the file in the shopping cart.

In one embodiment, there are two types of shopping carts: primary cart and named cart. Each user has a single primary shopping cart, but may create any number of named shopping carts. Preferably, each file can only be added to the main shopping cart. The named shopping cart is filled by the load in the contents of the main shopping cart or another named cart.

In one embodiment, a user may load a company logo on one shopping cart and a product package type on another shopping cart. The user first
Create two named shopping carts: "logo" and "Dies". The user then stacks the logo file on the main shopping cart, loads the contents of the main shopping cart into the "logo" cart, and then discharges from the main cart. The user then stacks the package type files in the ejected main cart and loads the new contents into the "type" cart. In one embodiment, the user can even create another named shopping cart named "Logo and Type" and even load the contents of both named carts onto the cart.

What each user does ultimately with each file stacked in the shopping cart may depend on the options set during system installation and may vary from site to site. For example, a system installation may allow a user to download a file or transfer a file to another computer.

In describing the operation of the shopping cart in this embodiment, an exemplary system database, the “Whacky Foods” database, is used again. Although the user's database may contain different information, these examples illustrate the functionality of a shopping cart.

The files stored in the system data hierarchy can be added to the user's primary shopping cart. Once in the main cart, each file can be loaded into a named shopping cart. To add files to the main shopping cart, the user preferably first finds the desired file by browsing, navigating or searching.

As described above, the file list page of FIG. 12 can be opened by using the “Browse” button 65 or a search tool. The file list page contains files that the user can add to the main shopping cart. The first column 66 in the data table 44 is titled "Cart". The cart column 66 includes an icon 68 indicating which file is in the shopping cart, and an icon 70 allowing the user to put files in and out of the shopping cart. The icon 68, or status icon, to the left of the above column indicates whether the file is currently in the main shopping cart (the file is in the main shopping cart; the file is not in the main shopping cart). The icon 70 on the right side of the column, the action icon, indicates the action that will occur if the radio button 71 preceding the icon is selected (move file into main shopping cart; move file out of main shopping cart). Identify.

For example, by clicking the radio button 71 preceding the action icon 70, the pinata.eps and redpeps.eps files are selected to be included in the main shopping cart, resulting in the data table 44 shown in FIG. obtain. If the user changes his mind after selecting the action icon for the file, the user clicks the radio button 69 preceding the status icon 68 to restore the file to its original shopping cart state. Further, when the reset button (FIG. 12) in the control frame is clicked, all the files are restored to the original state.

Preferably, clicking the radio button 71 preceding the action icon 70 does not immediately move the file in or out of the shopping cart. Instead, the user must click the Save button (FIG. 12) in control frame 22 to validate the action. Thus, the user may click on / off the action and status icon radio buttons without making accidental changes to the shopping cart.

Referring to FIG. 48, opening the main shopping cart displays which files are currently in the cart and allows the user to manipulate the contents of the cart. FIG.
The "Main cart contents" page shown in FIG. 8 is opened by clicking the shopping cart button 97 (FIG. 12) of the above-mentioned control frame. For each item in the cart, a thumbnail, a file name link, and a shopping cart icon are displayed. Thumbnails provide a graphic preview of the contents of the file. The file name link appears below the thumbnail. Clicking on this link opens a file details page where the user can verify detailed information about the file.

[0133] Below the file name link is a shopping cart icon. To remove an item from the shopping cart, the user clicks a radio button preceding the action icon. To return an item to the shopping cart, the user clicks the radio button preceding the status icon. Preferably, the item is not immediately removed from the shopping cart when the action icon is selected. Instead, the user preferably clicks the save button in the control frame to take that action.

At the bottom of the page is a line-by-line file pop-up that can be used to change the number of files displayed in each line of the page. For example, if "2" is selected from the pop-up in FIG. 48, two files are displayed instead of four files per line.

When the contents of the main cart page are 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 items) If the Empty button is not displayed: 1)
"Cart" button: Clicking this button displays a page listing the shopping carts that the user can access, such as the user's primary cart and named cart, and the user can click the cart name link to view the contents of the enumeration cart. 2) "Load" button: Clicking this button allows the user to load the contents of any shopping cart into the displayed cart, and preferably, upon loading, The files in the selected source cart are appended to the displayed cart contents; 3) "Replace" button: When this button is clicked, unlike the loading operation, the user will be able to copy the displayed shopping cart contents. You can replace the contents of another cart, and the contents of the displayed cart will be replaced before adding a new file. Deleted; 4) "Eject" button: Click this button to remove all files from the displayed cart; 5) "Remove All" button: Click this button to move to the page The eject action icons for all files in the displayed cart are selected for removal and marked for removal (even if they are files), but preferably each file is not removed until the save button is clicked 6) "Reset" button: Clicking this button returns the shopping cart to the state when the user first opened the page; and 8) "Save" button: Clicking this button causes shopping. All changes made to the cart contents are permanently saved.

Preferably, when the contents of the named cart page are displayed, the following buttons are added if appropriate: 1) "Delete" button: Clicking this button will cause the named shopping cart to be displayed. The named shopping cart is deleted, displaying a confirmation dialog box before being deleted; and 2) an "Edit" button: when this button is clicked, the user copies the name of the shopping cart to another shopping cart. Can be changed to a unique name that has not been assigned.

As noted above, named shopping carts are used to stack a group of files and organize them under descriptive titles. According to the invention, the user
Multiple named shopping carts can be created and saved. Since the named shopping cart created by the user belongs only to the user, other users cannot examine the named shopping cart or access the contents. In addition, the user's named shopping cart remains in the shopping cart list even after the user logs out and persists until the user explicitly deletes the named shopping cart.

In one embodiment, the user can create a named shopping cart where the files needed to redesign a Mexican Super Corn product can be collected. Returning to FIG. 12, when the user first clicks the "shopping cart" button 97, the contents of the main shopping cart are displayed, for example, as shown in FIG. When the user clicks the "cart" button in the control frame 22, a list including the names of all the shopping carts of the user is provided as shown in FIG. Next, the user sets the control frame
Click the "Add Cart" button in 22 to specify the name for the new shopping cart. As a result, the cart addition display shown in FIG. 50 is shown, and the user can specify a name for the new shopping cart, such as "MexCon Redesign". Next, when the user clicks the "add cart" button, the cart list page is displayed again, at which time a new shopping cart is enumerated as shown in FIG.

Once the user has created a named shopping cart, the user can add files to the cart. Preferably, however, the user cannot directly add files to the named shopping cart. Instead, the user first adds the desired files to the main shopping cart and then loads the contents of the main cart into the named cart. If desired, the user may empty the primary cart before starting the file stacking to ensure that only the desired files are added.

In the following, “Me” from the main shopping cart will be described using an embodiment of the present invention.
A representative example is provided for loading files into the "xCon Redesign" shopping cart. First, when the user clicks the shopping cart button 97 in the control frame 22 of FIG. 12, the contents of the main shopping cart are displayed, as shown in FIG. Here, the user can verify that only the desired files to be loaded into the “MexCon Redesign” cart are in the primary cart. If the primary cart contains files that should not be loaded, If so, the user removes each file from the cart by clicking the radio button preceding the retrieve action icon for those files and then clicking the "Save" button in control frame 22.

Next, when the user clicks the “cart” button in the control frame 22, FIG.
Is displayed, and the shopping carts of the user are listed. FIG.
At 1, the "MexCon Redesign" shopping cart has no files.
Thus, the user opens the "MexCon Redesign" shopping cart and adds files into it.

Next, when the user clicks the “MexCon Redesign” link, the “MexCon Redesi
The content of the “gn” page is displayed as shown in FIG. 52 with the message “MexCon Redesign shopping cart is empty”. Next, when the user clicks the "Load" button in the control frame 22, the page shown in FIG. 53 is displayed, and the user selects the shopping cart containing the file to be loaded into the "MexCon Redesign" shopping cart. obtain.

Next, when the user clicks on the “Main Cart” link, the files from the main shopping cart are loaded into the “MexCon Redesign” shopping cart and the contents of the “MexCon Redesign” cart are shown in FIG. Is displayed as follows:
Preferably, each file remains in the primary shopping cart even if each file is loaded into another shopping cart. In the above example, the main cart
Although the files were loaded into the "MexCon Redesign" cart, loading files from any shopping cart to another shopping cart is also encompassed by the present invention.

As mentioned above, all system users have one main shopping cart and can create additional named shopping carts to further organize the files they want to store. For the main shopping cart, only the files displayed on the file list page can be added. To place each file in the named shopping cart, the user preferably adds each file to the main shopping cart and then moves each file to the named cart using the load or replace function.

Furthermore, as described above, when the shopping cart page is displayed, the control frame 22 is provided with a button for providing access to an operation that can be performed by the user on the shopping cart. There may be custom shopping cart operations available at certain system sites, such as those that allow a user to transfer files from a shopping cart to another computer.

Operations are performed on each file collected in the shopping cart with the user's name, such as the file size based on whether the file is a font, image or other design element, File format changes or more advanced features. In addition, files collected in a user's named shopping cart may be routed over a local or wide area network to send the file to another user or another database.

As described above, the present invention provides a project management function that allows a user to set up a project, manage a group of jobs for a particular project, and complete the project. Tasks to be completed within a time frame may be assigned. A project is a specific campaign or promotion for a given brand. A job is a specific print run for a promotion.

With reference to FIG. 6, by clicking on the “project” hyperlink 300 in the control frame 22, the data frame 23 is changed to display a project list screen 302 as shown in FIG. The project list screen 302 shown in FIG. 55 includes the manufacturer “Whacky Foods” as indicated by the route confirmation window 20.
Display information about the project for. The project list screen 302 also includes a project details hyperlink 304 and a job list hyperlink 3
06 is also provided. In addition, the control frame 22 includes a project addition hyperlink 308. By clicking on the project addition hyperlink 308, the data frame 23 is changed to display the project addition screen 310 as shown in FIG. In the project addition screen 310, the project data such as the project number, the project name, the scheduled date, the actual start date, the due date, the actual end date, and the note can be changed in the status drop-down list 314 and the save hyperlink 316 is clicked. It contains a field 312 for inputting. A new project is created by entering project information in form 312, selecting a project status from project status drop down list 314, and clicking save changes hyperlink 316.

Returning to FIG. 55, clicking on the project details hyperlink 304 changes the data frame 16 to display a project details screen 318 as shown in FIG. The project details screen 318 includes the same information as the project list screen 302 for a specific project. The control frame 22 of the project details screen 318 includes the lower project hyperlink 320 and the job hyperlink 3
22, including an event hyperlink 324, a contact hyperlink 326 and a security hyperlink 328. By clicking on the lower project hyperlink 320, the data frame 23 is changed to display a new project detail screen 318 for any lower project. By clicking the job hyperlink 322, the lower asset list screen of FIG. 11 is displayed. Clicking on the event hyperlink 324 changes the data frame 23 to display the event list screen 336 associated with the project, as shown in FIG. Event list screen 336 is described in detail below.

Returning to FIG. 57, by clicking on the edit hyperlink 326, the data frame 23 is changed to display the project edit screen 334 as shown in FIG. Within the project edit screen 334, all information about the project may be edited and saved, as described above for other data types. By clicking on the contact hyperlink 328, the data frame 23 is changed to display a contact list screen 284 as shown in FIG. By clicking on security hyperlink 330, data frame 23 is modified to display a security screen described below with respect to management functions.

Returning to FIG. 55, by clicking on the job hyperlink 308, the data frame 23 is changed to display a lower asset list screen including the job as shown in FIG.

Returning to FIG. 11, by clicking on the lower asset hyperlink 64 indicating the event, the data frame 23 is changed to display the event list screen 336 as shown in FIG. The event list screen 336 includes pertinent information about events planned in the job, such as event name, event contact, event due date, event end date, and event status. The event list screen 336 also provides an event name hyperlink 338, an event contact hyperlink 340, and an event addition hyperlink 342. By clicking on the event name hyperlink 338, the data frame 23 is changed to display an event detail screen 344 as shown in FIG. The event details screen 344 includes an edit hyperlink 346 in the control frame 22 and a contact hyperlink 3
Provides 48 and email hyperlink 350.

In one embodiment, a management function is provided. Referring to FIG. 62, to provide system security against unauthorized access, a login name field 402,
A login screen 400 providing a password field 404 and a login hyperlink 406 is provided. To log in, the user types a valid login name in login name form 402, a valid password in password form 404, and clicks on login hyperlink 406. If the login name and password are valid, the lower asset list screen 40 of FIG. 6 for the company with which the user is associated appears. By clicking on the logout hyperlink 408 in the control frame 22 of FIG. 6, the user is automatically logged out and returned to the login screen 400.

In one embodiment, screen 40 of FIG. 6 may include a “management” hyperlink (such as reference number 407 in FIG. 57), in which case clicking on the link causes data frame 23 to be displayed. Is changed to show a title management screen 410 as shown in FIG. Five management hyperlinks are provided in the control frame 22: company hyperlink 412, group hyperlink 414, code table hyperlink 416, login hyperlink 418, and lock hyperlink 420.
It is. Data frame 23 by clicking on the company hyperlink 412
Inside, a company list screen 422 as shown in FIG. 64 is displayed. In addition, a company addition hyperlink 424 is added to the control frame 22. The company list screen 422 provides information on all companies associated with the system.
The company list screen 422 also includes a company name hyperlink 426, an email hyperlink 4
28 and a contact hyperlink 429 are also provided.

By clicking the company addition hyperlink 424, the data frame 23 is changed to display the company addition screen 430 as shown in FIG. Company additional screen 4
30 is a form 432 for company name, address, city, state, zip code, phone, fax, email, etc., a country drop down list 434, and a status drop down list
436 and a save changes hyperlink 438. Type the appropriate information in each field 432, select the correct country and status from each of the drop-down lists 434, 436 and click the Save Changes hyperlink 438, then add new company information to the above system Is done.

By clicking on the company name hyperlink 426 in FIG. 64, the data frame 23 is displayed as shown in FIG. 66, with appropriate information regarding the customer company such as company name, company address, company telephone, company fax, company status, etc. Changed to include company detail screen 440 containing information. The company details screen 440 further includes a company edit hyperlink 442 and a company contact hyperlink 444. By clicking on the company edit hyperlink 442, the data frame 23 is changed to display a company edit screen 446 as shown in FIG. By changing the information in each field of the company edit screen 446 and clicking the change save hyperlink 448, the information for the company is updated.

Referring to FIG. 66, by clicking on the company contact hyperlink 444, the data frame 23 is changed to display the company contact list screen 450 as shown in FIG. The company contact list screen 450 provides information about each contact associated with the company. The contact list screen 450 also includes a contact name hyperlink 452, a contact email hyperlink 454, and a contact addition hyperlink 4.
56 is also included. By clicking on the contact name hyperlink 452, the data frame 23 is changed to display the contact details screen 458 as shown in FIG. Contact details screen 458 includes pertinent information for a particular contact, such as contact name, contact company, contact address, contact email address, and contact status. The contact details screen 458 shows the company hyperlink 460 and the email hyperlink 4
Includes 62 and contact details edit hyperlink 464.

By clicking on the contact details edit hyperlink, the data frame 23 is changed to display a contact details edit screen 466 as shown in FIGS. 70a and 70b. According to the contact details edit screen 466, the contact details can be edited and saved by clicking the save contact details hyperlink 468.

Referring to FIG. 69, clicking on the company hyperlink 460 changes the data frame 23 to display the company detail screen 440 of FIG. E in FIG.
By clicking on the email hyperlink 462, an email message can be sent to that contact.

Referring to FIG. 68, by clicking the contact addition hyperlink 456, the data frame 23 is displayed on the contact addition screen as shown in FIGS. 71a and 71b.
Changed to display 470. Change the fields on the contact addition screen 464 and click the Save Changes hyperlink 472.

Referring to FIG. 64, by clicking on the email hyperlink 428,
An e-mail message can be sent to the company. Clicking on the contact hyperlink 429 changes the data frame 23 to display the contact list 450 of FIG.

Referring to FIG. 66, by clicking on the user hyperlink 474,
Data frame 23 is modified to display a user screen 476 showing the current user for the company as shown in FIG. This user screen also provides a user added hyperlink 478. Clicking on the user-added hyperlink 478 changes the data frame 23 to display the contact addition screen 470 of FIGS. 71a and 71b.

Referring to FIG. 63, by clicking on group hyperlink 414, data frame 23 is changed to display arrow 48 as shown in FIG. The group list screen 480 displays the current user group, the user group status, and the number of users in the group. The group list screen 480 also includes a group details hyperlink 482, a group number hyperlink 484, and a group addition hyperlink 486. By clicking on the group details hyperlink, the data frame 23 is changed to display a group details screen 488 as shown in FIG. The group details screen 488 shows the details shown on the group list screen 480. The group details screen 488 further includes a group edit hyperlink 490
Contains. By clicking on the group edit hyperlink 490, the data frame 23 is changed to display a group edit screen 492 as shown in FIG. By editing each field on the group edit screen 492 and clicking the change save hyperlink 494, the group information is changed. By associating a user with a group, the right of a specific user to perform a certain function of brand management and project management and a file exchange function can be edited. Also, certain user rights may be restricted to reference only, not to editing or adding new data.

Referring to FIG. 63, by clicking on the code table hyperlink 498, the data frame 23 is changed to show a code table screen 500 as shown in FIG. The code table screen 500 is used to provide customization of the present embodiment to each specific user of the system.

Referring to FIG. 63, by clicking on the login hyperlink 502, the data frame 23 is changed to show a login screen 506 as shown in FIG. The login screen 506 displays a list of users who are currently logged in to the system.

Referring to FIG. 63, by clicking on the lock hyperlink 504,
Data frame 23 is modified to show lock screen 508 in FIG. Lock screen 5
08 displays a list of records currently locked by the above system.

While specific embodiments have been shown and described, many modifications are possible without significantly departing from the scope of the invention, and the scope of protection is limited by the appended claims. Only.

[Brief description of the drawings]

FIG. 1 is a functional block diagram of an embodiment of a working structure suitable for implementing the present invention and having a display.

FIG. 2 is a diagram showing a screen provided on the display of FIG. 1 and having a “navigate” link.

FIG. 3 is a diagram illustrating a brand hierarchy structure that organizes asset data associated with brands, products, jobs, and files.

FIG. 4 is a diagram showing a project hierarchical structure for organizing production data associated with a project, a job, and an event.

FIG. 5 is a diagram showing the interlacing of job levels between the respective hierarchies of FIGS. 3 and 4;

FIG. 6 shows a top-level brand page provided on the display of FIG. 1 and having subordinate brand links for “Consumer Brand Name” and “Corporate Brand Name”.

FIG. 7 shows a brand list page having a lower brand link, which is displayed in FIG. 6 in accordance with the selection of the lower brand link for “consumer brand name”.

FIG. 8 shows a brand list page having a lower brand link and a product link, which is displayed in response to selecting one of the lower brand links in FIG. 7;

FIG. 9 is a product list page having lower product links, which is displayed in response to selecting one of the product links in FIG. 8;

FIG. 10 shows a product list page having a job link, which is displayed in response to selecting one of the subordinate product links in FIG. 9;

FIG. 11 is a job list page having an event link and a file link, and shows a job list page displayed in response to selecting one of the job links in FIG.

FIG. 12 shows a file list page displayed in response to selecting one of the file links in FIG. 11;

FIG. 13 shows a top navigation page including a plurality of objects, which is displayed in response to a user selecting “navigate” in FIG. 6;

FIG. 14 is a navigation page in which one object of FIG. 13 is expanded in accordance with a user's selection of the object.

FIG. 15 is a navigation page showing the object extensions of FIG. 14 according to user selection.

FIG. 16 is a navigation page showing the object extension of FIG. 15 in response to a user selection.

FIG. 17 is a navigation page showing the object extensions of FIG. 16 in response to a user selection.

FIG. 18 is a navigation page showing the object extension of FIG. 17 in response to a user selection.

FIG. 19 is a navigation page showing the object extensions of FIG. 18 according to user selection.

FIG. 20 is a search page that accepts multiple search and display criteria,
7 is a search page displayed in response to a user selection for a “product” link in FIG. 6.

FIG. 22 is a diagram illustrating search criteria supported by the search page of FIG. 20;

FIG. 23 is a view similar to FIG. 22;

FIG. 24 is a view similar to FIG. 22.

FIG. 25 is a diagram showing display determination criteria supported by the search page of FIG. 22.

FIG. 26 is a view similar to FIG. 25.

FIG. 27 illustrates an example of a search using the search page of FIG. 20.

FIG. 28 shows a product search list displayed as a result of selecting a “search” link in the search page of FIG. 27.

FIG. 29 is a detailed setting search page displayed at least partially in response to selection of a “detailed setting” link on the search page of FIG. 20;

FIG. 30 is a view similar to FIG. 29.

FIG. 31 is a view similar to FIG. 29.

FIG. 32 is a view similar to FIG. 29.

FIG. 33 is a view similar to FIG. 29;

FIG. 34 is a view similar to FIG. 29.

FIG. 35 is a detailed page displayed as a result of a user selecting an object displayed on another page.

FIG. 36 is a brand edit page displayed as a result of the user selecting the “edit” link in the detail page of FIG. 35;

FIG. 37 is an attribute list page displayed as a result of the user selecting the “Asset Attribute” link in FIG.

FIG. 38 is an attribute detail page displayed in response to a user selecting an attribute on the attribute list page of FIG. 37.

FIG. 39 is an attribute edit page displayed in response to the user selecting the “edit attribute” link on the attribute detail page of FIG. 38.

FIG. 40 is a property addition page displayed in response to a user selecting an “add property” link on the attribute detail page of FIG. 38.

FIG. 41 is a property removal page displayed in response to a user selecting a “remove property” link on the attribute detail page of FIG. 38.

FIG. 42 is an attribute addition page displayed in response to a user selecting an “add attribute” link on the asset attribute page in FIG. 37.

FIG. 43 is another attribute-added page displayed in response to the user selecting the “search” link in FIG. 42.

FIG. 44 is a “new attribute addition” page displayed in response to the user selecting the “new attribute” link in either FIG. 42 or FIG. 43.

FIG. 45 is an “attribute removal” page displayed in response to a user selecting an “attribute removal” link on the asset attribute page of FIG. 37.

FIG. 46 is a “contact list” page displayed in response to a user selecting a “contact” link on the detail page of FIG. 35;

FIG. 47 is a data table provided by the “file list” page of FIG. 12, which has been selected by the user.

FIG. 48 shows a “contents of main cart” page displayed in response to a user selecting a “shopping cart” link in FIG. 12.

FIG. 49 is a “Cart List” page displayed in response to the user selecting the “Cart” link in FIG. 48.

FIG. 50 is an “add cart” page displayed in response to the user selecting the “add cart” link in FIG. 49.

FIG. 51 is a representative “cart list” page displayed in response to the user selecting the “add cart” link in FIG. 50.

FIG. 52 is a “contents of user's cart” page displayed in response to a user selecting a user-defined cart link in FIG. 51.

FIG. 53 is a “load file to user's cart” page displayed in response to the user selecting the “load” link in FIG. 52.

FIG. 54 is a “contents of user's cart” page displayed in response to a user selecting a cart link in a “load file to user's cart” page in FIG. 53.

FIG. 55 is a “project list” page displayed in response to the user selecting the “project” link in FIG.

FIG. 56 is an “Add Project” page displayed in response to the user selecting the “Add Project” link in the “Project List” page of FIG. 55.

FIG. 57 is a “project details” page displayed in response to a user selecting a project details link on the “project list” page of FIG. 55.

FIG. 58 is an “event list” page displayed in response to a user selecting an “event” link on the “project details” page of FIG. 55.

FIG. 59 is a “project edit” page displayed in response to a user selecting an “edit” link on the “project details” page of FIG. 57.

FIG. 60 is a “contact list” page displayed in response to the user selecting the “contact” link on the “project details” page in FIG. 57.

FIG. 61 is an “event details” page displayed in response to a user selecting an event name link on the “event list” page of FIG. 58;

FIG. 62 is a “login” page provided on the display of FIG. 1 when a user wishes to enter the system.

FIG. 63 is a “management” page provided in response to a user selecting a “management” link that can be provided on the “top” page of FIG. 6;

FIG. 64 is a “company list” page provided in response to a user selecting a “company” link on the “management” page of FIG. 63;

FIG. 65 is an “add company” page provided in response to the user selecting the “add company” link on the “company list” page of FIG. 64;

FIG. 66 is a “Company Details” page provided in response to the user selecting a company name link on the “Company List” page of FIG. 64.

FIG. 67 is an “Company Edit” page provided in response to a user selecting an “Edit” link on the “Company Details” page of FIG. 66;

FIG. 68 is a “Contact List for Company” page provided in response to the user selecting the “Contact” link on the “Company Details” page of FIG. 66.

FIG. 69 is a “Contact Details” page provided in response to a user selecting a contact name link on the “Contact List for Company” page of FIG. 68.

FIG. 70a is an “edit contact” page provided in response to a user selecting an “edit” link on the “contact details” page of FIG. 69;

FIG. 70b is a view similar to FIG. 70a.

FIG. 71a is a “contact addition” page provided in response to the user selecting the “user addition” link on the “user list for company” page in FIG. 72;

FIG. 71b is a view similar to FIG. 71a.

FIG. 72 is a “User List for Company” page provided in response to the user selecting the “User” link on the “Company Details” page of FIG. 66.

FIG. 73 is a “group list” page provided in response to a user selecting a “group” link on the “management” page of FIG. 63;

FIG. 74 is a “group details” page provided in response to a user selecting a group detail link in the “group list” page of FIG. 73.

FIG. 75 is a “Group Edit” page provided in response to the user selecting the “Edit” link on the “Group Details” page of FIG. 74.

FIG. 76 is a “code table” page provided in response to a user selecting a “code table” link on the “management” page of FIG. 63;

FIG. 77 is a “login list” page provided in response to a user selecting a “login” link on the “management” page in FIG. 63.

FIG. 78 is a “lock list” page provided in response to a user selecting a “lock” link in the “management” page of FIG. 63.

[Procedure amendment]

[Submission date] April 16, 2001 (2001.4.1.6)

[Procedure amendment 1]

[Document name to be amended] Statement

[Correction target item name] 0021

[Correction method] Change

[Correction contents]

Referring to FIG. 2, a screen providing a user interface is shown.
In one embodiment, all of the screens selected by the user are displayed on the visual display 18 (
As shown in FIG. 1) and having the same basic structure in the present invention, each screen 20 includes a search frame 21, a control frame 22, and a data frame 23. Therefore, the frames 20, 21, 22 are displayed together on the display 18 by the client software 12. “Screen (scree) used throughout this application
The terms "n)" and "page" shall be construed to refer to frames 20, 21, and 22. For "thumbnails (29)": observing a thumbnail is the same information as observing a list But includes a visual representation of the logo of the sub-brand. About “Navigate (74)”: In the Navigate mode, you can use pop-down navigation to make it easier for you to use your brand and product. Can be found with the tool, which is very similar to what you might already be using on your own desktop operating system. "
About Projects (26) ": Relates to Projects (200). Currently, projects cannot have subprojects or events, even if the database is designed to support these concepts. Yes, future announcements may realize the full design.About “Shopping Cart (26)”: Active Cart is the cart with which the user can currently interact.Add files only to Active Cart Files can only be removed from the active cart or the active cart. The contents of the active cart can be stored as a named data repository for later use.
About: User info is an information that identifies a user. “
About "Logout": Logging out means terminating the operating system. About "26800": 26800 indicates the brand number.
Regarding “20400”: 20400 indicates the brand number. About “consumers”: Consumers are consuming entities. About “Analyze Skog”: Analyze skog is the name of the manager (human). Regarding “active”: “active” indicates a state. Regarding "sub-brands": sub-brands indicate hot links.

[Procedure amendment 2]

[Document name to be amended] Statement

[Correction target item name] 0051

[Correction method] Change

[Correction contents]

Preferably, each list link 58 is a phrase that indicates what type of sub-assets or objects the asset includes, such as “sub-brand”, “sub-product” or “product”. Therefore, when the list link 58 is clicked, the data frame 23 changes, and a screen displaying each asset or object in the clicked lower-level asset is displayed. For example, by clicking the list link 58 in FIG. 6 for the brand “consumer”, the data frame 23 is changed to the content displayed in FIG. The resulting page displays the associated name brand (ie, sub-brand) below the consumer brand, such as “Cyber Snacks”
, "Krispy" food and "Youbetcha" vegetables. It should be noted that the present invention supports a data hierarchy having many levels of brands, sub-brands, products and sub-products. About "Cyber Snacks": Cyber Snacks indicates the brand name (trademark). About “crispy”: Crispy indicates the brand name (trademark). Regarding “Ubeccia”: Ubeccia indicates the brand name (trademark). About "Lalla O'Brien": Lalla O'Brien indicates the name of the manager (human). About “Faunas Donahue”: Faunas Donahue shows the name of the manager (human). About “Sterling Grossman”: Sterling Grossman indicates the name of the manager (human). Regarding "active": active indicates a state. Regarding "sub-brands": sub-brands indicate hot links.

[Procedure amendment 3]

[Document name to be amended] Statement

[Correction target item name] 0052

[Correction method] Change

[Correction contents]

Moving further down in the hierarchy to the “Youbetcha” brand is done by clicking the “lower brand” list link 58 in the list column 52 in the bottom row of FIG. By clicking on the "lower brand" list link 58 for the lower brand "Youbetcha", the data frame 23 becomes "Youbetcha" as shown in FIG.
"Youbetcha" as shown in the list column 52 has another level below it, consisting of the next four sub-brands. : Super Beans, Super Carrots, Super Corn and Su
per Peas. By clicking further down the hierarchy, depending on which sub-brand is selected, the user reaches another level of sub-brand or product level. About "Super Beans": Super Beans is the brand name (trademark)
Is shown. Regarding “Super Carots”: Super Carots indicates the brand name (trademark). Regarding “super corn”: super corn indicates the brand name (trademark). About "Super Peas": Super Peas indicates the brand name (trademark). About “Cooper Sinclair”: Cooper Sinclair is the name of the manager (human). About "Fiona Natlavelie": Fiona Natlavelie is the name of the manager (human). Regarding "active": active indicates a state. Regarding "sub-brands": sub-brands indicate hot links. Regarding "Youbeccia": Youbeccha indicates the brand name (trademark).

[Procedure amendment 4]

[Document name to be amended] Statement

[Correction target item name] 0053

[Correction method] Change

[Correction contents]

By clicking on the “Products” list link 58 for the next sub-brand “Super Corn” in the bottom row of table 44, the “Super Corn” sub-assets (ie, products) are displayed as data in FIG. Shown in frame 23. Title 41 is now shown as a "product list" and the data frame is at the top "Super"
Provide user access to Corn ”products.
Just like the "brand list" page, the "product list" page includes a data table 44 listing its contents, ie, available sub-products. “Su
There are four sub-products under the “per Corn” brand, all of which include additional sub-product links or job links that appear in list column 52 on the product list page. About "super corn": cheese super corn shows brand name (trademark) About "creamed super corn": creamed super corn shows brand name (trade name) About "Mexican super corn": mexican super corn Indicates a brand name (trademark) About "Sweet Super Corn": Sweet super corn indicates a brand name (trademark).

[Procedure amendment 5]

[Document name to be amended] Statement

[Correction target item name] 0056

[Correction method] Change

[Correction contents]

Clicking on the “Job” list link 58 associated with the “15.oz. (443.59 cm ³ (15 oz), Mexican Super Corn”) product in FIG. 10 will list the lower level jobs for that product as shown in FIG. Is displayed. These three jobs are “443.59
cm ³ (15 oz), associated with the Mexican Super Corn ”product.
A single repeat of the “443.59 cm ³ (15 oz), Mexican Super Corn” product label is shown. Regarding "Frozen Mexican Super Corn": Frozen Mexican Super Corn indicates the brand name (trade name). About Maris McKinny: Maris McKinny is the name of the manager (human).

[Procedure amendment 6]

[Document name to be amended] Statement

[Correction target item name] 0058

[Correction method] Change

[Correction contents]

As shown in FIG. 11, the job “443.59 cm ³ (15 oz), Mexican Super Corn
The “Baseline” includes two list links, one indicating “event” and the other indicating “file.” Thus, in the list column 52, the user can view each file or event associated with the job. Clicking on the "Files" link 62 will allow the user to select one of the links to view any of them, and go one level further down to the bottom of the brand hierarchy to display the file list page of Figure 12. "Events" link 64 When you click, you will be crossed over to the project hierarchy and the event list page will be displayed.About "Adub Photoshop": Adub Photoshop indicates the application of the software. About "Adub Illustrator": Adub Illustrator: Indicates the application of the software “EPS file”: EPS file Is the format of the file of the software application. This is a particular format can be read by certain applications.

[Procedure amendment 7]

[Document name to be amended] Statement

[Correction target item name] 0060

[Correction method] Change

[Correction contents]

Clicking on the “Files” list link 62 associated with “15 oz. (443.59 cm ³ (15 oz), Mexican Super Corn Baseline”) in FIG. 11, lists the files included in the job as shown in FIG. Is displayed. The title of this page 41
Is a "file list" and this page lists the files associated with the job and displays the software application, file type, creation date and size associated with them. Although nine files are associated with the job shown in FIG. 12, initially only four are displayed in the data table. By using the display record pop-up 43, the user may first view files 5-8 and then finally file 9 for the remaining files in the list. Regarding “Mexican corn baseline”: The Mexican corn baseline indicates the name of the job. About “Mexican Corn Cancan Vacation Promotion”: Mexican Corn Cancan Vacation Promotion indicates the name of the job. Regarding “8023JPG”: 8023JPG is a format of a specific video file. This is a specific format readable by some applications. About "Pinata eps": Pinata eps is a format for a specific application file. This is a specific format that can be read by a specific application. “
About Red Peps eps: Red Peps eps is the format of a specific application file. This is a specific format readable by some applications. About “SC15 die eps”: SC15 die eps is the format of a specific application file. Format, which is a specific format readable by some application.For "Adobe Photoshop": Adobe Photoshop refers to an application, which is a specific format readable by some application. About "EPS file": EPS file is a format of application file, which is a specific format readable by some applications.

[Procedure amendment 8]

[Document name to be amended] Statement

[Correction target item name]

[Correction method] Change

[Correction contents]

When the display icon 80 at the top of the “consumer” brand is clicked, lower-level brands in the consumer category are displayed as shown in FIG. In this example, three brands are displayed under the consumer category: "Cyber Snacks", "Kris
"py" foods and "Youbetcha" vegetables. About "Cyber Snacks": Cyber Snacks shows brand name (trademark) About "Crispy": Crispy shows brand name (trademark)

[Procedure amendment 9]

[Document name to be amended] Statement

[Correction target item name] 0076

[Correction method] Change

[Correction contents]

Clicking on the display icon 80 at the top of the “Krispy” brand allows the user to verify that part of the brand hierarchy as well. As shown in FIG. 16, the outline is expanded to show two sub-brands under the “Krispy” brand. “Krispy Flake
The "s" brand can be further expanded to reveal its content, because display icons have been deployed, since the "Krispy Puffs" brand has no lower-level objects in the hierarchy, No icon is displayed at the beginning About "crispy flakes": Crispy flakes shows the brand name (trademark) About "crispy puffs": crispy puffs shows the brand name (trademark)

[Procedure amendment 10]

[Document name to be amended] Statement

[Correction target item name] 0077

[Correction method] Change

[Correction contents]

By expanding and contracting various objects, the user can enter “Youbetcha”
The object hierarchy below the brand may be further verified. Navigating therefore takes on a different brand hierarchy aspect than is done by browsing. On a single page, the user can not only find a particular job, but also compare each object. For example, as shown in FIG. 17, the "Cheese Super Corn" product is one size, the "Mexican Super Corn" is three sizes, and the "Mexican Super Corn"
"Is the only product with a $ 0.20 coupon. About" Sweet Super Carots ": Sweet Super Carots indicates the brand name (TM).

[Procedure amendment 11]

[Document name to be amended] Statement

[Correction target item name]

[Correction method] Change

[Correction contents]

The control frame of the detail page includes an attribute list screen 140 as shown in FIG.
May be included as well as an asset attribute hyperlink to cause the system to display. According to the attribute list screen 140, the user can create and edit attributes associated with the asset. As shown in FIG. 37, the attribute list screen 140 includes information related to the associated attribute, such as the name and type of the attribute. The attribute list screen 140 also provides an attribute details hyperlink 142, an attribute addition hyperlink 144, and an attribute removal hyperlink 146. By clicking on the attribute details hyperlink 142, the data frame 23 is changed to display the attribute details screen 148 as shown in FIG. Regarding "neatness": neatness is an example of "attributes" that a user can create. Regarding "Submit": When this hyperlink is pressed, a criterion for processing is presented and a link to the result is provided. Regarding "wordiness": wordiness is an example of an "attribute" that a user can create.

[Procedure amendment 12]

[Document name to be amended] Statement

[Correction target item name]

[Correction method] Change

[Correction contents]

Next, when the user clicks the “cart” button in the control frame 22, FIG.
Is displayed, and the shopping carts of the user are listed. FIG.
At 1, the "MexCon Redesign" shopping cart has no files.
Thus, the user opens the "MexCon Redesign" shopping cart and adds files into it. About “Mex Corn Redesign”: Mex Corn Redesign is the name of the project.

[Procedure amendment 13]

[Document name to be amended] Statement

[Correction target item name] 0148

[Correction method] Change

[Correction contents]

With reference to FIG. 6, by clicking on the “project” hyperlink 300 in the control frame 22, the data frame 23 is changed to display a project list screen 302 as shown in FIG. The project list screen 302 shown in FIG. 55 includes the manufacturer “Whacky Foods” as indicated by the route confirmation window 20.
Display information about the project for. The project list screen 302 also includes a project details hyperlink 304 and a job list hyperlink 3
06 is also provided. In addition, the control frame 22 includes a project addition hyperlink 308. By clicking on the project addition hyperlink 308, the data frame 23 is changed to display the project addition screen 310 as shown in FIG. In the project addition screen 310, the project data such as the project number, the project name, the scheduled date, the actual start date, the due date, the actual end date, and the note can be changed in the status drop-down list 314 and the save hyperlink 316 is clicked. It contains a field 312 for inputting. A new project is created by entering project information in form 312, selecting a project status from project status drop down list 314, and clicking save changes hyperlink 316. About “Redesign of Mexican Super Corn”: Redesign of Mexican Super Corn indicates the name of the project.

[Procedure amendment 14]

[Document name to be amended] Statement

[Correction target item name]

[Correction method] Change

[Correction contents]

Returning to FIG. 11, by clicking on the lower asset hyperlink 64 indicating the event, the data frame 23 is changed to display the event list screen 336 as shown in FIG. The event list screen 336 includes pertinent information about events planned in the job, such as event name, event contact, event due date, event end date, and event status. The event list screen 336 also provides an event name hyperlink 338, an event contact hyperlink 340, and an event addition hyperlink 342. By clicking on the event name hyperlink 338, the data frame 23 is changed to display an event detail screen 344 as shown in FIG. The event details screen 344 includes an edit hyperlink 346 in the control frame 22 and a contact hyperlink 3
Provides 48 and email hyperlink 350. About "Ralfivanlia": Ralfivanlia is a contact (human)
Indicates the name of About "Peppiguanza": Peppiguanza indicates the name of the contact (human). About "Harii modeler": Hari modeler shows the name of the contact (human). Regarding "Pouli Wendal": Pouli Wendal indicates the name of a contact (human). Regarding "Quinten pace": Quinten pace indicates the name of a contact (human).

[Procedure amendment 15]

[Document name to be amended] Statement

[Correction target item name]

[Correction method] Change

[Correction contents]

In one embodiment, screen 40 of FIG. 6 may include a “management” hyperlink (such as reference number 407 in FIG. 57), in which case clicking on the link causes data frame 23 to be displayed. Is changed to show a title management screen 410 as shown in FIG. Five management hyperlinks are provided in the control frame 22: company hyperlink 412, group hyperlink 414, code table hyperlink 416, login hyperlink 418, and lock hyperlink 420.
It is. Data frame 23 by clicking on the company hyperlink 412
Inside, a company list screen 422 as shown in FIG. 64 is displayed. In addition, a company addition hyperlink 424 is added to the control frame 22. The company list screen 422 provides information on all companies associated with the system.
The company list screen 422 also includes a company name hyperlink 426, an email hyperlink 4
28 and a contact hyperlink 429 are also provided. Regarding “Interchange”: Interchange indicates the name of the company (business execution entity). Regarding "Lincoln Graphics": Lincoln Graphics indicates the name of the company (business executing entity). “Pouly printing”
About: Poury Printing shows the name of the company (the entity that runs the business). About "Popii Productions": Poppy Productions indicates the name of the company (the business entity). Regarding “Prepress Pasture”: Prepress Pasture indicates the name of a company (business executing entity). About "Shiouku Graphics": ShowGraphics indicates the name of the company (the business entity). Regarding "zippy connecting": the "zippy connecting" indicates the name of the company (business executing entity).

[Procedure amendment 16]

[Document name to be amended] Statement

[Correction target item name]

[Correction method] Change

[Correction contents]

By clicking the company addition hyperlink 424, the data frame 23 is changed to display the company addition screen 430 as shown in FIG. Company additional screen 4
30 is a form 432 for company name, address, city, state, zip code, phone, fax, email, etc., a country drop down list 434, and a status drop down list
436 and a save changes hyperlink 438. Type the appropriate information in each field 432, select the correct country and status from each of the drop-down lists 434, 436 and click the Save Changes hyperlink 438, then add new company information to the above system Is done. Regarding "Save Changes": Pressing the save button saves changes to the active window.

[Procedure amendment 17]

[Document name to be amended] Statement

[Correction target item name]

[Correction method] Change

[Correction contents]

Referring to FIG. 66, by clicking on the company contact hyperlink 444, the data frame 23 is changed to display the company contact list screen 450 as shown in FIG. The company contact list screen 450 provides information about each contact associated with the company. The contact list screen 450 also includes a contact name hyperlink 452, a contact email hyperlink 454, and a contact addition hyperlink 4.
56 is also included. By clicking on the contact name hyperlink 452, the data frame 23 is changed to display the contact details screen 458 as shown in FIG. Contact details screen 458 includes pertinent information for a particular contact, such as contact name, contact company, contact address, contact email address, and contact status. The contact details screen 458 shows the company hyperlink 460 and the email hyperlink 4
Includes 62 and contact details edit hyperlink 464. About "Annaly's Skog": Annalie's Skog is a contact (human)
Indicates the name of About "Dee Thani blog": Diet blog shows the name of the contact (human). About “Faunas Donahue”: Faunas Donahue shows the name of the contact (human). About "Fiona Traveley": Fiona Traveley indicates the name of the contact (human). About "Gabriel Winker": Gabriel Winker shows the name of the contact (human). About "Laura O'Brien": Laura O'Brien indicates the name of the contact (human). About "Maris McKinney": Maris McKinney indicates the name of the contact (human). About "Sterling Grossman": Sterling Grossman shows the name of the contact (human).

[Procedure amendment 18]

[Document name to be amended] Statement

[Correction target item name] Brief description of drawings

[Correction method] Change

[Correction contents]

[Brief description of the drawings]

FIG. 1 is a functional block diagram of an embodiment of a working structure suitable for implementing the present invention and having a display.

FIG. 2 is a diagram showing a screen provided on the display of FIG. 1 and having a “navigate” link.

FIG. 3 is a diagram illustrating a brand hierarchy structure that organizes asset data associated with brands, products, jobs, and files.

FIG. 4 is a diagram showing a project hierarchical structure for organizing production data associated with a project, a job, and an event.

FIG. 5 is a diagram showing the interlacing of job levels between the respective hierarchies of FIGS. 3 and 4;

FIG. 6 shows a top-level brand page provided on the display of FIG. 1 and having subordinate brand links for “Consumer Brand Name” and “Corporate Brand Name”.

FIG. 7 shows a brand list page having a lower brand link, which is displayed in FIG. 6 in accordance with the selection of the lower brand link for “consumer brand name”.

FIG. 8 shows a brand list page having a lower brand link and a product link, which is displayed in response to selecting one of the lower brand links in FIG. 7;

FIG. 9 is a product list page having lower product links, which is displayed in response to selecting one of the product links in FIG. 8;

FIG. 10 shows a product list page having a job link, which is displayed in response to selecting one of the subordinate product links in FIG. 9;

FIG. 11 is a job list page having an event link and a file link, and shows a job list page displayed in response to selecting one of the job links in FIG.

FIG. 12 shows a file list page displayed in response to selecting one of the file links in FIG. 11;

FIG. 13 shows a top navigation page including a plurality of objects, which is displayed in response to a user selecting “navigate” in FIG. 6;

FIG. 14 is a navigation page in which one object of FIG. 13 is expanded in accordance with a user's selection of the object.

FIG. 15 is a navigation page showing the object extensions of FIG. 14 according to user selection.

FIG. 16 is a navigation page showing the object extension of FIG. 15 in response to a user selection.

FIG. 17 is a navigation page showing the object extensions of FIG. 16 in response to a user selection.

FIG. 18 is a navigation page showing the object extension of FIG. 17 in response to a user selection.

FIG. 19 is a navigation page showing the object extensions of FIG. 18 according to user selection.

FIG. 20 is a search page that accepts multiple search and display criteria,
7 is a search page displayed in response to a user selection for a “product” link in FIG. 6.

FIG. 21 is a diagram showing a list of sub-assets (attributes) having a search frame, a control frame, and a data frame.

FIG. 22 is a diagram illustrating search criteria supported by the search page of FIG. 20;

FIG. 23 is a view similar to FIG. 22;

FIG. 24 is a view similar to FIG. 22.

FIG. 25 is a diagram showing display determination criteria supported by the search page of FIG. 22.

FIG. 26 is a view similar to FIG. 25.

FIG. 27 shows an example of a search using the search page of FIG.

FIG. 28 shows a product search list displayed as a result of selecting a “search” link in the search page of FIG. 27.

FIG. 29 is a detailed setting search page displayed at least partially in response to selection of a “detailed setting” link on the search page of FIG. 20;

FIG. 30 is a view similar to FIG. 29.

FIG. 31 is a view similar to FIG. 29.

FIG. 32 is a view similar to FIG. 29.

FIG. 33 is a view similar to FIG. 29;

FIG. 34 is a view similar to FIG. 29.

FIG. 35 is a detailed page displayed as a result of a user selecting an object displayed on another page.

FIG. 36 is a brand edit page displayed as a result of the user selecting the “edit” link in the detail page of FIG. 35;

FIG. 37 is an attribute list page displayed as a result of the user selecting the “Asset Attribute” link in FIG.

FIG. 38 is an attribute detail page displayed in response to a user selecting an attribute on the attribute list page of FIG. 37.

FIG. 39 is an attribute edit page displayed in response to the user selecting the “edit attribute” link on the attribute detail page of FIG. 38.

FIG. 40 is a property addition page displayed in response to a user selecting an “add property” link on the attribute detail page of FIG. 38.

FIG. 41 is a property removal page displayed in response to a user selecting a “remove property” link on the attribute detail page of FIG. 38.

FIG. 42 is an attribute addition page displayed in response to a user selecting an “add attribute” link on the asset attribute page in FIG. 37.

FIG. 43 is another attribute-added page displayed in response to the user selecting the “search” link in FIG. 42.

FIG. 44 is a “new attribute addition” page displayed in response to the user selecting the “new attribute” link in either FIG. 42 or FIG. 43.

FIG. 45 is an “attribute removal” page displayed in response to a user selecting an “attribute removal” link on the asset attribute page of FIG. 37.

FIG. 46 is a “contact list” page displayed in response to a user selecting a “contact” link on the detail page of FIG. 35;

FIG. 47 is a data table provided by the “file list” page of FIG. 12, which has been selected by the user.

FIG. 48 shows a “contents of main cart” page displayed in response to a user selecting a “shopping cart” link in FIG. 12.

FIG. 49 is a “Cart List” page displayed in response to the user selecting the “Cart” link in FIG. 48.

FIG. 50 is an “add cart” page displayed in response to the user selecting the “add cart” link in FIG. 49.

FIG. 51 is a representative “cart list” page displayed in response to the user selecting the “add cart” link in FIG. 50.

FIG. 52 is a “contents of user's cart” page displayed in response to a user selecting a user-defined cart link in FIG. 51.

FIG. 53 is a “load file to user's cart” page displayed in response to the user selecting the “load” link in FIG. 52.

FIG. 54 is a “contents of user's cart” page displayed in response to a user selecting a cart link in a “load file to user's cart” page in FIG. 53.

FIG. 55 is a “project list” page displayed in response to the user selecting the “project” link in FIG.

FIG. 56 is an “Add Project” page displayed in response to the user selecting the “Add Project” link in the “Project List” page of FIG. 55.

FIG. 57 is a “project details” page displayed in response to a user selecting a project details link on the “project list” page of FIG. 55.

FIG. 58 is an “event list” page displayed in response to a user selecting an “event” link on the “project details” page of FIG. 55.

FIG. 59 is a “project edit” page displayed in response to a user selecting an “edit” link on the “project details” page of FIG. 57.

FIG. 60 is a “contact list” page displayed in response to the user selecting the “contact” link on the “project details” page in FIG. 57.

FIG. 61 is an “event details” page displayed in response to a user selecting an event name link on the “event list” page of FIG. 58;

FIG. 62 is a “login” page provided on the display of FIG. 1 when a user wishes to enter the system.

FIG. 63 is a “management” page provided in response to a user selecting a “management” link that can be provided on the “top” page of FIG. 6;

FIG. 64 is a “company list” page provided in response to a user selecting a “company” link on the “management” page of FIG. 63;

FIG. 65 is an “add company” page provided in response to the user selecting the “add company” link on the “company list” page of FIG. 64;

FIG. 66 is a “Company Details” page provided in response to the user selecting a company name link on the “Company List” page of FIG. 64.

FIG. 67 is an “Company Edit” page provided in response to a user selecting an “Edit” link on the “Company Details” page of FIG. 66;

FIG. 68 is a “Contact List for Company” page provided in response to the user selecting the “Contact” link on the “Company Details” page of FIG. 66.

FIG. 69 is a “Contact Details” page provided in response to a user selecting a contact name link on the “Contact List for Company” page of FIG. 68.

FIG. 70a is an “edit contact” page provided in response to a user selecting an “edit” link on the “contact details” page of FIG. 69;

FIG. 70b is a view similar to FIG. 70a.

FIG. 71a is a “contact addition” page provided in response to the user selecting the “user addition” link on the “user list for company” page in FIG. 72;

FIG. 71b is a view similar to FIG. 71a.

FIG. 72 is a “User List for Company” page provided in response to the user selecting the “User” link on the “Company Details” page of FIG. 66.

FIG. 73 is a “group list” page provided in response to a user selecting a “group” link on the “management” page of FIG. 63;

FIG. 74 is a “group details” page provided in response to a user selecting a group detail link in the “group list” page of FIG. 73.

FIG. 75 is a “Group Edit” page provided in response to the user selecting the “Edit” link on the “Group Details” page of FIG. 74.

FIG. 76 is a “code table” page provided in response to a user selecting a “code table” link on the “management” page of FIG. 63;

FIG. 77 is a “login list” page provided in response to a user selecting a “login” link on the “management” page in FIG. 63.

FIG. 78 is a “lock list” page provided in response to a user selecting a “lock” link in the “management” page of FIG. 63.

──────────────────────────────────────────────────続 き Continuation of front page (81) Designated country EP (AT, BE, CH, CY, DE, DK, ES, FI, FR, GB, GR, IE, IT, LU, MC, NL, PT, SE ), OA (BF, BJ, CF, CG, CI, CM, GA, GN, GW, ML, MR, NE, SN, TD, TG), AP (GH, GM, KE, LS, MW, SD, SL, SZ, UG, ZW), EA (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM), AE, AL, AM, AT, AU, AZ, BA, BB, BG, BR , BY, CA, CH, CN, CU, CZ, DE, DK, EE, ES, FI, GB, GD, GE, GH, GM, HR, HU, ID, IL, IN, IS , JP, KE, KG, KP, KR, KZ, LC, LK, LR, LS, LT, LU, LV, MD, MG, MK, MN, MW, MX, NO, NZ, PL, PT, RO, RU, SD, SE, SG, SI, SK, SL, TJ, TM, TR, TT, UA, UG, US, UZ, VN, YU, ZA, ZW (72) Inventor Mirror, Blues United States of America, Minnesota 55410 , Minneapolis, Ewing Avenue South 5129 (72) Inventor Ziggler, Robert United States of America, New Jersey 08108, Collingswood, East Stills Avenue 22 (72) Inventor Bruce, Mark United States of America, Illinois 60091, Wilmette, Lake Avenue 2105 (72) Inventor Lambert, Robert United States, 60656, Illinois, Chicago, North East River Road 5 143-unit F160 F term (reference) 5B075 ND20 ND36 NK43 NK46 PP03 PP13 PQ02 PQ13 PQ22 QT06 5B082 GA07

Claims (97)

[Claims] Claims 1. A portion of a brand that accepts and holds the identity of one or more brands and that is at a first level of relation, the product that accepts and holds the identity of one or more products. Part of the
At a second relationship level directly related to the one relationship level, and a portion of the job that accepts and holds one or more job identities and is directly related to the second relationship level At the level of the third relationship, comprising: a system for the management of the development of the description of the graphical package. 2. The system of claim 1, wherein the level of the first relationship is one-to-many with the level of the second relationship. 3. The system of claim 1, wherein the level of the second relationship is in a one-to-many relationship with the level of the third relationship. 4. The system of claim 1, further comprising a brand editor, a brand searcher, a company identification portion, a company editor, a brand contact identification portion, a brand market portion, a brand file portion, a brand property portion, and a brand attribute portion. 5. The system further comprises a product editor, a product searcher, a product contact identification portion, a included product portion, a product file portion, a product property portion, and a product attribute portion.
The system according to claim 1. 6. A job editor, a job searcher, a job contact identification part,
The system of claim 1, further comprising a job properties portion, a job market portion, a job event portion, and a job file portion. 7. The brand portion further comprises a lower brand portion; the lower brand portion includes a lower brand editor, a lower brand searcher, a lower brand contact identification portion, a lower brand market portion, a lower brand file portion, a lower brand property. Part, having a lower brand attribute part; the brand part stores at least one brand within itself, and the lower brand part has at least one lower brand part within itself, and at least one brand is The system of claim 1, wherein the system has at least one sub-brand associated with the brand. 8. The product part further comprises a sub-product part; the sub-product part includes a sub-product editor, a sub-product searcher, a sub-product contact identification part, a sub-product part, a sub-product file part, and a sub-product property. Part, having a sub-product attribute part; said product part storing at least one product therein and said sub-product part having at least one sub-product part therein, wherein at least one product is said product The system of claim 1, wherein the system has at least one sub-product associated with. 9. The level of the first relationship directly associated with the level of the second relationship links the brand portion directly to the product portion and includes at least one product The system of claim 1, wherein is linked to at least one brand, and the products so linked to the brand are accessible from the brand portion. 10. The second relation level, which is directly associated with the third relationship level, directly links the product part to the job part, wherein at least one job is Linked to at least one product,
The system of claim 1, wherein a job so linked to the product is accessible from the product portion. 11. The system of claim 1, wherein the brand searcher may search for a brand by at least one property value of the brand property portion. 12. The system of claim 1, wherein the product searcher can search for a product by at least one property value of the product property portion. 13. The system of claim 1, wherein the job searcher can search for a job by at least one property value of the job property portion. 14. The system of claim 1, wherein property values of the brand property portion can be used to search for files in the brand file portion. 15. The system of claim 1, wherein property values of the product property portion can be used to search for a file in the product file portion. 16. The system of claim 1, wherein a property value of the job property portion can be used to search for a file in the job file portion. 17. A project part having a project searcher, a project editor, a project contact identifier part, a project property part, a project event part, a project job part, which is directly associated with the job part. The system of claim 1, further comprising: an event portion having an event searcher, an event editor, and an event file portion, the event portion being directly associated with the job portion. 18. The system of claim 17, wherein at least one job is linked to at least one project, and wherein the jobs so linked to the project are accessible from the project portion. 19. The system of claim 17, wherein a job is linked to at least one event, and wherein the job so linked to the event is accessible from the event portion. 20. The system of claim 17, wherein the project searcher can search for a project by at least one property value of the project property portion. 21. The system of claim 17, wherein the event searcher can search for an event by at least one property value of the event property portion. 22. The system of claim 1, further comprising a collector for collecting one or more files selected from one or more of the brand file portion, the product file portion, and the job file portion into a collection file portion. System. 23. The system of claim 22, wherein the collector is capable of removing one or more files from the collected file portion. 24. The system of claim 1, further comprising a brand associator for associating at least one file with a brand entered in the brand portion.
The described system. 25. The system of claim 1, further comprising a product associator for associating at least one file with a product entered in the product portion. 26. The system of claim 1, further comprising a job associator for associating at least one file with a job entered in the job portion. 27. A brand editor, a brand searcher, a company identifier,
A part of a brand having a company editor, a brand contact identifier part, a brand file part, and at a first level of relation, having a product editor, a product searcher, a product file part, and the level of the first relation Parts of the product at the level of the directly related second relationship,
And managing the development of the graphical package description, comprising: a job editor, a job searcher, and a job file portion having a job file portion and at a third relationship level directly related to the second relationship level. System for 28. The system of claim 27, wherein the brand portion further comprises a brand market portion that accepts and holds one or more market identifiers for one or more brands. 29. The system of claim 27, wherein the brand portion further comprises a brand property portion that accepts and holds one or more property identifiers for one or more brands. 30. The system of claim 27, wherein the brand portion further comprises a brand attribute portion that accepts and holds one or more attribute identifiers for one or more brands. 31. The system of claim 27, wherein the product portion further comprises a product contact identification portion that accepts and holds one or more contact identifiers for one or more products. 32. The system of claim 27, wherein the product portion further comprises an inclusion product portion that receives and holds one or more inclusion products for one or more products. 33. The system of claim 27, wherein the product portion further comprises a product property portion that accepts and holds one or more property identifiers for one or more products. 34. The system of claim 27, wherein the product portion further comprises a product attribute portion that accepts and holds one or more attribute identifiers for one or more products. 35. The system of claim 27, wherein the job portion further comprises a job contact identifier portion that accepts and holds one or more contact identifiers for one or more jobs. . 36. The system of claim 27, wherein the job portion further comprises a job property portion that accepts and holds one or more property identifiers for one or more jobs. 37. The system of claim 27, wherein the job portion further comprises a job market portion that accepts and holds one or more market identifiers for one or more jobs. 38. The system of claim 27, wherein the job portion further comprises a job event portion that accepts and holds one or more event identifiers for one or more jobs. 39. A system for managing resources and projects, comprising at least one program stored on a removable compact transfer medium and readable by the management system, the program comprising a plurality of jobs and files. Code for creating a multi-level asset hierarchy having objects of the following; code for creating a multi-level project hierarchy having a plurality of objects including the asset hierarchy jobs and events; visualizing the asset hierarchy and the objects in the project hierarchy Code to create a display, code to allow editing of the object in the asset hierarchy and the project hierarchy, and code to create a visual representation of the job in both the asset hierarchy and the project hierarchy. Having cis Tem. 40. The system of claim 39, further comprising code that allows a user to browse the asset hierarchy by visually observing the objects in the asset hierarchy at each hierarchy level. 41. The system of claim 39, further comprising code that allows a user to browse the project hierarchy by visually observing the objects in the project hierarchy at each hierarchy level. 42. The apparatus of claim 39, further comprising code that allows a user to visually navigate the asset hierarchy by navigating the asset hierarchy.
The described system. 43. The system of claim 41, further comprising code that allows a user to focus on a particular level of the object. 44. The system of claim 39, further comprising code that allows a user to visually navigate the project hierarchy by navigating the project hierarchy. 45. The system of claim 44, further comprising code that allows a user to focus on a particular level of the object. 46. The system of claim 39, further comprising code that allows a user to search the asset hierarchy to find a set of objects that satisfy user-defined criteria. 47. The system of claim 39, further comprising code that allows a user to search the project hierarchy to find objects that satisfy a particular set of user-defined criteria. 48. The system of claim 39, further comprising code for providing a shopping cart that allows a user to collect at least one file. 49. The system of claim 48, further comprising code that allows a user to perform operations on files collected in said shopping cart. 50. The system of claim 49, further comprising code that allows a user to route files collected in the shopping cart to another database. 51. The system of claim 39, further comprising code that allows a user to edit objects in the asset hierarchy. 52. The system of claim 39, further comprising code that allows a user to edit objects in the project hierarchy. 53. Creating a multi-level asset hierarchy having a plurality of objects including jobs and files, storing the asset hierarchy in system memory, a plurality of objects including the asset hierarchy jobs and events. Creating a multi-level project hierarchy having: storing the project hierarchy in the system memory; creating and providing a visual representation of the asset hierarchy and the objects in the project hierarchy; the asset hierarchy And editing the objects in the project hierarchy; and creating and providing a visual representation of the job in both the asset hierarchy and the project hierarchy. Method. 54. The method of claim 53, further comprising the step of allowing a user to visually observe the objects in the asset hierarchy at each hierarchy level. 55. The method of claim 53, further comprising allowing a user to visually observe the objects in the project hierarchy at each hierarchy level. 56. The method of claim 53, further comprising the step of allowing a user to visually observe the overview of the asset hierarchy. 57. The method of claim 56, further comprising allowing a user to focus on a particular level of the object. 58. The method of claim 53, further comprising allowing a user to visually observe the overview of the project hierarchy. 59. The method of claim 58, further comprising allowing a user to focus on a particular level of the object. 60. The method of claim 5, further comprising the step of allowing a user to search the asset hierarchy to find objects that satisfy a particular set of user-defined criteria.
3. The method according to 3. 61. The method further comprising allowing a user to search the project hierarchy to find objects that satisfy a particular group of user-defined criteria.
54. The method of claim 53. 62. The method of claim 53, further comprising providing a shopping cart that allows a user to collect at least one of the files. 63. The method of claim 62, further comprising allowing a user to perform operations on at least one of the files collected in the shopping cart. 64. The method of claim 62, further comprising the step of allowing a user to route files collected in the shopping cart to another database. 65. The method of claim 53, further comprising allowing a user to edit the object in the asset hierarchy. 66. The method of claim 53, further comprising allowing a user to edit the object in the project hierarchy. 67. A multi-level asset hierarchy stored in the system memory having a plurality of objects including jobs and files, and a multi-level project hierarchy stored in the system memory. And having a plurality of objects including the asset hierarchy job and events, program code for creating a visual representation of the objects in the asset hierarchy and the project hierarchy, and both the asset hierarchy and the project hierarchy. A program code for creating a visual representation of the job in the hierarchy. 68. The system of claim 67, further comprising code that allows a user to edit objects in the asset hierarchy and the project hierarchy. 69. The system of claim 67, further comprising code that allows a user to visually observe the objects in the asset hierarchy at each hierarchy level. 70. The system of claim 67, further comprising code that allows a user to visually observe the objects in the project hierarchy at each hierarchy level. 71. The system of claim 67, further comprising code that allows a user to visually view the asset hierarchy overview. 72. The system of claim 71, further comprising code that allows a user to focus on a particular level of the object. 73. The system of claim 67, further comprising code that allows a user to visually view the overview of the project hierarchy. 74. The system of claim 73, further comprising code that allows a user to focus on a particular level of the object. 75. The apparatus of claim 6, further comprising code that allows a user to find objects in an asset hierarchy that satisfy a particular group of user-defined criteria.
7. The system according to 7. 76. The system of claim 67, further comprising code that allows a user within the project hierarchy to find a particular set of objects that satisfy user-defined criteria. 77. The system of claim 67, further comprising a shopping cart that allows a user to collect at least one of said files. 78. The system of claim 77, further comprising code that allows a user to perform operations on the files collected in the shopping cart. 79. The system of claim 77, further comprising code that allows a user to route files collected in the shopping cart to another database. 80. The system of claim 67, further comprising code that allows a user to edit the object in the asset hierarchy. 81. The system of claim 67, further comprising code that allows a user to edit the object in the project hierarchy. 82. Storing a multi-level asset hierarchy having a plurality of objects including jobs and files in a system memory, the multi-level project hierarchy having a plurality of objects including jobs and events in the system. Storing in memory; creating and displaying a graphical representation of the object in the asset hierarchy and the project hierarchy; creating a graphical representation of the job in both the asset hierarchy and the project hierarchy. Displaying, a method for managing resources and projects. 83. The method of claim 82, further comprising editing the object in the asset hierarchy. 84. The method of claim 82, further comprising editing the object in the project hierarchy. 85. The method of claim 82, further comprising the step of allowing a user to visually observe a graphical representation of said objects in said asset hierarchy at each hierarchy level. 86. The method of claim 82, further comprising the step of allowing a user to visually observe a graphical representation of said objects in said project hierarchy at each hierarchy level. 87. The method of claim 82, further comprising the step of allowing a user to visually observe a schematic graphical representation of the asset hierarchy. 88. The method of claim 87, further comprising allowing a user to focus on a particular level of the object. 89. The method of claim 87, further comprising the step of allowing a user to visually observe a schematic graphical representation of the project hierarchy. 90. The method of claim 89, further comprising allowing a user to focus on a particular level of the object. 91. The method of claim 82, further comprising the step of allowing a user within the asset hierarchy to find a particular set of objects that satisfy user-defined criteria. 92. The method of claim 82, further comprising the step of allowing a user within the project hierarchy to find a particular set of objects that satisfy user-defined criteria. 93. The method of claim 82, further comprising providing a shopping cart that allows a user to collect at least one of said files. 94. The method of claim 93, further comprising allowing a user to perform operations on the files collected in the shopping cart. 95. The method of claim 94, further comprising the step of allowing a user to route files collected in the shopping cart to another database. 96. The method of claim 82, further comprising allowing a user to edit the object in the asset hierarchy. 97. The method of claim 82, further comprising allowing a user to edit said object in said project hierarchy.