Abstract:
A self-evolving generic index for storing marketplace information for multiple types of items allows users to add new parameters, values and possibly new classifications for use in describing items. The new parameters/values/classifications can then be selected by other users for use in describing their own items. It is especially contemplated that the system can display information relating to the usage with which parameters/values/classifications have historically been employed in describing different types of items. This encourages users to be consistent in selecting parameters/values/classifications for both entering and searching data, while still allowing great flexibility.

Description:
BACKGROUND OF THE INVENTION 
     This invention relates to the field of wide access databases. 
     BACKGROUND 
     The Internet is by now the world&#39;s largest computer network, interconnecting millions of computers. One side effect of this large size is that the vast amount of information available on the Internet is often extremely difficult to access. Similar problems tend to occur on any wide access network, and in this discussion the Internet is used merely as an example of a wide access network. 
     Several attempts have been made to index the Internet, but each of these attempts has fallen short. One of the earliest attempts was to alphabetically index the names (URL addresses) of Internet users. Unfortunately, such an index is little more than an electronic &#34;white pages,&#34; and is generally only useful if one knows the exact name or address of the user to be contacted. A straight alphabetical index also provides little or no ability to access information by subject matter, unless the name happens to include an indication of the subject matter, as in &#34;Bob&#39;s Pharmacy.&#34; These shortcomings can be quite annoying when the amount of information is relatively small, and present profound difficulties as the amount of information grows. 
     Another attempt at indexing information on the Internet relies upon keywords. In keyword indices, users enter information into a freeform text field, and then the system, the system manager, or the user indexes key words found in the text. A considerable amount of scientific information is presently indexed in keyword indices such as Medline™. Although advantageous relative to URL indices, keyword indices are still impractical where the subject matter does not lend itself to keyword indexing. For example, if one is looking for a red colored automobile in a used car index, a keyword index would only be useful to the extent that all red cars are indexed according to the color red. Cars indexed as rose or magenta, crimson, ruby, vermilion or scarlet would not be located by a search for &#34;red.&#34; Moreover, as the number of records grows, keyword indices have seriously diminishing usefulness. For example, it does little good to conduct a search for red automobiles if the database locates 5000 records for red automobiles. 
     Still another attempt at indexing information on the Internet relies upon the use of specialty indices. In specialty indices the subject matter on a given database is limited to a particular type of product or service, and parameters are provided which specifically relate to that subject matter. Thus, a specialty real estate index may store data according to the parameters of property type (commercial, residential, undeveloped land, etc.), location, square footage, number of bedrooms, number of baths, style (Mediterranean, Cape Code, traditional, etc.), and price. Additional information may also be allowed in a comment or image field, but such information is typically not searchable or sortable, and is difficult to standardize. In addition, specialty indices are unable to properly handle multiple types of items, i.e., items which are generally described using inconsistent or otherwise different parameters. Thus, a real estate index is very poorly adapted for storing information relating to clothes or automobiles because the data parameters required for these items are almost completely inconsistent with the parameters useful for real estate. 
     One technique which has proven useful for organizing information relating to multiple types of items in a generic index is a hierarchical &#34;yellow pages.&#34; Thus, for example, the Big Book™ collects together Internet addresses for various categories such as attorneys, bookkeepers, florists and so on. The Big Book™ also indexes Internet addresses according to geographical location. Thus, one can select family law attorneys in Miami, rather than all attorneys, or all family law attorneys throughout the country. Despite these advantages, the &#34;yellow pages&#34; type of index is still not particularly useful where the subject matter one is searching for is not well categorized, or where the categories are vague or counterintuitive. For example, if one is searching for zipper manufacturers, a &#34;yellow page&#34; type index may not have any categories specifically for zippers, or zippers may be listed under some obscure category such as &#34;interlocking clothing connectors.&#34; Still further, such indices are notoriously cumbersome when searching for related products. For example, if one is searching for all types of clothing connectors, a &#34;yellow pages&#34; type of index may require separate searches for zippers, buttons, snaps, etc. 
     Similar problems exist with respect to limiting the searches by geographical location. For example, an index may well have categories for continents, countries, major metropolitan markets, or even specific cities, but a user must still discover on his own how the database treats a particular address such as &#34;upstate&#34; New York. In short, unless a user knows how the index is organized, it may be nearly impossible to find desired information in a convenient manner. 
     A better solution for organizing information in a generic index involves hierarchical sorting of products and services as is done by Netscape™ and others. In a hierarchical index one can begin with a high level category, and then logically work down to a lower level category by selecting choices from various menus. Thus, in selecting patent attorneys one might sequentially choose the following categories: Services (level 1), Business (level 2), Legal (level 3), Attorneys (level 4), and finally Patent (level 5). The same strategy can also be applied to geographical locations. One may, for example, select Los Angeles by choosing North America (level 1), United States (level 2), California (level 3), Southern California (level 4) and Los Angeles (level 5). 
     Even generic indices which select records hierarchically, however, are unsatisfactory for accessing huge amounts of information. One problem is that presently known hierarchical indices do not allow users to select smaller subsets of records, and to sort the selected records, based upon parameters having particular meaning for the field being searched. A search in the field of automobiles can be used to illustrate these shortcomings. If one searches a presently known Internet index for used Ford™ automobiles, one might locate thousands of cars for sale. Clearly that number is too large for a user to realistically review every listing. Even if the number of selected records could be reduced by limiting the subject matter to a particular model, or by limiting the geographical location to a particular city, there might still be several hundred cars for sale, and it would be a terrible waste of time to scan through each of those records if the user is only looking for cars with purchase prices of less than $3000. Specialty indices may allow a user to limit the search by price, color, body style, and other parameters all at the same time, but that capability is not available on generic indices which additionally cover other types of items, such as real estate and computers. 
     Even if generic indices could be developed that use different sets of parameters for different products, the creation costs of such an index would be enormous. There are millions of different types of products and services that need to be indexed, and if each type has five to ten different parameters, one would have to enter tens of millions of parameter-type pairs. This would be unrealistic not only from a labor standpoint, but also because it would be impossible for any given developer to understand all the different parameters applicable to all the different types of products. It is unclear, for example, just what appropriate parameters would be for various &#34;chat rooms&#34;. Only those individuals having interests in the relevant subject matters would likely know what parameters are best to use. Moreover, the parameters that are best for one person may be unsuitable for another person, and the most suitable parameters for any given subject matter may even change over time. In short, as marketplaces throughout the world evolve, it would continue to be unrealistic for any given developer to keep up with the evolution of desired parameters. 
     Thus, there is a continuing need to provide a generic index that can effectively handle multiple types of products having multiple parameters. 
     SUMMARY OF INVENTION 
     The present invention provides a self-evolving generic index for storing marketplace information for multiple types of items. The index is self-evolving in that users can add new parameters for use in describing items, and the new parameters can then be selected by other users for use in describing their own items. 
     In preferred embodiments parameters are not tied exclusively to particular types of items, but can instead be used with different types of items. Thus, the parameter, color, may be used to describe such diverse items as automobiles, shoes and telephones. In more preferred embodiments the system displays information relating to the usage with which parameters have historically been employed in describing different types of items. This encourages users to be consistent in selecting parameters for both entering and searching data, while still allowing great flexibility. In still more preferred embodiments the system also displays information relating to the usage with which data values have historically been used with particular parameters in describing specific types of items. This further encourages users to be consistent in selecting data values for both entering and searching data, while still allowing great flexibility. 
     Various objects, features, aspects and advantages of the present invention will become more apparent from the following detailed description of preferred embodiments of the invention, along with the accompanying drawing, in which like items are represented by like numerals. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     FIG. 1 is Venn diagram of data in a preferred database according to the present invention. 
     FIG. 2 is a schematic of a preferred data interface screen for use with an index according to one aspect of the present invention. 
     FIGS. 3A-3C are examples of a preferred item interface screen used in accordance with one aspect of the present invention. 
     FIG. 4 is an example of a preferred geography interface screen used in accordance with one aspect of the present invention. 
     FIGS. 5A-5K are diagrams of record, table or other data structures that can be advantageously used in conjunction with an index according to the present invention. 
    
    
     DETAILED DESCRIPTION 
     In FIG. 1 a preferred database 10 generally includes four intersecting sets of information: item information 20, posting entity information 30, parameter information 40 and values information 50. The intersection 60 of these sets 20, 30, 40, 50 represents records of particular interest to a user. 
     In FIG. 2 a preferred data interface screen 100 generally comprises a title 110, advertising or other graphics 120, an item classification hierarchy 130, a market hierarchy 140, and a data selection and display matrix 170. 
     Title 110 is used for identification purposes only, and is completely optional. Here, the name PROMETHIUS is used to identify the database, but any suitable trademark or descriptive name may be used. 
     The advertising or other graphics 120 are again entirely optional, and are shown here merely for the sake of exemplification. On the other hand, it is contemplated that advertising space may be sold to vendors as a significant source of funding, and that such advertising may be context sensitive to increase its value to vendors. Thus, for example, when a user is viewing information on airline fares, the graphics 120 may advantageously display advertising for an airline. Similarly, when a user is viewing information on automobiles in Los Angeles, the graphics 120 may advantageously display advertising for a Los Angeles area automotive dealer. 
     Item classification hierarchy 130 is advantageously 3 to 5 levels deep, and is preferably arranged in a logical manner to provide convenient access to users. In the particular example of FIG. 1, the user has selected &#34;Automobiles&#34; as the first or &#34;highest&#34; level, &#34;Used vehicles&#34; as the second level, and &#34;Sport Utility Vehicles&#34; as the third level. There are innumerable ways to establish and maintain classifications for these various levels, but at the inception of a database or database system, it is contemplated that preset classifications will be established for at least the first two levels, and preferably the first three levels. Optionally, however, it is contemplated that item classifications on every level can be open to supplementation by users as described below. 
     In one contemplated embodiment, each level of the item hierarchy may have a drop down menu that presents an alphabetic list of choices. Thus, for example, the highest level of the item hierarchy may include the following choices: Advertising, Air Conditioning, Ambulance, Answering Service, Appliances, Attorneys, Automobiles, Banks, Boats, etc. Choices in the second level would then depend on what choice is picked at the first level. For example, the second level choices under Automobiles may include: New Parts, New Vehicles, Used Parts, Used Vehicles. In the same manner, choices in the third level would depend on what choice is picked at the second level. Continuing with this example, third level choices under Used Vehicles may include Passenger Cars and Sport Utility Vehicles. 
     Item selection may advantageously be accomplished on a subsidiary item selection screen by clicking on an item screen selector such as item screen selector button 132. The subsidiary item selection screen may appear as in FIGS. 3A, 3B and 3C, with FIGS. 3A and 3B corresponding to the selection of &#34;Sport Utility Vehicles&#34; on FIG. 2, and FIG. 2C exemplifying selection of an unrelated item, &#34;chip&#34;. 
     FIG. 3A again depicts an optional title 110, a description entry field 134, and a data table 135. In this particular data table 135 has six columns: item selection column 136A, major category column 136B, minor category column 136C, item description column 136D, usage column 136E, and slider column 136F, and seven rows: title row 137A, limitation row 137B, data rows 137C-137F, and new data entry row 137G. 
     In the preferred embodiment shown, the data rows 137C-137F are all filled in by the system based upon the description entered by the user in the description entry field 134. Subsequently, rows may advantageously be selected in which the description matches any of the major, minor or, item descriptions 136B-136D. Thus, based upon the user having entered &#34;Sport Utility Vehicles&#34; in description entry field 134, the system displays data row 137C in which &#34;Sport Utility Vehicles&#34; matches data in the item description column 136D, data rows 1137D and 137F in which &#34;Sport Utility Vehicles&#34; matches data in the minor category column 136C, and displays data row 137E in which &#34;Sport Utility Vehicles&#34; matches data in the major category column 136B. It is also contemplated that the user can enter whatever data he or she wants in new data entry row 137G, creating major, minor and item descriptions at will. What is expected to maintain general consistency throughout the system is that the user can see what categories have been chosen by others in the usage column 136E, and will presumably want to use categories that have proven to be popular in the past. 
     The term &#34;usage&#34; is employed herein in its broadest possible sense to include information relating to occurrence, absolute or relative frequency, or any other data which indicates the extent of past usage with respect to the various choices. It is contemplated, for example, that the choices for which usage information is displayed would include one or more of item classifications, geographic classifications, parameters, and values. It is also contemplated that the usage information displayed would relate to subsets of choices determined by a user&#39;s previous responses. Thus, when selecting a minor item classification, the system may display a listing of possible minor item classes determined by the user&#39;s selection of major classification, along with relative usage information among the displayed minor classes. Similarly, the item descriptions displayed, and the corresponding usage information, would preferably be a function of the major and minor item classes selected. As yet a further example, the parameters and/or values displayed, and the corresponding usage information would preferably be a function of the item selected, and possibly also of the geographic class(es) selected. 
     Usage information can be presented in many ways. In FIGS. 3A-3C, usage information is shown on a relative frequency scale as an integer from 1 to 100, with the data rows 137C-137F sorted from highest frequency to lowest frequency. In other embodiments, usage information can be displayed by depicting absolute frequency, by depicting occurrence of number of uses or &#34;hits&#34;, or even by displaying data or data rows in different colors or using other identifying indicia. 
     Depending on the intersection between information in the data base and the data entered into the description entry field 134, there may be an unwieldy number of data rows displayed. In that instance it may be helpful for the user to limit the number of data rows by selecting one or more values for a particular major category, minor category or item description. This can be accomplished in many ways, such as with a pull down menu. In FIG. 3B, the data rows have been limited by entering the choice &#34;Automobiles&#34; as the major category in row 137B. This selection has limited the data in rows 137C, 137D and 137E of FIG. 3B to data that was present in rows 137C, 137D and 137F of FIG. 3A. 
     Also, by way of example in FIGS. 3A and 3B, the user has selected a particular value row for inclusion into the main data interface screen of FIG. 2. This has been accomplished by clicking on, or otherwise marking column 136A of row 137C in both FIGS. 3A and 3B. Presently it is contemplated that a user will select only one value row, but, of course, it is also possible that the system could be designed to accommodate selection of multiple data rows. 
     FIG. 3C is another example of an item hierarchy selection screen. Here, the selection interface is identical to that already described with respect to FIGS. 3A and 3B, but instead of selecting for item description &#34;Sport Utility Vehicles&#34;, a user is selecting for item description &#34;chip&#34;. This particular selection is instructive because there are many different types of chips, from potato chips to casino chips to various types of building materials. It is contemplated that this particular interface will allow a user to select among these choices more readily than with any previous system. 
     FIG. 4 is analogous to FIG. 3A except that major category, minor category and item description columns 136B-136D have been replaced with region category 146B, market category 146C and submarket category 146D columns. As with item classification, it is contemplated that usage information for the geographic classifications may be displayed as shown in column 146F, the display of data rows can be limited by entry or selection of data in limitation row 147B, one or more data rows can be selected in column 146A, and data from a selected row can be echoed back to the market hierarchy 140. Supporting interface screens corresponding to FIGS. 3B and 3C are also contemplated, but are not shown. 
     Focusing again on FIG. 2, data selection and display matrix 170 has 10 columns: a row selection column 172A, parameter columns 172B-172I, and a slider column 172J, and seven rows: header row 174A, limitation row 174B, data rows 174C-174F, and new data entry row 174G. 
     It is contemplated that the parameters shown in row 174A of columns 172B-172I can be selected by the user, as from a drop down menu (not shown). The drop down menu would preferably list only those parameters which have been used in the past by other users with respect to the item in item classification hierarchy 130, and would preferably list such parameters with some sort of usage information, such as was described above with respect to item and market selection in FIGS. 3A-3C and 4. In this particular example, the user has selected parameters &#34;make&#34;, &#34;model&#34;, &#34;price&#34;, &#34;year&#34;, &#34;mileage&#34;, &#34;color&#34;, and &#34;posted&#34;. An eighth parameter could have been selected for column 172F, but in this example the user chose not to add an eighth parameter. Ninth and further parameters could also be selected if the system were set up to do so, and the screen could scroll left and right to conveniently accommodate additional such parameters. But it is presently contemplated that eight parameters is an optimal the maximum number of parameters. On yet another screen (not shown), or perhaps as part of the drop down parameter selection menus, or even in row 174A, the user can enter a new parameter, either one that is entirely new or one that has been used before with respect to another type of item. 
     Sorting can take place in any number of ways, or alternatively the data list can be non-sorted. For simplicity, it is contemplated that the data rows will be sorted according to parameters selected, and the values for the different parameters. Thus, in FIG. 2, the primary sort is the first parameter selected, (make), the secondary sort is the second parameter selected, (model), the tertiary sort is the third parameter selected, (price), and so forth. 
     In row 174B it is contemplated that the user can select a specific value (or a range of values where the parameter contemplates a numeric value) to limit the number of data rows. For columns where no data is entered in row 174B, the system preferably has no additional selection for the corresponding parameter. 
     Data rows 174C-174F present the parameter data available in the system for records that match the item hierarchy 130, the market hierarchy 140 (if given), and the various values set forth in limitation row 174B. Of course, since users may be free to load data on the system by describing items according to any parameters they see fit, data may well be unavailable for any given parameter chosen by a subsequent user. Thus, it is contemplated that the lack of data for a particular parameter would serve to limit selection only if a data value for that parameter was given by the searching user. For example, if a user looking for automobiles selected weight as a parameter, but gave no data for the weight parameter, then the system would still pull up automobiles matching the user&#39;s other criteria even if records for those automobiles did not include weight data. On the other hand, if the user selected weight as a parameter, and also gave a weight value of &gt;4000 pounds, then only automobiles matching all other parameter value pairs, and which have weight greater than 4000 pounds would be selected. 
     New data row 174G can be used for entering new data, preferably up to one data value for each parameter selected. Significantly, each user will probably be limited to a maximum number of parameters, both to keep the size of the database within some sort of manageable limits, and to encourage users to employ parameters that others have used before. In this manner, each user will likely enter less than about 8-10 values for each item. 
     Of course, all of the above can be implemented in any number of ways, provided that the user is able to select choices based in some manner upon the usage (relative or absolute) of use of those choices by others. Nevertheless, some implementations are undoubtedly better than others, and it is contemplated that the system can be implemented as discussed below with respect to FIGS. 5A-5L. 
     FIGS. 5A-5D represent portions of sample tables for measurements, parameters, units, and values, respectively. The measurements table of FIG. 5A would likely be maintained by a system administrator, and would advantageously include all likely types of measurements that users would want to use. It is important to note that the term &#34;measurements&#34; refers to categories of measurements rather than units, or parameters for which such measurements may be employed. Thus, typical measurements are distance, weight, count, money, time, and so forth, and by way of example these particular measurements are listed as the first five records of the sample measurements table. 
     The parameters table of FIG. 5B would likely be maintained by individual users as a function of entering data as described above, and will therefore likely contain thousands of user defined parameters, all of which are used in one way or another to describe one or more items. By way of example, parameters may include make, model, year, color, odometer reading, condition, price, and so forth, and these parameters are listed as the first seven records of the sample parameters table. 
     The units table of FIG. 5C would likely be maintained by a system administrator, and would advantageously include all likely types of units that users would want to use. The record number is listed in the first column, the name of the unit is given in the second column, a cross-reference to the record number of the related measurement is given in the third column, and the interrelationships among the various units in this grouping is given in the fourth column. For example, records 1 through 7 in FIG. 5C all relate to units used to describe distance, which is the first record in the measurements table of FIG. 5A. Thus, column 3 of FIG. 5C for these rows all show the numeral 1, to point to the second record in the measurements table of FIG. 5A. Similarly, records 8 through 11 in FIG. 5C all relate to units used to describe weight, which is the second record in the measurements table of FIG. 5A. Thus, column 3 of FIG. 5C for these records all show the numeral 2, to cross-reference the second record in the measurements table of FIG. 5A. 
     The values table of FIG. 5D would usually be maintained by individual users as a function of entering data as described above, and will therefore likely contain many thousands of user defined values. In this particular case, the value record number is listed in the first column, the literal of the value is listed in the second column, and a cross-reference to the units table of FIG. 5C is listed in the third column. In this manner, the first three data rows of FIG. 5D correspond to a value of 5200 dollars, 1799 dollars and 2450 dollars, respectively. Similarly, the fourth record corresponds to a value of &#34;red&#34; with no units, and the seventh record corresponds to 89 kilograms. 
     One may, of course, ask whether the complexity of the above-described table structure is really necessary. The answer is that such complexity is not necessary at all, but is preferred because it is operationally efficient. The system is also flexible in that it can accommodate users from many different countries, who may enter data using all sorts of different systems. Thus, the system as described herein can readily received data in meters, but display the data in miles. 
     FIGS. 5E and 5F are sample tables that may be employed to store data regarding vendors, where the term &#34;vendors&#34; is used in its broadest possible sense to mean any person, company or other entity providing information. In many instances vendors will be those storing information on the system, and seeking a buyer. In other instances, vendors will be those merely advertising information, such as web site identifiers, but offering nothing at all for sale. In still other instances an intermediate situation may apply. 
     In view of the descriptions herein of the other tables, the headings of the tables in FIGS. 5E and 5F should be self explanatory. Among other things, the first column of the table in FIG. 5F is the branch record number, while the second column is a cross-reference to a vendor record number. It is contemplated that data in these tables will be entirely maintained by users, with access to individual records being limited according to a password maintained in the fifth column of the table of FIG. 5E, or by some other security arrangement. 
     As noted above with respect to other tables, a system using data tables of FIGS. 5E and 5F may appear overly complex. But in reality such a system is contemplated to be highly efficient. According to the data tables shown, for example, a single vendor may have many addresses linked to a single vendor name. 
     FIGS. 5G through 5I show tables containing names of major, minor and item classifications, respectively. Naturally, if there were two or four levels of item hierarchy, then two or four tables may advantageously be used. Similarly, it is possible to store the relevant information for three levels in fewer than, or more than, three tables. 
     The table of FIG. 5G also has a frequency of use counter in the third column, which allows the system to conveniently display actual or relative frequency of use of the various major classifications. Such frequency information may, for example, be displayed in a drop down menu in the interface of FIG. 2. The frequency information will presumably aid a user in choosing among various classifications. For example, a user might learn that the classification of Automobiles is used approximately 100 times more often than Cars, and therefore decide to choose the major classification of Automobiles. 
     The table of FIG. 5H contains names of minor classifications, and additionally has a cross-reference to major classification records in the third column, and a frequency of use counter in the fourth column. Using this information, the system can provide a user with relative or actual frequency information for minor classifications related to a previously chosen major classification. 
     The table of FIG. 5I contains names of classifications in the third (i.e., item) level, of classification. The table additionally has a cross-reference to major classification records in the third column, a cross-reference to minor classification records in the fourth column, and a frequency of use counter in the fifth column. Using this information, the system can provide a user with relative or actual frequency information for item classifications related to a previously chosen major and minor classification combination. 
     Another set of three tables (not shown) would also probably be employed to store names and frequency information regarding the various geographic classifications. Again, the number of tables may vary according to the number of levels used by the system. 
     FIG. 5J depicts the &#34;Main&#34; data storage table. While there are many possible configurations for storing the information shown, and while different information can be stored than that shown here, the Main data storage table is considered optimized for preferred uses. Here, column 1 contains a record number, column 2 contains a cross-reference to the level 3 item hierarchy of the table in FIG. 5I, columns 3, 4 and 5 contain cross-references to the three geographic classification levels, column 6 contains a record entry or last update date, column 7 contains a cross-reference to the branch record number of the table in FIG. 5F, and columns 8 through 25 contain cross-references to the tables in FIGS. 5B and 5D for (up to) eight parameter-value pairs. Other data may be stored as well. Examples include sunset dates upon which records will be deleted, additional usage statistics for individual records, and so forth. 
     There will presumably be hundreds of thousands, or even millions of records in a table such as that depicted in FIG. 5J. For operational efficiency, one might therefore split up the table into smaller tables that handle subsets, and a particularly preferred breakdown is according to level 3 items record numbers. Thus, all records with level 3 item record numbers corresponding to each major item classification may advantageously be placed in a different logical database, or even a different physical database. 
     FIG. 5K contains a table that stores frequency information. In the preferred embodiment being described, column 1 contains a record identifier, column 2 contains a cross-reference to the level 3 item hierarchy of the table in FIG. 5I, column 3 contains a cross-reference to a parameter in the table in FIG. 5B, column 4 contains a cross-reference to a value in the table in FIG. 5D, and column 5 contains frequency information. The frequency information would presumably be updated on an on-going basis, effectively storing the number of &#34;hits&#34; for each item/parameter/value combination. In addition, there will advantageously be an additional record for each item/parameter pair, collecting frequency information for all values for that item and parameter. 
     Operation of a system using tables of FIGS. 5A-5K should be readily apparent to those skilled in the art. For example, for a user seeking information as opposed to a user adding information to the system, a typical scenario may be as follows. After the user has chosen an item classification, and perhaps a geographical classification, the system scans through the Main Frequency table as in FIG. 5K, selecting records corresponding to that item classification. The system then displays the corresponding parameters that can be selected for the first of eight parameter choices, along with corresponding frequency information as discussed above with respect to FIG. 2. If the user chooses to limit the number of records according to a value or value range for that parameter, then the system will display the corresponding values along with respective frequency information for each value displayed. The same applies to up to seven additional parameter choices or parameter/value pair choices employed by the user. Once the parameter choices and parameter/value pair choices have been entered, the system searches through Main Data Table as in FIG. 5J for records that match the parameters and values chosen by the user, and displays the corresponding records, if any. The user can then further modify the search, such as by sorting the results or altering the search parameters, or jump to a more detailed display screen (not shown) to display vendor or other additional information on a particular record. 
     Adding information to the system is contemplated to be accomplished in an analogous manner, except that the user should have interface subwindows (not shown) that permits addition of new classification text, parameters, values, vendors, and so forth. 
     In short, it should be immediately apparent from the above discussion that this system is a significant improvement over previously known wide access database systems, and especially over previously known publicly modifiable database systems. It allows users to quickly and efficiently access hundreds of thousands or even millions of records, and still find only those few records that are relevant. Even more importantly, the system allows users to add data and search for items according to parameters which are at the same time open to supplementation, but tending to be limited by the choices of others. 
     Thus, a self-evolving, self-enforcing database has been described herein. While specific embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art that many more modifications are possible without departing from the inventive concepts herein. Among other things, for example, the concepts discussed herein can be employed in narrow access databases, such as those directed to employees or customers of a single company. The invention, therefore, is not to be restricted except in the spirit of the appended claims.