EP1214666A2 - Methods and apparatus for catalog data capture, storage and distribution - Google Patents
Methods and apparatus for catalog data capture, storage and distributionInfo
- Publication number
- EP1214666A2 EP1214666A2 EP00958931A EP00958931A EP1214666A2 EP 1214666 A2 EP1214666 A2 EP 1214666A2 EP 00958931 A EP00958931 A EP 00958931A EP 00958931 A EP00958931 A EP 00958931A EP 1214666 A2 EP1214666 A2 EP 1214666A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- product
- data
- attribute
- recited
- customer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
Definitions
- the present invention relates to methods and apparatus for capturing, storing,
- the present invention relates to
- a reseller may simply advertise the availability of a particular computer at an advertised cost while another reseller or a distributor may provide specific details regarding the same computer such as the type
- manufactures will have a competitive advantage.
- the present invention enables product data to be captured, stored and distributed in an efficient manner. This is accomplished, in part, through the use of a product
- product data suitable for use in electronic catalogs is captured and stored for subsequent distribution to customers (e.g., manufacturers, distributors, resellers) as customers (e.g., manufacturers, distributors, resellers) as customers (e.g., manufacturers, distributors, resellers) as customers (e.g., manufacturers, distributors, resellers) as customers (e.g., manufacturers, distributors, resellers) as customers (e.g., manufacturers, distributors, resellers) as
- the data structure is based on a data model having one or more classes, where each of the classes has one or more associated categories.
- each class definition being arranged to identify
- the data structure includes a plurality
- each category definition being arranged to identify an
- the data structure further includes a plurality of attribute
- each attribute group definition is arranged to identify one or
- each attribute has an associated possible value list that identifies
- product data may be captured and stored according to the data model.
- detailed product information may be gathered and concentrated in one location for subsequent distribution.
- a customer product portfolio file is
- the customer product portfolio file may identify products for
- a method of capturing data includes classifying a
- the data may be made available on the
- the data may be packaged and distributed according to the needs of the customers requesting the data. For instance,
- enriched product data may be generated from the system product data file according
- the customer profile identifies at least one customer as well as customer searchable attribute preferences corresponding to each customer. For instance, the customer searchable attribute
- preferences may specify attributes (e.g., speed, size) for which values are to be transmitted. Once the values are transmitted to the customer, the values may be obtained via a search engine to enable an end-user to compare selected attributes
- the category “Desktop” may be selected along
- selected products e.g., printers
- selected attributes e.g., memory speed
- This data may include, for example, a marketing description, product
- identifies related (e.g., compatible) products may be compiled for distribution.
- related products e.g., compatible
- the customer may use the data in
- the data may be stored for use with a variety of marketing schemes.
- the data may be stored for use with a
- the data may be printed in a traditional catalog, or the data
- a customer i.e., retailer
- a customer i.e., retailer
- search engines may easily be customized according to the needs of the manufacturer, distributor, reseller, or consumer.
- browsing and searching for product data by an end-user is simplified. For instance, an end-user wishing to find products according to specific criteria such as price or processor speed may easily locate and
- the shopping experience is ultimately determined by the consumer. Accordingly, through the use of the present invention, the bargaining power maybe
- FIG. 1 is a diagram illustrating a system in which the present invention may be implemented.
- FIG. 2 is diagram illustrating exemplary classes that may be applied to classify
- FIG. 3-1 through FIG. 3-3 are diagrams illustrating exemplary categories that
- FIG. 4 is a diagram illustrating exemplary attribute groups that may be used to
- FIG. 5 is a diagram illustrating a hierarchical data model that may be used to
- FIG. 6 is a diagram illustrating an exemplary data structure that may be used
- FIG. 7 is a diagram illustrating an exemplary data structure that may be used
- FIG. 8A is a diagram illustrating exemplary data structures that may be used to
- FIG. 8B is a diagram illustrating exemplary data structures that may be used to
- FIG. 8C illustrates exemplary data structures that may be used to store attributes in the product data according to an embodiment of the invention.
- FIG. 9 A and 9B illustrate a specific implementation of the data model and the product data, respectively, using relational databases according to one embodiment of the invention.
- FIG. 9C is a diagram illustrating a specific implementation of the data model
- FIG. 9D is a diagram illustrating a specific implementation of the product data
- FIG. 10A is a flow diagram illustrating a method of catalog maintenance according to an embodiment of the invention.
- FIG. 10B is an exemplary product portfolio file received in step 1002 of FIG.
- FIG. 11 is a flow diagram illustrating a method of mapping customer data to
- system data as shown in step 1004 of FIG. 10A according to an embodiment of the invention.
- FIG. 12A is a flow diagram illustrating a method of capturing product data for
- FIG. 12B-1 through FIG. 12B-2 illustrate an exemplary product data research form that may be used to capture product data as shown in FIG. 12A according to an
- FIG. 13A-1 through FIG. 13A-2 illustrate a proof data sheet illustrating
- FIG. 13B is a component generator report illustrating exemplary component definitions for creating specified components according to an embodiment of the invention.
- FIG. 13C is a diagram illustrating an exemplary component format that may be used to create components according to an embodiment of the invention.
- FIG. 13D is a flow diagram illustrating a method of generating component data for missing products as shown in step 1008 of FIG. 10 A.
- FIG. 13E is a flow diagram illustrating a general method of generating a
- FIG. 14A is a flow diagram illustrating a method of generating enriched
- FIG. 14B is a diagram illustrating an exemplary customer searchable attribute
- FIG. 14 A is a diagrammatic representation of FIG. 14 A.
- FIG. 15A is a diagram illustrating an exemplary system for retrieving catalog
- FIG. 15B is a diagram illustrating an exemplary user query for retrieving
- FIG. 15C is a diagram illustrating a comparison of selected products according to an embodiment of the invention.
- An invention is described herein that enables catalog data to be captured, stored, and distributed in an efficient manner through the use of a data model.
- each product is initially
- the data model may be developed in a wide range
- One approach is to
- the data model may include a hierarchical data structure
- each class may be further divided into categories.
- the classes may include Input Devices, Output Devices, Data Storage
- Output Devices may include the categories
- the data model defines attributes for each of the classification categories.
- the attributes identify the type of data
- attributes may be specified for each category within the data model.
- the attributes associated with each category may be specified.
- product data may be captured using the data
- potential values may be associated with some or all
- the product data may be stored and
- the product data and associated information from the data model may be transmitted
- catalog data may be distributed in its entirety or in portions (e.g., components).
- the product data may be made available to end users through a catalog such as a traditional catalog or an online catalog.
- a catalog such as a traditional catalog or an online catalog.
- FIG. 1 is a diagram illustrating a system in which the present invention may be
- an end user 102 may connect to an HTTP server 104 via the Internet 106 to access a catalog database 108.
- capture tool 110 may be used to capture product data 112 according to a data model
- a hierarchical data model may be used to capture, store,
- the data model may be divided into one or more
- FIG. 2 is diagram illustrating exemplary
- classify a computer-related product include input devices 402, output devices 404,
- each class of the data model one or more categories may be defined.
- FIG. 3 is a diagram illustrating exemplary categories that may be applied to categorize
- each class 500 may be further defined by one or more categories 504.
- the class "Systems" 502 may include the categories desktop 504, laptop
- classes memory 504, storage 506, input 508, output 510, network 512, and software 514 are shown to include multiple categories. Those of
- Each category of the data model may be further divided into attribute groups.
- FIG. 4 is a diagram illustrating exemplary attribute groups that may be used to define a given category in a computer system according to an embodiment of the invention.
- each category 602 may include one or more attribute groups 604.
- each category 602 may include one or more attribute groups 604.
- each of these attribute groups 604 may include one or more attributes 606
- the category "Desktop" 608 is shown to include multiple attribute groups 604, each of which include a plurality of attributes
- the attribute group "System” 610 is shown to include
- attribute attributes "Type” 612 and “Designation” 614 are attributes "Type” 612 and "Designation” 614. As yet another example, attribute
- Processor 616 may include attributes such as “Upgradabihty” 618 and "Clock
- category may be defined by greater or fewer attributes as necessary to properly define the corresponding category.
- a multi-value indicator 622 may indicate whether multiple values may be captured for a single attribute. In other words, the multi-value indicator 622 may indicate that more than one of the values in an associated possible
- a value may be selected from the value list.
- an associated unit may
- a value may be selected
- attributes with which the product is available may be
- a data capture priority 626 may be assigned to each attribute
- attributes may be assigned to those attributes which are of secondary importance. Of course, any number of levels of importance may be utilized.
- the attributes may also be assigned to those attributes which are of secondary importance. Of course, any number of levels of importance may be utilized.
- the attributes may also be assigned to those attributes which are of secondary importance.
- searchable 624 optionally be designated as "searchable" 624 by a system designer or administrator.
- Searchable attributes are attributes that are potentially available to be electronically
- the searchable attributes may be assigned a priority of "1," as shown.
- the data model may include various
- FIG. 5 is a diagram illustrating a hierarchical data model including classes
- the data model 702 includes one or more classes 704. Each of
- the classes 704 may be defined by one or more categories 706. Each category 706
- the data model may be applied during the data capturing process.
- values and units may be captured and input for selected
- FIG. 6 is a diagram illustrating an exemplary data structure that may be used to store an attribute group in the hierarchical data model of
- FIG. 5 according to an embodiment of the invention. As shown, each attribute group
- attribute group identifier includes an attribute group identifier, or attribute group name 712.
- attribute group name 712 includes an attribute group identifier, or attribute group name 712.
- the attribute group 708 includes an attribute list 714 including one or more attributes.
- an attribute group 708 may further include a
- repeating indicator 716 (e.g., flag) which indicates that the attribute group is a
- repeating group in the data model when the repeating indicator 716 is in a
- the listing of potential values for the attribute group may be provided or displayed multiple times as a prompt for user input during the data capturing process.
- each attribute group includes an attribute list that identifies one or more attributes that are associated with the attribute group.
- FIG. 7 is a diagram illustrating an exemplary data structure that may be used to store an
- each attribute 710 is identified by an attribute name 718 and is associated with a possible value list 720 that identifies values that are selectable as
- each attribute 710 may be associated
- attribute name 718 is associated with an attribute
- the possible value list 720 is associated with a value
- each of the attributes is
- language dependent indicator 730 is in a predefined state. Each attribute is further
- a data capture priority indicator 734 assigns priorities to at least some of the attributes in order that these attributes are
- a system administrator may indicate that
- searchable indicator 736 attributes designated as searchable may be prioritized during data capture.
- specific values may be selected from the possible value list for each of the selected searchable attributes.
- an attribute may be separately
- each attribute may be designated as comparable through
- the user may select products within a category which are to be compared.
- the product data may be obtained from the
- the product data may be stored in one or more databases which may
- attributes for use in a product catalog includes one or more attributes. These attributes may
- each attribute has one or more values as well as associated units. Moreover, each attribute
- ⁇ may have one or more associated indicators (e.g., comparable indicator).
- associated indicators e.g., comparable indicator.
- identifying data is associated with the captured data. As shown in FIG. 8A, such identifying information is stored in a product header
- the product header 802 is 802 according to one embodiment of the invention. As shown, the product header 802
- SKU system stock keeping unit
- the product information may include a
- category identifier 808 arranged to identify the category associated with the product.
- the product information may further include a manufacturer product
- description 810 that describes standard features of the product. Furthermore, additional data associated with the product may be linked to the
- the product header may include a link to an image 812 as well as to a
- the marketing description 814 may
- an image table 816 may include a link to one or more images
- each image 818 may be associated with an image ID 820.
- the product header 802 may include the appropriate image IDs 820 which may be used to access the corresponding images as defined in the image table
- a marketing table 822 may include a link to a marketing
- each marketing description 824 may
- the product header 802 may therefore
- FIG. 8B is a diagram illustrating exemplary data structures that may be used to
- a languages table 828 may indicate each language in which the product and
- one or more languages may be associated with a language ID 830.
- one or more languages may be associated with a language ID 830.
- one or more languages may be associated with a language ID 830.
- the information provided in the languages table 828 may be captured as standard attributes.
- a device may be designed for use with a specific voltage. To store such
- a country table, or country kits table 834 may specify each country for
- each country may be associated
- country ID 836 a country ID 836.
- one or more countries may be linked to the system SKU 832 associated with the product and corresponding product header.
- table 834 may be captured as standard attributes.
- a related products table 838 may list one or more related
- product may be associated with a system SKU assigned to the related product 840.
- the platform of the product is
- a product compatibility table 842 may include platform compatibility information associated with the product.
- compatibility information may include each platform compatible with the product.
- a computer product may be compatible with at least one of a
- each platform may be associated with a
- the appropriate platforms may be associated with the system SKU 832 for the product and product header. Alternatively, rather than
- the platform compatibility information may be captured as standard attributes during the capture process.
- the attributes may be
- FIG. 8C illustrates exemplary data structures that may be used to store attributes in the product data according to an embodiment of the invention.
- each attribute in the data model may have an associated possible
- the selected attributes may be stored in an attribute table 846. As shown, each of the selected attributes may be
- each attribute identified by a system SKU 848 and an attribute ID 850.
- each attribute is identified by a system SKU 848 and an attribute ID 850.
- each attribute is identified by a system SKU 848 and an attribute ID 850.
- stored in the attribute table 846 may have at least one of the values in the associated
- Each value may be associated with a value ID 852.
- the attribute may be further associated with a unit in the associated possible unit list. This unit may similarly be associated with a unit ID 854. However, not all attributes will have
- the attribute table may store an attribute which has a single value as
- an attribute table may contain
- repeating attribute table 856 may distinguish
- instance of an attribute may be distinguished by the corresponding system SKU 848, attribute ID 850, and set number 858. In this manner, values and units may be stored for each instance of an attribute.
- the data model and the product data may be implemented and linked in a variety of manners.
- FIG. 9 A and 9B illustrate a specific implementation of the data
- the data model 902 is shown in FIG. 9A while the product data 904 is
- FIGS. 9 A and 9B illustrate both the product
- the product data 904 may be stored in a database separate from the data model 902. To simplify the following discussion, the product data 904 is described as being stored in a system
- product data file The data may be stored in fields which may be stored and linked
- the data model includes a plurality of data structures
- the data model may include
- Each class in the data model may
- each class may be identified by a class
- Identifiers such as the class identifier 908 may be an alphanumeric
- Each class in the class table may be linked.
- Each class may include one or more categories, as described above with
- These categories may be stored in a category table 912 and linked to the corresponding class through the use of the corresponding class identifier
- Each category may be identified by a category identifier 916 and a
- each attribute group includes one or more attributes having
- group identifier 922 may be joined to create a unique joining identifier, category-
- attribute group identifier 924 In this manner, attributes and associated value lists
- the attribute "size" may be relevant in
- a category-attribute mapping table 926 may be created.
- the table includes a unique joining identifier, category-attribute identifier 928, which may be created by joining an attribute identifier 930 corresponding to the
- attribute identifier 928 may therefore be used to access each attribute (and
- each attribute associated with the category-attribute mapping table 926 is associated with the category-attribute mapping table 926.
- a data capture priority indicator 932 that assigns a
- the data capture priority to the attribute for data capture.
- the data capture priority is priority to the attribute for data capture.
- indicator 932 may designate an integer priority level to the corresponding attribute.
- a capture order may be assigned to the attributes within a particular category.
- the priority level may be an integer unique to the attribute within the particular category.
- the priority level may be used to create prioritized sets of attributes, each attribute within a set having the same priority level.
- each attribute within the category-attribute mapping table 926 may be designated as searchable 934 within the corresponding category.
- designation of an attribute as searchable may indicate that capture of the attribute is
- the attribute should also have a high priority level.
- an attribute may be specified as comparable 936 through an
- the comparable attribute may then be provided for selection
- Each attribute may have an associated value as well as a unit.
- a default unit may be provided for the corresponding unit.
- a default unit may be provided for the corresponding unit.
- a default unit for the attribute "Clock Speed" a default unit
- the default unit may be specified by a default unit identifier 938.
- attribute mapping table 926 may further include the corresponding attribute group
- each attribute may have one or more values.
- each attribute may have one or more values.
- each attribute may have an associated possible value list 940 identifying values that are selectable as values for the attribute.
- possible value list 940 is identified by a value list identifier 942 and a value list name
- an attribute may be language dependent. Therefore, a
- value list 940 it may also be associated with the entire attribute as well as associated
- Memory / Cache will have an alphanumeric value list (e.g., DRAM, ROM).
- each of the attribute values may have an associated unit.
- each attribute may have an associated possible unit list 950 containing units that are
- the possible unit list 950 may be identified by a
- unit list identifier 952 and a unit list name 954. As previously indicated, the unit list
- identifier 952 may be an alphanumeric value used in a relational database system.
- the attributes within the data model may be stored in an attribute table 956.
- each attribute stored in the attribute table 956 includes the corresponding
- associated attribute group may be provided for display purposes.
- associated attribute group may be provided for display purposes.
- the position 958 may indicate the order in which the attribute is printed or displayed.
- an attribute name 960 (e.g., upgradabihty) associated with the attribute may be provided to identify the attribute for which values are being captured.
- data entry personnel may correctly identify the attribute for which data is to be captured.
- the attributes may
- each attribute group it may be more informative and therefore preferable to provide a specific one of the attributes first to
- a leading indicator 962 may specify which
- attribute is leading within a particular attribute group.
- the leading attribute is the first attribute output (e.g.,
- each attribute is associated with its attribute group
- a multi-value indicator 964 may indicate
- a product may be available with a cache size of 1 GB as well as 2
- the associated unit list 950 e.g., MB, GB.
- Each attribute may have an associated attribute "type” 966.
- the attribute type 966 may be defined by the attribute group identifier 922 associated with the attribute, an attribute group name 968 associated with the attribute
- attribute groups for output purposes.
- an attribute group may be output according to the specified position of the attribute group 970.
- a repeating indicator 972 is used to specify whether the attribute group is repeating.
- a repeating indicator 972 is used to specify whether the attribute group is repeating.
- product for which data is being captured may be classified in a category according to
- the attributes in the category of the classified product may be provided for selection.
- the repeating indicator 972 indicates that the attribute group associated with the classified product is a repeating group in the data model, the listing of potential values
- Value lists and unit lists associated with each attribute may be separately
- the list 940 is associated with the value list identifier 942.
- the value has a
- the unit list identifier 952 in the possible unit list 940 is associated with the unit list identifier 952 as well as a
- the unit identifier 978 may be an
- unit name 979 indicates a unit which may be selected in association with the attribute.
- possible unit names include “KB” and “MB.”
- the captured data may be transmitted to the customer.
- Each customer may specify one or more languages in which the customer wishes to receive the captured data. This is particularly important
- table 980 containing translations for each class, category, attribute group, attribute,
- translation table 980 may be identified by a translation identifier 981.
- a translation identifier 981 may be identified by a translation table 980.
- a translation identifier 981 may be identified by a translation table 980.
- reference identifier 982 may indicate which class, category, attribute group, attribute,
- the reference identifier 982 may specify an attribute identifier.
- the attribute identifier may specify
- a language identifier 984 may
- language identifier 984 may be combined such that the translation identifier 981 is unique for the attribute and language in which the attribute is translated. Accordingly,
- a corresponding translation 985 may be retrieved through the use of this translation
- product data may be communicated in various languages. In order to
- languages table 986 indicates one or more languages in which the attributes may be
- product data may be provided upon transmission to the customer, and in which the product and associated
- Each language is associated with the corresponding language identifier 984 and a language name 988 (e.g., German).
- Each country is identified by a country identifier 992 and a country name 993.
- a possible compatibility table 995 may
- Each entry may be identified by a compatibility identifier 996 (e.g., integer) and a platform name 997 (e.g., PC).
- a compatibility identifier 996 e.g., integer
- a platform name 997 e.g., PC
- captured catalog data may be formatted prior to distribution to a customer or end user.
- Such distribution may be performed through various mechanisms including, but not
- the catalog data may be distributed in formatted portions, or "components.” More particularly, each customer may request that various portions or
- components of the catalog data be transmitted to the customer for selected products.
- an end user may wish to submit a catalog query for data associated with a
- a component generator 998 may be used to generate such components. Since the content and format of these components may further depend upon the category within which the
- the component generator 998 supplies different
- identifier 916 to determine the type of components and format of each component to be generated. In addition, each component that may be generated in association with
- the product data may be captured
- FIG. 9B illustrates a specific implementation of a database that
- a product header 1902 For each product, a product header 1902 is created which identifies the product.
- a product identifier 1904 e.g., system SKU
- a manufacturer identifier 1906 that identifies a manufacturer
- header 1902 to correctly identify the product manufactured by that specific
- the manufacturer product description 1910 is a product
- each product may be further associated with more detailed identifying information.
- a product line identifier 1912 that identifies a particular product line (e.g., Compaq Presario) of the product as well as a model line
- identifier 1914 that identifies a particular model line (e.g., 4500) associated with the product may be provided. Such product information may be linked to a particular model line (e.g., 4500) associated with the product.
- the product header 1902 associated with a particular product may
- the product header 1902 may be linked to one or more associated images
- the product header 1902 may be linked to a marketing
- the status 1922 may indicate that data capture for the product has been completed.
- the product information may be used by the component
- manufacturer table 1923 includes information associated with each possible
- Each manufacturer is identified by the manufacturer identifier 1906
- an image appropriate for use in a catalog may be associated with a particular manufacturer.
- each product line may be stored in a product lines table 1926.
- each product line may be stored in a product lines table 1926.
- each product line may be stored in a product lines table 1926.
- each product line may be
- the product line identifier 1912 e.g., alphanumeric value
- the attribute group identifier 922 associated with the product line e.g., the manufacturer identifier 1906
- a models table 1930 is provided to store the model information for each product
- model identifier 1914 For each possible model, the model identifier 1914
- identifier 1912 may be stored. In this manner, data associated with each product line
- each of the products may be stored in an images table 1934.
- each images table 1934 In this images table 1934, each of the products, may be stored in an images table 1934.
- image may be identified by its image identifier 1916 (e.g., alphanumeric value) as
- a manufacturer identifier 1906 may be associated with a manufacturer identifier 1906 as well as a product line
- a country kits table 1938 may
- an entry may include the product identifier 1904 associated with the product as well as the country identifier 992 that identifies a specific country for which the product is adapted for sale.
- each entry in the locales table 1940 specifies the product identifier 1904 that identifies the product and a language identifier 984 in which the
- product may have multiple associated entries in the locales table 1940.
- a product compatibility table 1942 indicates one or more platforms
- the platform may
- the table may include multiple
- products are specifically manufactured for use with a specific family
- a related products table 1943 identifies products that are related to
- table 1943 therefore includes the product identifier 1904 (e.g., system SKU) associated with the product as well as a related product identifier 1944 (e.g., system SKU)
- product identifier 1904 e.g., system SKU
- product identifier 1944 e.g., system SKU
- SKU SKU that identifies a product that is related to the product.
- SKU SKU
- manufacturer may recommend various products such as printers as compatible or related to a desktop computer for which data is being captured.
- various products such as printers as compatible or related to a desktop computer for which data is being captured.
- products table 1943 may include multiple entries in association with a single product.
- a marketing description table 1949 stores marketing descriptions
- the marketing identifier 1920 (e.g., integer) identifying the marketing identifier 1920
- a customer profile may include one or
- customer mapping tables 1945 that identify each customer as well as information associated with each customer.
- the tables 1945 may identify
- each customer a language in which the catalog data is to be transmitted to the customer, one or more components which are to be transmitted to the customer, and
- customer searchable attribute preferences which identify attributes which are to be supplied to the customer.
- a customer product map 1945 identifies each product for which a particular customer wishes data to be supplied. Each product is identified by the
- customer to the product and a customer identifier 1948 that identifies the customer.
- the customer mapping table 1945 maps the product identifier 1904 (e.g., system SKU) to the customer SKU 1946 assigned to the product by a particular
- the customer SKU 1946 may be unique to a particular customer.
- the customer SKU 1946 may be the manufacturer SKU assigned to the
- Each customer may be further identified in a customer table 1950.
- a customer may be identified by the customer identifier 1948, a
- each customer may speak different languages. As a result, each customer may
- a customer language table 1960 specifies one or more languages in
- an entry is identified by the customer identifier 1948 for a particular customer as well as the language
- identifier 984 identifying a language selected by the customer.
- a customer may wish to specify various catalog components which are to be transmitted to the customer in a format suitable for use in a catalog. Component generation will be described in further detail with reference to FIGS.
- a component may include various types of catalog data, such as a URL, an image, a marketing description, or technical specifications (i.e., extended
- a customer component table 1962 identifies those components that are requested by the customer.
- a customer-component identifier 1964 may be
- component identifier 1966 identifying one of the possible components which may be generated. In this manner, the customer may specify only that data which is desired
- the customer may tailor the data capturing process
- a customer may further specifying languages and components.
- searchable attributes which are to be supplied
- each such attribute is uniquely identified by a customer
- the customer attribute preference identifier 1970 The customer attribute preference identifier 1970
- customer product map 1945 Since some or all of the requested attribute data may have been previously captured, data for one or more of the identified products is captured as necessary. Once these attributes are captured, the captured attribute
- values may be stored in one or more product attribute tables. According to the embodiment shown, separate attribute tables may be provided for those attributes
- a product attribute table 1972 stores each captured attribute having a single value. Each attribute is identified by a unique product attribute identifier 1974 which may be created by joining the product identifier 1904 with the attribute identifier 930.
- the product attribute identifier 1974 identifies the attribute captured for the
- a unit identifier 978 identifying a unit in the
- the corresponding possible unit list may be provided in association with a captured value.
- the value identifier 974 identifies a value in the corresponding possible
- a separate attribute table stores attributes
- This table may be identical to the product attribute table 1972.
- the separate attribute table 1980 storing attributes having multiple captured values is implemented
- a product repeating attribute table 1982 stores values and units for
- a product repeating attribute group identifier 1984 may be created by joining the product identifier 1904, the attribute group identifier 922, a set number 1986, and the attribute identifier 930 to identify a specific instance (e.g., captured value and unit) of the captured attribute.
- a specific instance e.g., captured value and unit
- a product attribute group identifier 1988 may be created by joining the product identifier 1904 and the attribute group identifier 922.
- group identifier 1988 identifies the attribute group (e.g., processor) captured for a
- the captured attribute identifies the attribute (e.g., clock speed) captured for the specific
- the unit identifier 978 and the value identifier 974 are stored.
- FIG. 9A may be stored as shown. Each component is identified by the
- each component may include a section header 1991, a line header 1992,
- the components may then be transmitted to the customer on a regular basis or
- FIG. 9C is a diagram illustrating a specific implementation of the data model
- a countries table 990 and a compatibility table 995 are provided.
- FIG. 9D is a diagram illustrating a specific implementation of the product data
- each image is identified by its image identifier 1916 (e.g., alphanumeric value) as well as an image
- each image is associated with a manufacturer identifier 1906 as well as a product
- each image is further associated with a category identifier 916 and a model identifier 1914.
- each product line is associated with the
- the product header 1902 associated with a particular product may
- This data may vary from
- a URL 1918 may be associated with a particular product.
- a URL 1918 may be associated with a particular product.
- a URL associated with the product need not be specified in the product header.
- the product data Prior to transmission to each customer, the product data may be updated or
- FIG. 10A is a flow
- the process begins at step 1000 and a customer product portfolio file is received at step 1002 from a customer.
- the customer product portfolio file may
- the customer product portfolio file is then mapped to the system product
- missing products may be captured and added to the system product data file at step
- the data may be compiled and formatted in a manner suitable for use in a catalog.
- component data formatted for use in an electronic catalog may be generated for the missing products at step 1008.
- the component data may
- a customer may wish to receive product data in the form of portions or
- components By way of example, the customer may be interested in receiving
- the customer may limit the product data it receives.
- the customer may limit the product data it receives.
- this enriched product data may be generated from the system product data file according
- data may then be transmitted at step 1012.
- the process ends at step 1014.
- data may be generated for use by a particular customer according to that customer's preferences 1010 simultaneously with the capture of data 1006 and generation of component data 1008. This is particularly important since the data
- capturing process may be a time-consuming one since it may be performed, at least in part, by a manual process. As a result, capturing, storing, and distribution of data is
- a customer product portfolio file may specify products for
- FIG. 10B is an exemplary product portfolio file received in step 1002 of FIG. 10A according to an
- the customer product portfolio file may
- FIG. 11 is a
- step 1004 of FIG. 10A the process begins at step 1100 and at step 1102, a manufacturer identified in the customer
- product portfolio file is mapped to a system manufacturer file or table.
- the system manufacturer file may be included in the system product data file. It is then ascertained whether the manufacturer is new at step 1104. In other words, if the manufacturer is not identified in the system product data file, the manufacturer is a new manufacturer. If it is determined at step 1104 that the manufacturer is new, a
- manufacturer identifier is assigned to the new manufacturer and the manufacturer
- the record containing the new manufacturer may be flagged as new. If it is determined that there is
- SKU identified in the customer product portfolio file is mapped to a system SKU.
- this may be performed through the use of the manufacturer identifier
- customer SKU is new.
- the customer SKU is not identified in the system product data file, the customer SKU requires a new system SKU. If the
- a new system SKU is created at step 1114 such that the new
- system SKU is mapped in the system product data file to the customer SKU.
- the new system SKU is created, a new system SKU is assigned to the new record and
- the record may be flagged as new. If it is determined that there are more customer SKUs in the customer product portfolio file at step 1116, the process is repeated at step 1116.
- the system SKU may be classified according to the data model at step 1118.
- the new system may be classified according to the data model at step 1118.
- SKUs may be classified during one step as shown. Alternatively, each new system SKU may be classified separately during the mapping process.
- a customer SKU is unrecognizable when the corresponding
- FIG. 12A is a flow diagram illustrating a method of
- the process begins at step 1200.
- the product data may be captured according to a manual process as well as an automated
- Product data research forms may be
- a product data research form may then be
- the product may be researched and appropriate attribute values may be selected and marked on the product data research form. Data from the
- step 1210 In addition to inputting information associated with one or more attributes for the missing product, further product information may be input to the system product data file as shown in steps 1210 through 1216.
- step 1210 one
- images illustrating the product may be input to the system product data file, in addition to an expanded marketing description for the new system SKU.
- localization information may be input to the system product data file.
- one or more languages in which the product and documentation associated with the product are available may be specified.
- one or more languages in which the product and documentation associated with the product are available may be specified.
- one or more countries for which the product is adapted for sale may be input to the
- platform compatibility information may be
- the platform compatibility information may indicate that the product is compatible with a Macintosh or a PC.
- the manufacturer may recommend one or more products as
- a quality check may be performed on the inputted information at step 1218.
- inputted data may be checked against completed
- the status flag for the new system SKU may
- step 1220 If it is determined that there are more forms at step 1220,
- the data entry template maybe a product data research form that includes a listing of potential values associated with each of the attributes in the category of the classified product.
- the data entry template may be provided via an automated computer
- FIG. 12B illustrates an exemplary product data research form that may be used to capture product data as shown in FIG. 12A according to an embodiment of the
- a product data research form may be
- the form header 1226 may include a manufacturer identifier 1228, a
- manufacturer SKU 1230 a product line 1232, a model number 1234, a manufacturer
- product description 1236 a system SKU 1238, and a category identifier 1240.
- the attribute group name 1254 (e.g., Processor)
- attribute name 1256 e.g., Form Factor
- an attribute indicator 1260 is associated with an associated possible value list 1258.
- an attribute indicator 1260 is associated with an associated possible value list 1258.
- the data may be compiled in a format suitable
- FIG. 13A is a proof data sheet illustrating exemplary components that may be generated for use in a catalog according to an embodiment of the invention. As shown, the proof data sheet may indicate a language 1300 in which the
- a manufacturer identifier 1302 a manufacturer SKU 1304, a quantity
- the product may be packaged (e.g., in multiples of 5, 10, 100, etc.), and a system SKU 1308.
- Various components may be generated for use in a catalog.
- the proof data sheet may be any suitable technical specifications (i.e., extended specifications) 1316.
- the proof data sheet may be any suitable technical specifications (i.e., extended specifications) 1316.
- the component For each component that may be generated for use in a catalog, the component may have a format specified according to a component definition. Moreover, each
- component definition may be defined in association with one or more categories.
- FIG. 13B is a component generator report illustrating exemplary component
- Each component definition may be defined. Each component definition may further include a section header
- Each line body definition 1326 includes rules defining
- the contents of the line body are obtained according to
- the component displayed in the line body (e.g., "x").
- the component displayed in the line body (e.g., "x").
- the line header may identify an attribute group associated with the product and corresponding category.
- each component definition may be used to create a component having the contents and format specified by the component definition.
- FIG. 13C is a
- a component 1328 may include a section header 1330, at least one line header 1332, and a line
- FIG. 13D The process begins at step 1336 and at step 1338, it is
- specifications may be generated for the missing product at step 1344.
- extended technical specifications may be generated for the missing product
- FIG. 13E is a flow diagram illustrating a general method of
- a component definition may be obtained for the product category. For each item identified in the component definition, information
- a sample of the product data and the data model may be extracted from the product data and the data model at step 1354.
- component descriptor e.g., technical/extended specifications
- component definition e.g., literals provided in the component definition
- component descriptor may be provided in response to a catalog query.
- the process completes at step 1360.
- a customer may request that enriched product data be provided to the
- FIG. 14A is a flow diagram
- FIG. 10A according to an embodiment of the invention. As will be described, this
- enriched product data may be generated from the system product data file according to a customer profile.
- the customer profile may identify at least one customer and
- customer searchable attribute preferences may specify attributes
- system records may be set to "released.” Thus, system records for customer SKUs
- a system record associated with a customer is obtained from the system product data file (e.g., one of the released system records) for processing.
- a system product data file e.g., one of the released system records
- product header is created from the system record. This product header is different
- the product header will be associated with data that is to be exported to the customer.
- the product header may include a customer SKU associated with the system
- the product header may include a system SKU that identifies a
- the product header may then be exported to
- attributes associated with the system record may be exported
- the attributes that are exported may include, but are not limited to, an attribute ID
- computer product may include 1500MB, 3GB, 600MB, and 7KB. Although the value is not limited
- value-unit combinations are normalized to permit values to be compared by an end- user.
- Normalizing numeric value-unit combinations may be performed prior to data capture or upon completion of data capture. Thus, each value in the possible value
- each attribute value and associated unit may be assigned a value such that the smallest
- lists of related products may be transmitted to the customer.
- a list of related products associated with the system record may
- the list of related products may be those products recommended by the manufacturer.
- Related product information may include the customer SKU associated with the system record as well as a customer SKU for each
- the customer SKU associated with the system record may be obtained from the product header. If it is determined at step
- the customer may receive product data in one or more
- a vocabulary file may be generated and exported based upon the exported
- the vocabulary file preferably includes translations for each language dependent attribute.
- attribute may be language dependent (e.g., unit).
- the customer may wish to receive a list of those attributes it is receiving.
- searchable attribute preferences may be exported to identify the attributes that the
- step 1418 customer is receiving at step 1418.
- the process is completed at step 1420. In this
- a customer may indicate specific attributes for which the
- FIG. 14B is a diagram illustrating an
- exemplary customer searchable attribute preferences file that may be used in generating enriched product data as shown in FIG. 14 A. As shown, the customer
- profile includes a customer searchable attribute preferences file 1422 which identifies
- Each attribute may be identified by an attribute ID 1426 and the associated category may be identified by a category ID 1428.
- FIG. 15A is a diagram illustrating an exemplary system for retrieving catalog data according to an embodiment of the invention. As shown, an end user 1502 may
- the web site 1504 provides a query form 1510 which permits a user to
- catalog file such as the system product data file or customer catalog file.
- query supplied by the query form 1510 may be sent to the system data base server
- system database 1512 retrieves the requested information (e.g., component) from the system database 1514 (e.g., system product data file).
- the requested information may then be obtained from the system database 1514 (e.g., system product data file).
- FIG. 15B is a
- the user query 1518 may include a customer SKU 1520 associated with a product, a language selection 1522 in which
- the component may include a
- numeric values may be
- an end user may wish to compare multiple products.
- the user query may permit a user to compare selected products within an identical category 1526 according to selected comparable attributes.
- a selection of at least one of the set of attributes 1528 corresponding to the category 1526 may be obtained from a user.
- the selected attributes e.g., attribute
- the selected comparable attributes 1532 for the selected products 1530 may then be obtained for the selected products 1530 from the catalog database (e.g., system product data file or customer database) and displayed.
- the catalog database e.g., system product data file or customer database
- products 1530 may be provided to permit a side-by-side comparison as shown.
- the invention can also be embodied as computer readable code on a computer
- the computer readable medium is any data storage device that can store data which can thereafter be read by a computer system. Examples of the
- computer readable medium include read-only memory, random-access memory, CD-
- ROMs read only memory
- magnetic tape magnetic tape
- optical data storage devices optical data storage devices
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP10012802A EP2333680A1 (en) | 1999-09-02 | 2000-08-30 | Methods and apparatus for catalog data capture, storage and distribution |
Applications Claiming Priority (11)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US626090 | 1984-06-29 | ||
US15251099P | 1999-09-02 | 1999-09-02 | |
US152510P | 1999-09-02 | ||
US62634700A | 2000-07-26 | 2000-07-26 | |
US09/626,090 US7197479B1 (en) | 1999-09-02 | 2000-07-26 | Methods and apparatus for implementing a multi-lingual catalog system |
US625913 | 2000-07-26 | ||
US625745 | 2000-07-26 | ||
US09/625,913 US7949691B1 (en) | 1999-09-02 | 2000-07-26 | Methods of catalog data maintenance, storage, and distribution |
US09/625,745 US7284007B1 (en) | 1999-09-02 | 2000-07-26 | Methods of capturing catalog data |
US626347 | 2000-07-26 | ||
PCT/IB2000/001329 WO2001016796A2 (en) | 1999-09-02 | 2000-08-30 | Methods and apparatus for catalog data capture, storage, and distribution |
Publications (1)
Publication Number | Publication Date |
---|---|
EP1214666A2 true EP1214666A2 (en) | 2002-06-19 |
Family
ID=27538424
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP00958931A Withdrawn EP1214666A2 (en) | 1999-09-02 | 2000-08-30 | Methods and apparatus for catalog data capture, storage and distribution |
EP10012802A Withdrawn EP2333680A1 (en) | 1999-09-02 | 2000-08-30 | Methods and apparatus for catalog data capture, storage and distribution |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP10012802A Withdrawn EP2333680A1 (en) | 1999-09-02 | 2000-08-30 | Methods and apparatus for catalog data capture, storage and distribution |
Country Status (3)
Country | Link |
---|---|
EP (2) | EP1214666A2 (en) |
AU (1) | AU7033700A (en) |
WO (1) | WO2001016796A2 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6871198B2 (en) | 2001-12-21 | 2005-03-22 | Requisite Technology, Inc. | Composing and cataloging item configuration data |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5675784A (en) * | 1995-05-31 | 1997-10-07 | International Business Machnes Corporation | Data structure for a relational database system for collecting component and specification level data related to products |
US5745765A (en) * | 1995-10-23 | 1998-04-28 | Calico Technology, Inc. | Method and apparatus for automatic and interactive configuration of custom products |
US5890175A (en) * | 1996-09-25 | 1999-03-30 | Wong; Garland | Dynamic generation and display of catalogs |
-
2000
- 2000-08-30 WO PCT/IB2000/001329 patent/WO2001016796A2/en active Application Filing
- 2000-08-30 EP EP00958931A patent/EP1214666A2/en not_active Withdrawn
- 2000-08-30 EP EP10012802A patent/EP2333680A1/en not_active Withdrawn
- 2000-08-30 AU AU70337/00A patent/AU7033700A/en not_active Abandoned
Non-Patent Citations (1)
Title |
---|
See references of WO0116796A3 * |
Also Published As
Publication number | Publication date |
---|---|
WO2001016796A2 (en) | 2001-03-08 |
AU7033700A (en) | 2001-03-26 |
WO2001016796A3 (en) | 2002-04-18 |
EP2333680A1 (en) | 2011-06-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8738662B2 (en) | Methods and apparatus for catalog data capture, storage and distribution | |
US7197479B1 (en) | Methods and apparatus for implementing a multi-lingual catalog system | |
US7284007B1 (en) | Methods of capturing catalog data | |
US7542978B2 (en) | Auction notification system | |
US20180285883A1 (en) | Providing Market Feedback Associated with Electronic Commerce Transactions to Sellers | |
US7480628B2 (en) | Smart multi-search method and system | |
US6983276B2 (en) | Facilitating electronic commerce transactions using buyer profiles | |
US7076463B1 (en) | System and method for providing decentralized E-commerce | |
US7127416B1 (en) | Distributed processing of sorted search results in an electronic commerce system and method | |
US8402068B2 (en) | System and method for collecting, associating, normalizing and presenting product and vendor information on a distributed network | |
US7650334B2 (en) | Content enhancement for analyzing data in a database | |
US6038668A (en) | System, method, and medium for retrieving, organizing, and utilizing networked data | |
US7349868B2 (en) | Pre-qualifying sellers during the matching phase of an electronic commerce transaction | |
US20050065996A1 (en) | Client-server multitasking | |
US8244736B2 (en) | Electronic brokerage system and methods of performing the same | |
US20070078850A1 (en) | Commerical web data extraction system | |
AU2001241718A1 (en) | Client-server multitasking | |
US20070239666A1 (en) | Method and System for a De-Normalized Electronic-Catalog | |
KR20200139561A (en) | Product information processing apparatus for multiple online shopping maill product registration and method thereof | |
WO2006065546A2 (en) | Method, system and graphical user interface for providing reviews for a product | |
US7475030B1 (en) | Facilitating electronic commerce transactions using a shared product data repository | |
US7412424B1 (en) | Third party certification of content in electronic commerce transactions | |
US20020082959A1 (en) | Method, apparatus and article for tracking replacement part information | |
EP2333680A1 (en) | Methods and apparatus for catalog data capture, storage and distribution | |
WO2001001291A1 (en) | System for providing information to intending consumers |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20020402 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE |
|
AX | Request for extension of the european patent |
Free format text: AL PAYMENT 20020402;LT PAYMENT 20020402;LV PAYMENT 20020402;MK PAYMENT 20020402;RO PAYMENT 20020402;SI PAYMENT 20020402 |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: KVIATKEVITCH, ALEXANDRE IGOREVITCH Inventor name: ZABRODINE, CONSTANTIN NICKOLAYVICH Inventor name: DE HEER, RUDOLF, CORNELIUS, WILHELMUS Inventor name: BLAETTLER, ERIC, OSCAR Inventor name: DE HEER, ALBERT, HENRICUS, FRANCISCUS |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: 7G 06F 17/30 A Ipc: 7G 06F 17/60 B |
|
17Q | First examination report despatched |
Effective date: 20080104 |
|
APBK | Appeal reference recorded |
Free format text: ORIGINAL CODE: EPIDOSNREFNE |
|
APBN | Date of receipt of notice of appeal recorded |
Free format text: ORIGINAL CODE: EPIDOSNNOA2E |
|
APBR | Date of receipt of statement of grounds of appeal recorded |
Free format text: ORIGINAL CODE: EPIDOSNNOA3E |
|
APAF | Appeal reference modified |
Free format text: ORIGINAL CODE: EPIDOSCREFNE |
|
APAF | Appeal reference modified |
Free format text: ORIGINAL CODE: EPIDOSCREFNE |
|
APBT | Appeal procedure closed |
Free format text: ORIGINAL CODE: EPIDOSNNOA9E |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20150303 |