Versata Development Group, Inc.

Trilogy Development Group, Inc.

Other

Jeremy Weinrib

Scott Bonneau

Michael Nonemacher

An arbitrary number of custom catalogs for an arbitrary number of customers can be published from a single database of seller catalog data. Custom browse hierarchies can be generated for each of the custom catalogs. The custom catalogs are subsets of the catalog database, and are generated in accordance with a set of rules that defines the scope of the content of the custom catalog. The rule sets define a series of sequential searches by which a subset of the product SKUs contained in the database are returned. A primary hierarchy is maintained that can have a scope coextensive with the primary database. Custom browse hierarchies can be pruned to render their scope approximately coextensive with each subset. The custom catalog subsets and the custom browse hierarchies are generated periodically through a virtual publication process.

Browse hierarchies customized for rules based custom catalogs

Custom browse hierarchies for subsets of items in a primary hierarchy

An arbitrary number of custom catalogs for an arbitrary number of customers can be published from a centrally maintained database of seller catalog data. The custom catalogs are subsets of the catalog database, and are generated in accordance with a set of rules that defines the scope of the content of the custom catalog. The rule sets define a series of sequential searches by which a subset of the item SKUs contained in the database are returned. For extranet buyers, the subsets for each rule set are maintained in a subset table. Whenever a user authorized by a particular buyer wishes to browse the unique catalog subset assigned to that buyer, any queries regarding the catalog will result first in a search of the full catalog database, and the results from the full search are pared down to only those items the SKUs for which have entries in the subset table associated with the buyer's assigned subset. A buyer-authorized user browses the catalog using a standard PC and browser, and SKUs returned to the user based on the user's query will include descriptive information such as descriptive text, pictures etc., which are displayed by the browser. Buyers who are not coupled to the seller via an extranet connection can have customized subsets of the total catalog database produced in accordance with their own rule sets, and formatted and delivered off-line for incorporation into their web sites and procurement networks.

Rules based custom catalogs generated from a central catalog database for multiple entities

A logical and constraint-based hierarchical approach provides a highly flexible and expressive way in which to browse items stored in a database. The logical and constraint-based approach permits a user to create an arbitrary number of hierarchical representations of the items in a database. The approach permits items to be logically grouped on one level and grouped based on attribute/value constraints on the next. The hierarchical representation consists of nodes that are related to one another in a tree-like structure starting with a root node. Each node has a unique label, preferably indicative of the items in the database that it represents. Each node has a list of the labels of the nodes that are its children. Each node can only be the child of one parent node. Nodes may optionally express constraints based on attributes and their values that serve to define the scope of database items that fall under the node in the hierarchy. Each node inherits the constraints of its ancestors and therefore the scope of items in a database that that fall underneath a given node are defined by the aggregation of the constraints from the given node up to and including the root. A node that does not specify constraints instead specifies a logical grouping of items that cannot be specified by one or more constraints. The constraints are implicitly ANDed together in the aggregate. A logical grouping represents the equivalent of a logical ORing of constraints, but without the need for specifying attribute values or performing the function. A user browsing a database using the hierarchy triggers a search of the database by selecting one of the leaf nodes in the hierarchy. The constraints are aggregated and a rule is established that includes all of the database items that meet the aggregation of constraints. A database query is derived from the rule, and the database is searched for all items that meet the aggregated constraints. A set of items is returned and displayed for the user.

Logical and constraint based browse hierarchy with propagation features

A maintenance tool is used to import and centrally maintain the data and metadata representing catalog items in a catalog database. The maintenance tool is further used to create and maintain constraint-based rule sets defining custom catalogs that are subsets of the items in the database, constraint-based pricing profiles that define custom pricing schemes to be applied by the items in the database, and a primary browse hierarchy that represents the items in the database. The maintenance tool is used to create and maintain accounts for organizations and to assign to each organization a custom catalog and a pricing profile. The maintenance tool republishes the data on a periodic basis to update the custom catalogs and pricing profiles based on additions and modifications to the database, the rule sets, and the pricing profiles, and to generate new custom browse hierarchies from the primary hierarchy. The maintenance tool may be used to generate physical manifestations of the custom catalogs, pricing information and browse hierarchies for exportation to organizations not directly coupled to the catalog database through a network.

Growing community of inventors

Austin, TX, United States of America

Jeremy Weinrib