Abstract:
A method for determining whether an entered character string corresponds to terminology utilized in a catalogue database, comprising: accepting the entered character string; determining if the character string matches terminology utilized in the database; if the character string does not match terminology utilized in the database, applying at least one action to the character string to create an edited character string; and determining if the edited character string matches terminology utilized in the database.

Description:
BRIEF DESCRIPTION OF THE DRAWINGS 
       [0001]      FIG. 1  illustrates a system for determining whether an entered character string corresponds to terminology utilized in a catalogue database, according to one embodiment. 
         [0002]      FIG. 2  illustrates components of a scrubbing application, according to one embodiment. 
         [0003]      FIG. 3  illustrates a method for determining whether an entered character string corresponds to terminology utilized in a catalogue database, according to one embodiment. 
     
    
     DESCRIPTION OF EMBODIMENTS 
       [0004]    In one embodiment, the system and method analyzes seller&#39;s listings and compares the listings to a pre-defined taxonomy to determine the proper locations for the listings. In one embodiment, the listings are ticket listings made up of a character string. Those of ordinary skill in the art will see that other types of listings can also be utilized, including any ecommerce item catalogues. For example, those of ordinary skill will see that several embodiments of the present invention can be used in various electronic catalogs where items entered are specific items that have to match up with a pre-defined catalog of items. Thus, several embodiments of the present invention can be used to catalogue any item or service (clothing, electronics, automobiles, tickets) that has attributes (e.g., size, color, style, feature set), which attributes set the item or service apart from other items or services in its family (e.g., megapixels for cameras, section # for tickets). In the case of ticket listings, the system and method analyzes data in the character string (e.g., section and/or row information) provided by the seller. The character string is edited and analyzed utilizing a pre-defined set of rules relating to the venue taxonomy that describes the layout for the venue. In one embodiment, a separate catalogue database can be created for each venue or type of venue. In another embodiment, a catalogue database combining many types of venues can be utilized. In one embodiment, the character string is attempted to be matched to a particular section in the catalogue database before and after each type of editing and analyzing. 
         [0005]      FIG. 1  illustrates a system for determining whether an entered character string corresponds to terminology utilized in a catalogue database, according to one embodiment. Matching application  101  includes a queuing application  110  and a scrubbing application  115 . The queuing application takes all of the input strings and queues them for processing based on priority. A priority is defined based on pre-defined rules such as who entered the listing, what process caused the listing to be sent to the scrubbing application  115 , etc. The scrubbing application  115  runs the character string through a pre-defined set of rules and compares the character string to data in the transactional database  120  (e.g., a catalogue database). The user interface  105  communicates with the matching application  101  to provide the character string to the matching application  101  so that the character string can be edited and analyzed. As users of the user interface  105  often do not use consistent terminology when describing their tickets, the matching application  101  allows these users to list tickets in a non-restrictive way, and is able to display the listed tickets consistently so that like tickets can be accurately compared. In one embodiment, the user of the user interface  105  is able to view the resulting edited and analyzed character string. In another embodiment, the edited and analyzed character string is not shown to the user of the user interface  105 . 
         [0006]      FIG. 2  illustrates components of a scrubbing application, according to one embodiment. The scrubbing application  115  includes a cleaning application  205 , a stemming application  210 , a formatting application  215 , and an alias application  220 . The cleaning application  205  cleans up the character string. In one embodiment, this is done by removing non-alpha-numeric characters, and making sure the spacing between letters and numbers is standardized. Thus, for example, the character string “5% Sec” could be cleaned to remove the “%” character, so that the character string becomes “5 Sec” In one embodiment, standardized spacing could include adding spacing between letters and numbers, and also reducing all spacing to a standardized space, such as one space. Thus, for example, the character string “5 Sec” could be changed to “5 Sec”. The stemming application  210  applies stems to the character string. In one embodiment, this is done by changing recognized abbreviated words to full words, and/or changing full words to standard abbreviations. Thus, for example, the character string “5 Sec” could be changed to “5 Section”. The formatting application  215  formats the character string to a standardized format. In one embodiment, the first number can be moved to the first or last position in the character string. This is done so that the character strings are in a consistent format. Thus, for example, the character string “5 Section” could be changed to “Section 5”. The alias application  220  checks the character string for aliases. In one embodiment, the character string is checked to determine the existence of an alias for the string in the section taxonomy. For example, “section” could be searched and the alias “group” could be found. 
         [0007]      FIG. 3  illustrates a method for determining whether an entered character string corresponds to terminology utilized in a catalogue database, according to one embodiment. In  305  a character string is accepted. For example, “5% Sec” could be accepted. In  310  it is determined if the character string is in the database taxonomy. If yes, in the  311  the character string is associated with the internal identifier (for example, “Section A217” with consistent internal terminology “Section A217” or with internal number “27459”). If the character string is not in the database taxonomy, in  315  the character string is cleaned up. For example, non-alphanumeric characters are removed, spacing between letters and numbers is added, and all spacing is reduced to single space. Thus, for example, “5% Sec” could be changed to “5 Sec”. In  320  it is again determined if the character string is in the database taxonomy. If yes, the process moves to  311  as before. If no, in  325  stems are applied to the character string. Thus, for example recognized abbreviated words are changed to full words, and full words are changed to standard abbreviations. For example, “5 Sec” could be changed to “5 Section”. In  330  it is again determined if the character string is in the database taxonomy. If yes, the process moves to  311  as before. If no, in  335  the character string is formatted. For example, the first number can be moved to the last position in the character string, the last number can be moved to the first position in the character string, or any other movement can be made. For example, “5 Section” could be changed to “Section 5”. In  340 , it is again determined if the character string is in the database taxonomy. If yes, the process moves to  311  as described above. If no, in  345  the character string is checked for aliases. Thus, for example, the existence of an alias for the character string is checked in the venue section taxonomy. Say that in one venue, groups are used instead of sections. In this case, “Section” could be searched, and the alias “Group” could be found. “Section 305 could then be replaced with “Group 305”. In  350 , it is again determined if the character string is in the database taxonomy. If yes, the process moves to  311  as described above. If no, the character string is added to a report of unsuccessful matches. This report is then reviewed (either manually or electronically) to determine which of the cleaning, stemming, formatting and/or alias applications must be modified to capture any additional generic terms. Those of ordinary skill in the art will see that the cleaning, stemming, formatting, and/or alias applications can be applied in any order. In addition, those of ordinary skill in the art will see that any combination of the cleaning, stemming, formatting and/or alias application, with or without additional applications, can be utilized. 
         [0008]    While various embodiments have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art(s) that various changes in form and detail can be made therein without departing from the spirit and scope of the present invention. In fact, after reading the above description, it will be apparent to one skilled in the relevant art(s) how to implement the invention in alternative embodiments. Thus, the present invention should not be limited by any of the above-described exemplary embodiments. 
         [0009]    In addition, it should be understood that the figures, which highlight the functionality and advantages of the present invention, are presented for example purposes only. The architecture of the present invention is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown in the accompanying figures. 
         [0010]    Further, the purpose of the Abstract of the Disclosure is to enable the U.S. Patent and Trademark Office and the public generally, and especially the scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or phraseology, to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. The Abstract of the Disclosure is not intended to be limiting as to the scope of the present invention in any way.