The present invention relates to an online item and product management system that is associated with an online category management system. In particular, the present invention relates to a product management system wherein users of the system can become category experts and manage categories and associated SKUs in the online item and product management system.
The Internet has provided amazing opportunities to connect people and provide information. However, it is sometimes difficult to obtain all of the information people need, especially when the domain of the information is quite large. For example, if the domain of information is products, there are a great many products that users might be interested in. Additionally, different users may be searching for different pieces of information about a product. For example, some users may want to buy or sell a product, while other user may want to value products they already have. Still other users may simply wish to learn more about a product.
Many resources on the Internet can help solve aspects of this problem. For example, search engines can be used to find web pages with relevant content. Discussion boards, newsgroups, and blogs on the Internet can also be used to find information. However, all of these sources of information can at times be incomplete, untrustworthy, or difficult to find for one reason or another.
It would be desirable to have a centralized location where information on a variety of products could be easily found and where those products can be easily exchanged between users of this centralized community.
Embodiments of the present invention relate to an online category management system and related taxonomy in which products are classified in a structured fashion. In many prior systems, the taxonomy that is used to organize, classify, and give structure to items in online item and product management systems is controlled by an administrator of the system. Using an administrator to create the taxonomy of the product management system presented some problems. For example, systems that relied upon system administrators to create the taxonomy of the online category management system may not always update their category listings as quickly and efficiently as the users of the system might like. Additionally, a system administrator may not be particularly knowledgeable about various categories in the system, and the taxonomy decisions made by such an administrator may not always be the decisions that well-versed users would prefer. These problems can make it more difficult for users of the system to find the products and information they seek.
Embodiments of the present invention improve on these prior systems by allowing select users to become category experts. A user may apply to become a category expert for one or more categories in which the user has particular expertise or other qualities that would make for a good category expert. According to some embodiments, a utility can be developed for eligible candidates to apply to become category experts. A successful category applicant can create, modify, edit, and manage information about a specific category and its taxonomy together with the products. Additionally, a user selected to become a category expert can use a category expert workbench to create, manage, and maintain a category together with the associated taxonomy for a structured product classification. Embodiments of this system can enhance the relevance and accuracy in searching product information within a particular category on the Internet. The collection of these categories will produce a catalog in which the general public can use to add, browse and search product information and their related meta-data such as ownership and pricing information.
In addition, the workbench or utility empowers category experts to perform category management tasks such as the review and approval of stock keeping units (SKUs), engage in community forums, discussion, and networking, and foster the growth of the category in term of the number of SKUs created. The category structure is intimately linked to a product management system wherein users can add a SKU, provide information about the SKU, and lay claim to it to share in a portion of the revenues. Likewise, the category expert will also be rewarded in a similar fashion by having a share of the revenues generated by advertisement and transaction fees within the category.
Embodiments of the present invention address these and other problems.
In an embodiment of the present invention, a computer system is provided that maintains information about products and provides for transactions between users buying and selling those products as well as providing a public exchange for valuing those products. The system also tracks the users who set up products in the system as well as maintain product categories. That tracking can be used for sharing revenue related to those products with the users, controlling which users become “experts” for a category of products or specific products, allowing for user-to-user interactions, etc.
According to one embodiment, an apparatus for managing one or more categories and one or more SKUs associated with the one or more categories is disclosed. The apparatus comprises an item database and an item server coupled to the item database. The item server is capable of reading and modifying the item database. The item database comprises a table of categories and a table of SKUs. One or more SKUs stored within the table of SKUs is associated with one or more categories stored in the table of categories. A plurality of users have the ability to create one of more SKUs in the table of SKUs via the item server. A category expert is associated with one or more categories. The category expert has the ability to create and modify the one or more categories associated with the category expert within the table of categories via the item server. The category expert is one of the plurality of users.
According to one embodiment, a method is disclosed for managing one or more categories and one or more SKUs associated with the one or more categories in a product management system. The product management system comprises an item database and an item server, wherein the item server is coupled to the item database and wherein the item server is capable of reading and modifying the item database. The item database comprises a table of categories and a table of SKUs. The method comprises giving a category expert the ability to create and modify one or more categories in the table of categories. The category expert is selected from a plurality of users. The method then publishes the one or more categories to the plurality of users so that the plurality of users have permission to view the one or more categories. Next, the plurality of users are given the ability or create one or more SKUs in the table of SKUs, wherein the SKUs are associated with the one or more categories.
An improved product management, transaction and presentation system is described herein. According to some embodiments, a category expert can set the rules for SKU (Stock Keeping Unit) entry and templates, in effect providing their expertise to the SKU entry process.
In one embodiment, computer system 200 typically includes a monitor 210, a computer 220, user output devices 230, user input devices 240, communications interface 250, and the like.
As shown in
User input devices 230 can include various possible types of devices and mechanisms for inputting information to a computer 220. These may include a keyboard, a keypad, a touch screen incorporated into the display, audio input devices such as voice recognition systems, microphones, and other types of input devices. In various embodiments, user input devices 230 are typically embodied as a computer mouse, a trackball, a track pad, a joystick, wireless remote, drawing tablet, voice command system, eye tracking system, and the like. User input devices 230 typically allow a user to select objects, icons, text and the like that appear on the monitor 210 via a command such as a click of a button or the like.
User output devices 240 can include various possible types of devices and mechanisms for outputting information from computer 220. These may include a display (e.g., monitor 210), non-visual displays such as audio output devices, etc.
Communications interface 250 provides an interface to other communication networks and devices. Communications interface 250 may serve as an interface for receiving data from and transmitting data to other systems. Embodiments of communications interface 250 typically include an Ethernet card, a modem (telephone, satellite, cable, ISDN), (asynchronous) digital subscriber line (DSL) unit, FireWire interface, USB interface, and the like. For example, communications interface 250 may be coupled to a computer network, to a FireWire bus, or the like. In other embodiments, communications interfaces 250 may be physically integrated on the motherboard of computer 220, and may be a software program, such as soft DSL, or the like.
In various embodiments, computer system 200 may also include software that enables communications over a network such as the HTTP, TCP/IP, RTP/RTSP protocols, and the like. In alternative embodiments of the present invention, other communications software and transfer protocols may also be used, for example IPX, UDP or the like.
In some embodiment, computer 220 includes one or more Xeon microprocessors from Intel as processor(s) 260. Further, one embodiment, computer 220 includes a UNIX-based operating system.
RAM 270 and disk drive 280 are examples of tangible media configured to store data such as embodiments of the present invention, including executable computer code, human readable code, or the like. Other types of tangible media include floppy disks, removable hard disks, optical storage media such as CD-ROMS, DVDs and bar codes, semiconductor memories such as flash memories, read-only-memories (ROMS), battery-backed volatile memories, networked storage devices, and the like. RAM 270 and disk drive 280 may be configured to store the basic programming and data constructs that provide the functionality of the present invention.
Software code modules and instructions that provide the functionality of the present invention may be stored in RAM 270 and disk drive 280. These software modules may be executed by processor(s) 260. RAM 270 and disk drive 280 may also provide a repository for storing data used in accordance with the present invention.
RAM 270 and disk drive 280 may include a number of memories including a main random access memory (RAM) for storage of instructions and data during program execution and a read only memory (ROM) in which fixed instructions are stored. RAM 270 and disk drive 280 may include a file storage subsystem providing persistent (non-volatile) storage for program and data files. RAM 270 and disk drive 280 may also include removable storage systems, such as removable flash memory.
Bus subsystem 290 provides a mechanism for letting the various components and subsystems of computer 220 communicate with each other as intended. Although bus subsystem 290 is shown schematically as a single bus, alternative embodiments of the bus subsystem may utilize multiple busses.
Item database 304 contains a table of item records 305. Item records can further be organized into categories in the item database. Item record 306 represents one item record or one page from item records 305. Each item record in item database 304 is associated with a SKU number. As used herein, the “term item record” and “SKU” are interchangeable. The term “SKU” may also be used for the item the SKU refers to. Often times, the item the SKU refers to is presented to the user, along with other information, in the form of a web page or other similar presentation means.
At a high level, each SKU within item database 304 is homesteaded by a user of the invention. When a SKU is homesteaded by a user, the SKU is claimed by the user, and an ownership interest in the SKU is given to the user. As used herein, the terms homesteaded, claimed, owned, or variants thereof all refer to this concept. A SKU owned by the user can be referred to as a homesteaded item. When a user homesteads a SKU, the user gains the potential for earning revenue off of that SKU.
A user can acquire a SKU ownership interest, and thus a financial interest, in a SKU in a variety of ways. One such way is for a user to add an item that is not currently listed in item database 304. Another way is for a user to correct, improve, enhance or otherwise “perfect” an existing item, thereby laying claim to it. Other methods may also exist for users to obtain an ownership interest in a SKU. For example, in some embodiments a user can acquire a SKU ownership interest by trading for the interest from another user.
Another method for a user to acquire an financial interest is to become a category expert. A category expert is much like a securities analyst in the stock market or a subject matter expert in the technology world. The category experts may write reports on the categories they cover to provide analysis and guidance to help users make informed decisions whether to buy, sell, or hold some specific items. The report may contain a product review, valuation opinion, and/or answers to questions posted by users. A portion of the category revenue may be allocated to the experts for sharing knowledge, driving traffic, and/or raising the performance of a category that satisfies the needs of the community.
Additionally, a category expert may create categories and construct the taxonomy associated with the category. The category expert can define the attributes that distinguish one SKU from another SKU within the category and define the relationships among the various attributes of the SKUs in the category. Once the category is published to users, the category expert can review and approve SKUs submitted by users for inclusion in the category and ultimately to the item database 304. A SKU may be placed into a “pending” table for review and approval/rejection. This pending table may be periodically reviewed by a category expert, catalog administrator, other reviewing entity who can review that submission and either approve or reject it. If approved, the user can be notified, and at that point the user will officially own the SKU and can start deriving future revenue from it. It is at this point the user becomes a homesteader for that particular item. In one embodiment, the relationship between a SKU Owner and a SKU can be stored in the Item Database 304 in a table of associations. If the submission is rejected, then the user may or may not receive an opportunity to resubmit the SKU depending on the quality of the initial submission.
A user can be a homesteader, a category expert, or other person with interest in a SKU or category all at the same time, and as a result, there are many different incentives given to a user to become an active, productive, participating member of the community. Additionally, the ability for a user to play many different roles within the system allow for users to have much control over how the system is organized and how the system can grow.
Revenue related to a SKU typically comes from one of two sources: buying/selling transactions between users involving a SKU and advertising revenue received from third-party accounts. This revenue can be collected in a central location. For example,
Block 410 represents the SKU itself. Each SKU entry contains a list of attributes that describe the SKU in detail. For example, information about the manufacturer, model number or name, color, price, etc., of the SKU may be stored.
Additionally, each SKU entry contains information that links the SKU to a variety of other pieces of information. For example, the SKU can contain a reference linking the SKU to the SKU_Owner 420. Advertising 430 and transaction 440 tables can also link to the SKU so that revenue generated by this SKU can be uniquely tracked. SKUs may also belong to a category 450 and these categories may be subordinate to one or more “parent” categories as well. This category information can be stored in a category table. The category table may be stored in the item database 304 or in another database. The branch within the category tree which a SKU belongs to may determine the specific attributes that are required for that SKU. The category may also have one or more category experts associated with the category.
In the disclosure below, various actions that a category expert may take are described in detail. For example, a category expert may create categories, define the attributes associated with SKUs within a category, and accept SKUs to be associated with their categories. One skilled in the art will recognize that these actions can be effectuated using a database structure such as the one illustrated in
According to various embodiments, a user 510 that wishes to become a category expert may fill out an application to become a category expert. This application process is shown at 520. During this process, information is collected from the user 510 so that a product management system administrator can properly judge whether the user 510 would make a good category expert for the category applied for by the user 510.
Application information collected using forms such as the ones illustrated in
After a category expert is accepted by an administrator, the new category expert may undergo a tutorial to familiarize him- or herself on the application of the category expert workbench. The category expert workbench will be described in more detail later in this disclosure. Upon completion of the computer-based training, the individual will be assigned to the category he or she applies to manage as an expert.
Referring back to
In the embodiment illustrated in
In
A description can be associated with each attribute defined by the category expert. A description can help explain what data should be entered for a specific attribute. This feature can be useful if the name of the attribute does not necessarily clearly communicate what data the attribute is meant to capture. For example, if an attribute was named “power” the description can explain that a user should enter the horsepower of a car rather than the available torque.
Now referring back to
Once the category is published, the category expert can review and approve the stock keeping units submitted by users for inclusion in the category and ultimately to the catalog. Once a category is published, users can create, trade, perfect, or take other actions in SKUs. Users may also discuss various topics related to the category in message boards associated with the category. Revenue generated from these activities can be shared between users, category experts, and other users as dictated by an appropriate revenue sharing scheme. Category experts themselves can also act as user in the community to buy, sell, or trade SKUs. Such a category expert is illustrated at 560.
Category experts also have many duties associated with their category. In one embodiment, a category expert workbench can be used by the category expert to carry out these duties. This is shown at 570. As mentioned previously, category experts have many duties associated with SKUs. For example, category experts have the duty to approve new SKUs submitted by users for their category. The category expert workbench can also be a tool that category experts use to communicate with owners, collectors, or interested parties on category activities and product information.
Further embodiments can be envisioned to one of ordinary skill in the art after reading this disclosure. In other embodiments, combinations or sub-combinations of the above disclosed invention can be advantageously made. The example arrangements of components are shown for purposes of illustration and it should be understood that combinations, additions, re-arrangements, and the like are contemplated in alternative embodiments of the present invention. Thus, while the invention has been described with respect to exemplary embodiments, one skilled in the art will recognize that numerous modifications are possible.
For example, the processes described herein may be implemented using hardware components, software components, and/or any combination thereof. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that various modifications and changes may be made thereunto without departing from the broader spirit and scope of the invention as set forth in the claims and that the invention is intended to cover all modifications and equivalents within the scope of the following claims. In addition, the technique and system of the present invention is suitable for use with a wide variety of methodologies for programming a device. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents.
This application claims priority to U.S. Provisional Application No. 61/048,907 entitled “Category Expert Workbench” filed on Apr. 29, 2008, which is hereby incorporated in its entirety for all purposes. Additionally, this application is related to U.S. application Ser. No. 12/188,100 entitled “Client-Server System For Managing an Item Database and Item Transactions with User-Item Associations” filed on Aug. 7, 2008, which is hereby incorporated in its entirety for all purposes.
Number | Date | Country | |
---|---|---|---|
61048907 | Apr 2008 | US |