US20100094848A1

US20100094848A1 - Adding Attributes and Labels to Structured Data

Info

Publication number: US20100094848A1
Application number: US12/469,468
Authority: US
Inventors: Bindu Reddy; Jonathan Brunsman; Ning Mosberger; Gaurav Ravindra Bhaya; Sarah Sirajuddin; David Kale; Jennifer L. Kozenski; Arvind Sundararajan; Puneet Agarwal
Original assignee: Google LLC
Current assignee: Google LLC
Priority date: 2005-10-23
Filing date: 2009-05-20
Publication date: 2010-04-15
Also published as: JP2009512953A; EP1955137A4; EP1955137A2; KR20080080098A; US20070100862A1; CA2626856A1; JP5300960B2; WO2007046829A3; US20130339338A1; JP2012053917A; WO2007046829A2; US20120290557A1; US9792333B2

Abstract

A method and system associating labels and attribute values with items in a collection of data. Providers can associate attributes and labels with their data or attributes and labels can be added to existing data. A preferred embodiment allows a content provider to upload data and to attach their own custom labels and attributes to items or to use predefined labels and attributes. Providers can upload data using a user interface or a bulk upload mechanism.

Description

RELATED APPLICATIONS

This application is a continuation application of U.S. application Ser. No. 11/256,883, filed Oct. 23, 2005, and is related to U.S. application Ser. No. 11/257,282, filed Oct. 23, 2005, both of which are incorporated by reference herein.

BACKGROUND OF THE INVENTION

Conventional search engines are capable of searching extremely large collections of information, such as the world wide web or very large databases. As the size of data collections to be searched grows, it is no longer enough to correctly return query results that match query terms entered by a user. Instead, it is desirable to provide a mechanism to help the user sort through the large amount of data returned from a search.
Several conventional search engines currently use various methods to organize the data returned in query result. The goal of such an organization method is to decide which query result will most interest the user. Conventional search engines generally use a variety of techniques to prioritize the results of a search, but these techniques are not ideal because they must make assumptions about the type of information for which the user is searching. For example, if the user enters “jobs” he might be searching for job postings, information of Steve Jobs, job statistics for a particular country, or any number of other items. Thus, when using a conventional search engine, a user would not enter just “jobs” as a query term. He would probably also enter additional query terms that narrowed the search. Unfortunately, he may also miss relevant listings that do not contain the narrowing terms.
Currently, it is difficult to search over different types of data that may or may not be stored on the world wide web. Conventional search engines usually operate on data from only a few sources. For example, web-based search engines traditionally allow a user to search pages on the world wide web. Web-search engines often have a “back-end” that indexes the collection of information in order to make it searchable. For example, web-based search engines periodically crawl the world wide web and create indices of the pages and sites crawled. Other search engines allow a user to search existing databases. Such search engines rely on a predetermined organization of the database. For example, if a database has known fields and attributes, the user can search within those attributes. For example, XML databases only accept well-formed XML inputs. If the data to be searched is not so-organized, XML databases are generally not able to accept the data or organize the data for search.
Other search engines allow a user to search databases or to search text documents having a flat organization. Such search engines must know about the organization of the database and the organization of the documents within it. The variety of locations and formats in which data are stored means that users must often search in multiple locations in multiple databases to find the information that they need.
It would be desirable for a collection of documents to be searchable via a web-based search engine and thus easily accessible to most people while, at the same time, containing a variety of types of documents and formats of data. Moreover, it would be desirable if the searchable collections of documents were organized in ways that could help users fine-tune their searches.

SUMMARY OF THE INVENTION

The described embodiments of the present invention associate labels and attribute values with data items to be searched. Providers can associate attributes and labels with their data or attributes and labels can be added to existing data. A preferred embodiment allows a content provider to attach his own custom labels and attributes to items or to use predefined labels and attributes. Providers can upload data using a user interface or a bulk upload mechanism.

BRIEF DESCRIPTION OF THE DRAWINGS

The teachings of the present invention can be readily understood by considering the following detailed description in conjunction with the accompanying drawings. Like reference numerals are used for like elements in the accompanying drawings.

FIG. 1( a) is a block diagram showing a data processing system in accordance with a preferred embodiment of the present invention.

FIG. 1( b) is a block diagram showing another data processing system in accordance with a preferred embodiment of the present invention.

FIG. 1( c) is an architecture diagram in accordance with a preferred embodiment of the invention.

FIG. 2( a) is a flowchart showing an overview of creation of a collection of data items searchable in accordance with a preferred embodiment of the present invention.

FIG. 2( b) is a flowchart showing an overview of searching the collection of documents and refining the search in accordance with a preferred embodiment of the present invention.

FIG. 3( a) is a flowchart showing a method of extracting labels and attributes from a collections of data items.

FIG. 3( b) is a flowchart showing a method of receiving a query term and displaying a query result.

FIG. 3( c) is a flowchart showing a method of determining which attributes to display for a given query result.

FIG. 3( d) is a flowchart showing a method of allowing the user to refine the displayed query result using labels and/or attribute values.

FIG. 3( e) shows a method performed periodically to determine whether any new, provider provided attributes should be added to the Core attributes for an information type.

FIG. 4( a) is an example screen shot of a search engine and a query term entered by a user.

FIG. 4( b) is an example screen shot showing query result from the query of FIG. 4( a) and also showing labels and attributes relating to the query result for the query term.

FIGS. 4( c)-4(g) are example screen shots showing additional attributes and labels and how a user might narrow his search using attributes and/or labels.

FIG. 5( a) shows a data format used to store attributes and labels for a collection of searchable data.

FIG. 5( b) shows an example of an attribute stored using the format of FIG. 5( a).

FIG. 5( c) shows an example of a label stored using the format of FIG. 5( a).

FIG. 5( d) shows an example data structure to map information types to their attributes.

FIG. 5( e) shows an example of an information type mapped to some example attributes for that information type.

FIGS. 6( a)-6(e) are example screen shots showing a user interface allowing a provider to edit and enter data into the system.

FIG. 7 is an example screen shot showing a user interface for registering a bulk upload file.

FIGS. 8( a)-8(d) show how a provider does a bulk upload of data and attribute values.

The figures depict embodiments of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.

DETAILED DESCRIPTION OF EMBODIMENTS

The following paragraphs describe various embodiments of a system to upload and search structured data in accordance with the present invention.
FIG. 1( a) is a block diagram 100 showing a data processing system in accordance with a preferred embodiment of the present invention. FIG. 1( a) includes a plurality of client data processing systems 110 a . . . 110 n, a network 130, and a server data processing system 120. In the Figure, an example user data processing system 110 a includes a processor 140, a browser 150, and a memory 160. User data processing system 100 or its components can be any appropriate data processing system including but not limited to a personal computer, a wired networked computer, a wireless network computer, a mobile phone or device containing a mobile phone, a handheld device, a thin client device, some combination of the above, and so on. Network 130 can be any network that allows communication between one or more of the user data processing systems 110 and the server data processing system 120. For example, network 130 can be but is not limited to the Internet, a LAN, and WAN, a wired network, a wireless network, a mobile phone network, a network transmitting text messages, some combination of the above.
In a preferred embodiment of the invention, user data processing system 110 a includes browser software 150 in memory 160 that is executed by processor 140 to allow the user to communicate with server system 120. As described below in detail, such a browser 150 allows the user to communicate with server data processing system 120 to send query terms to the server data processing system 120 and to receive query results from the system 120. As further described below, browser 150 allows the user to receive labels and attributes associated with the query result and to use the labels and attributes to further define a query result. Although the embodiments discussed herein are browser-based, the invention is not limited to browser-based searching and any appropriate mechanism for communication between user 110 and sever 120 may be used without departing from the spirit and scope of the invention.
Some of all of the software and computer-executable instructions discussed herein are capable of being stored as a computer program product on a computer-readable medium, including but not limited to: a memory of a data processing system, a CD ROM, a flash memory, a floppy disk, or capable of being transmitted as signals over a network or between system components.
Server data processing system 120 includes a processor 170 that executes search and query engine software 185 to enable server system 120 to search a collection of structured data 190 for a query term. (Search and query engine 185 is also called “search engine”). One example of structured data is fielded data, i.e., data items, each having one or more data fields (such as Name, address, status, etc).
Memory 180 also includes an attribute repository 195, which stores the attributes (and labels) for some or all of the data items in structured data 190. The repository is discussed below in connection with FIG. 5. Although repository 195 is shown as being a part of collection of structured data 190, repository 195 may also be separate from collection of data 190.
Search engine 185, repository 195, and collection of structured data 190 are all shown in FIG. 1( a) as being in a single memory 180, although a large search engine and a large collection of data may be stored in many ways, including but not limited to distributed data processing systems, cooperating data processing systems, networks data processing systems, and so on. Search engine 185 can be software, hardware, firmware, or any combination of these.
In a preferred embodiment, a query term is entered by a user via one or more of the plurality of user systems 110 and transmitted to server data processing system 120 via network 130. Details of methods used by server 120 to receive, index, and search the collections of data are discussed in detail herein.
FIG. 1( b) is a block diagram 111 showing another data processing system in accordance with a preferred embodiment of the present invention. In FIG. 1( b), the user stores a personal data collection 190 on his machine 110. It is contemplated that a personal search engine will access and organize this data to make it searchable by the user and possibly by other users over network 130. Such a system also would allow databases and other types of data collections to be added to the pool of searchable documents that are accessible by the central search engine.
In the embodiment of FIG. 1( b), data collection 190 is stored on a user's data processing system 110 or an enterprise server (not shown) and may be made available to a selected group of persons or individuals, such as only to the user, only to a smaller sub-set of users, or to all users who are aware of how to access data collection 190. In such a case, the ability to filter searches via attributes and labels, as described herein, can be part of a personal search engine 185 that runs locally on a computer or on a local network of computers. For example, the Google Desktop Search tool, available from Google, Inc. of Mountain View, Calif., is a search tool that runs on a user's desktop and indexes data on his personal computer. An implementation of Google Desktop search incorporating the present invention would give the user the ability to search databases and other types of data collections stored on or accessible from his desktop.
It would also give the user the ability to organize his data with useful attributes and labels. For example, a university library can make all of its online collection available to students, faculty, and alumni of the university. In such as case, the information would not be on a publicly available server, but would be stored in a server of the university and would be accessible and searchable only to those persons (and programs) permitted access by the university data provider. In the example, the university would also be able to control which providers had the ability to add to the data collection.
FIG. 1( c) is an architecture diagram 131 in accordance with a preferred embodiment of the invention. In the described embodiment, providers can use one or more of three ways of inputting data and attributes to the system. A provider-facing front end 132 (see, for example, FIG. 6( b)) allows a provider to enter data items and attributes using a user interface provided for that purpose. The provider can also perform a bulk upload 133 of data items (see, for example, FIGS. 8( a)-8(d)). The provider can also upload 134 items from a specific URL (for example, using FTP). Search and Query engine 185 indexes items in the collection of data 190, preferably including the entered attributes and their values for the data items to produce an index of all data 137. Search engine 185 also allows a user to enter a query (see, for example, FIG. 4( a)). The system also includes an Application Program Interface (API) to allow software programs to query the data via search engine 185.
FIG. 2( a) is a flowchart 200 showing an overview of creation a collection of data items searchable in accordance with a preferred embodiment of the present invention. As is discussed below in connection with FIGS. 6( a)-6(e) and FIG. 8( a)-8(d), server 120 receives 202 a collection of data items. This data can be received either as a result of a standard web crawl or can be provided by one or more providers who desire their data to become searchable. The received collection of data items is processed to extract labels, attributes, and attribute values as described below and those labels, attributes, and attribute values are associated with the various information types. In certain circumstances, a user will provide attribute names and/or attribute values for some or all of the entered data. As an example, a user may upload a database that he has created to hold a collection of medical journals. He may have specified attributes to these journals with values reflecting attribute names such as “Journal,” “year of publication,” “Journal Name.” He may also enter zero or more labels for each journal such as “Medical,” “Dental,” “From Harvard,” and so on. Labels are a special kind of attribute (also called a valueless tag) that do not have values associated with them. Details of element 204 are discussed in connection with FIG. 3( a).
FIG. 2( b) is a flowchart 210 showing an overview of searching the collection of documents and refining the search in accordance with a preferred embodiment of the present invention. In a described embodiment, the user enters 212 one or more query terms (such as “cancer receptor” 402 in the screen shot 400 of FIG. 4( a)).
In certain embodiments, the user may also enter attribute names and values as part of a query typed into area 402. For example the user might type the following into area 402:

- cancer receptor attr(JournalType: medical)
  If the user knows that some items in the query result have an attribute named JournalType but that the attribute is not part of the Core set of attributes, and the user wants to return only medical journals.

The system determines 213 a query result as discussed in more detail below in connection with FIG. 3( b). In some embodiments, the query result is displayed 213 at this point. In other embodiments, the query result is not displayed yet, but instead the user is asked to further refine his search by selecting labels and/or attributes specific to the query term. As shown in, for example, FIG. 3( d), the user can refine his search 214 by specifying labels and attributes.
FIG. 3( a) is a flowchart 300 showing a method of extracting labels and attributes from a collections of data items. This method is part of the set-up process used to organize collections of data so that they can be searched.
Once the data items are received, for each data item having an information type, the system determines 304 labels and attributes for this information type. An attribute is a name/value pair having a name, such as “journal,” which then has one or more possible values of the names of journals.
In a preferred embodiment, attributes and labels are specified by a provider of data. Thus, determining attributes is merely a matter of identifying user-provided attributes and labels.
In certain cases, a provider of data does not specify attributes and labels for his items. For example, if the items are web pages located by a web crawler, the owners of the web pages do not have an opportunity to specify attributes or labels for their pages. Thus, in another preferred embodiment, labels and attributes are derived by software for a collection of data. Deriving labels and attributes may involve a purely automated process in which potential values for a predetermined list of labels and attributes are found within the data collection by software. For example, in a listing of items for sale (e.g., Google's Froogle system) price amounts meeting predetermined criteria are assigned as values of a “Price” attribute for that item. In another preferred embodiment, software performs an interactive process with the provider in which the software proposes attribute/value pairs, which are then accepted or rejected by the provider. In another preferred embodiment, html tags are scanned and information discovered is used to derive attribute values for the pages having the tags. As an example, if a page contains an html comment:
<!Current price is at http://www.todayspricesforbigco.com %id=32423490!>
The software would obtain a current price from the indicated URL and make it the value of a Price attribute for that web page.
Once attributes and labels have been associated 306 with data items, their data items are indexed 309 so that they can be searched. In a first preferred embodiment, attributes and labels and their values also are indexed, although in other preferred embodiments, they are searched separately or indexed separately.
FIG. 5( a) shows an example of a format 500 used to store labels and attributes in repository 195. Each item is associated with specific attributes and labels appropriate to its type. For example—A job posting may have the attributes, job function—product management, employer—ABC Corporation and job type—Professional. Attributes and labels in a preferred embodiment can have values of the following types:

- BOOLEAN
- INT
- FLOAT
- URL
- STRING
- LOCATION
- DATE
- DATE RANGE

Attributes and labels are indicated in storage by metatags as follows:


	<start name>
	name
	</end name>
	<start value>
	value
	</end value>

Thus, in a preferred embodiment, each attribute is a name/value pair, such as an attribute name of “journal” and a value for the “journal” attribute of “Journal of Inflammation.” (see FIG. 5( b)). Each label has only a name, such as “Medical” which would indicate that a particular journal is a medical journal (see FIG. 5( c)). In a preferred embodiment, the information type of a data item is also the name of one of its labels. Thus, a data item having an information type of “Events and Activities” would also have a label with the same name. That way, a user can search for data having a particular information type by specifying a label with the same name as the data item's information type.
FIG. 5( d) shows an example data structure to map information types to their attributes. Thus, if an item in collection of data 190 has an information type of “Product,” the attributes of the item can be determined by accessing the data structure of FIG. 5( c), which includes the attributes and their attribute type for the information type “Product.”
As shown in FIG. 5( d), each information type has predefined attributes. The values of an attributes are of an attribute type. FIG. 5( e) shows some actual values. Thus, an information type of “Journal” has an attribute of “Journal name” with values of attribute type string and a label of “Medical” with null values. Such attributes would, for example, allow a user to search for a particular journal title or to search for all medical journals. Similarly, the information type of “Product” has an attribute of “NumAvail,” which indicates a number of a particular product that are available for sale and has an attribute type of integer. All attributes are optional. Providers may choose to populate any of the attributes suggested to them or create their own.
FIG. 3( b) is a flowchart 310 showing a method of displaying a query result in response to a received query term or terms. In a preferred embodiment, a query result is determined by search engine 185. For example, a query of “cancer receptor” 402 (see FIG. 4( a)) might return 312 a query result 406 of items having attributes 404 such as those shown in FIG. 4( b). As mentioned earlier, some embodiments of the present invention determine but not display the query result 406 at this point.
Once a query result is determined for a query (and optionally displayed), at least some of the attribute names and labels for the query result are displayed 322. The data items in the data set 406 have certain information types. Attributes 404 that are initially displayed are some or all of the attributes for the information types of the data items in query result 406. The query result will have data items, each of which have different attributes. The attributes that show up on top of the query result are the attributes are most common in the query result and the ones that have been clicked on or refined by searchers the most. E.g. Query “housing” has a lot of items with bedrooms and bathrooms as attributes and searchers have always refined by the attributes “bathrooms” and “bedrooms” for the query housing. So bedrooms and bathrooms should show up on the top line above the search results
FIG. 4( b) shows query result 406 and a plurality of attribute and label names 404 (“journal,” “pubmed,” “news source,” “authors”). The numbers after each attribute indicate the number of items in the query result 406 that have the attribute associated with it. For example, in FIG. 4( b), query result 406 includes 2050 items having an associated “journal” attribute/label. Thus, the number and identity of the attributes shown with a particular query result is query-dependent, and is further dependent on the attributes and labels later chosen to narrow the search.
FIG. 3( c) is a flowchart 340 showing a method of determining which attributes to display for a given query result 406. When an end-user performs a search, the q most relevant results are determined 341 by search engine 185 and the n most popular attributes are determined 342 for the q most relevant results. For the top n attribute names, the system determines 344 the top m attribute/label values. It then calculates 348 histograms, or offer counts, by counting the number of matching offers in the set of relevant results. The values q, n, and m are all configurable. Example values, which are not to be taken in a limiting sense are: q-1,000-100,000 K (q can also be set to ALL results that match a particular query term.) N is in the range of 100s and M is in the range of 20-100.
In a preferred embodiment, the attributes are normalized 346 before histograms are determined. In certain implementations, a certain amount of data cleanup and normalization is done when the data is initially stored in data collection 190. In the described embodiment, data normalization is done on the fly based on the query term being searched (e.g., when the query term is “autos” it makes sense to normalize all “brand” attributes to “make”, however if the query is “handbag” it makes sense to normalize all make attributes to “brand”) Other embodiments may do more normalization at the time data is received into collection of data 190. Data normalization is accomplished in a preferred embodiment by:

1. Stemming—For example, restaurant=restaurants.
2. Abbreviations—For example, sz=size.
3. Units equivalence—For example, weight=ounces, lbs, etc.
4. Attempted spelling correction

Stemming is particularly useful in systems where providers specify their own attributes names, allowing variations and misspellings to creep into data collection 190. Stemming, for example, allows a user to filter by attribute names of “Journal,” “journasl,” “Journsl” and so on with a single selection of the stemmed attribute “Journals.”
In certain preferred embodiments, attributes added by providers are type checked. For example, URL, DateTime, Number, String, Location, Boolean attributes are checked to see if they are valid values. Some embodiments ping each URL value to see if it is active, although this is optional for various implementations. For a preferred embodiment, locations are Geocoded so that they can be referenced by on online mapping service such as, for example, GoogleMaps. In certain embodiments, attributes of “location” that cannot be geocoded are considered invalid. Once popular attributes and labels are determined and displayed 322 (FIG. 3( b)), the user is allowed to specify 324 one or more of the displayed labels and attribute values for the query result (see FIG. 3( d)).
FIG. 4( c) shows an example in which a use has selected the attribute “journal” from FIG. 4( b) and is preparing to enter in field 408 the names of journals to which he wishes to confine his search. Notice that the query term 402 is now “cancer receptor filter: journal.” The attribute “journal” has disappeared from the listed Core attributes 404.
Similarly, in FIG. 4( d), the user selects a second attribute “year” 410 and enters a year or range or years over which he wishes to search in the specified journals query term. The attribute year is of an attribute type “range of years”. Notice that the query term 402 is now “cancer receptor filter: journal filter: year.” The attribute “year” has disappeared from the listed attributes 404. If the user selects the GO button 411, the search is performed again using the selected attributes as filters and a display such as that of FIG. 4( e) is displayed. Thus, the user can select one or more popular attributes for displayed query result and can filter an initial search in accordance with the displayed attributes (or labels). If the user leaves an attribute value blank, all attribute values are matched. For example, if the user selects the attribute Journal but does not enter a journal name, all data items with an attribute of journal (and similarly named attributes) are selected as possible candidates for the query result. Data items not having an attribute of Journal are not selected for the query result.
FIG. 4( d) shows an example where a user has selected more than one attribute or label to narrow the search. In the described embodiment, multiple labels and attributes are selected by clicking on multiple labels and attributes of the attributes and labels 404. Other preferred embodiments allow labels and attributes to be entered into the search window 402. For example, if an attribute Price exists, the user might type the following as a query term:
Attribute(Price: $150)
This query would locate data items in the current query result having an attribute of Price and an attribute value of $150.
As another example, the user might type:
Attribute(Price: $150) AND Label(SmallerThanABreadBox)
This query would locate data items in the current query result having an attribute of Price, and Attribute value of $150, and a label of SmallerThanABreadBox. Other preferred embodiments would use other appropriate user interface elements to allow a user to logically combine attributes and labels.
FIG. 4( e) shows a query result limited to particular journals of a particular year or range of years as specified in FIG. 4( d). The user is allowed to decide whether he wants to continue to search within journals 412 or whether to search the entire collection of data items (e.g., “Search all of Googlebase”) 413. In the example, the user is offered the choice of several labels in area 414 (“biotechnology, “medical,” and “photography,” which respectively are associated with 30, 15, and 6 items in the query result 406′). In the example, the user is further offered a choice to specify values for the attributes in area 416: Date, author, pubmed, citation. The user is also offered the option of sorting 416 the query result 406′ by relevance, date attribute, or any of the attributes that the user has defined by. (e.g. price, location, etc.).
In FIG. 4( f), the user has selected attribute “Date” from area 414 of FIG. 4( e) and is given a chance to enter a date 420. When the user selects the drop-down operator “between” he is given the opportunity to select a date range (as shown). The attribute “Date” has disappeared from the listed attributes 418. In this example, the attribute of “Author” has disappeared from attributes 414. Attributes disappear if they are no longer are relevant to the query and the query result. The fact that the user has not filtered by the journal now assumes that he is looking only at the restricted item set. The user selects the Go button to perform a search and the author term reappears.
FIG. 4( g) shows the user specifying an author name 422. As the query is being refined new attributes and labels show up since the attributes and labels are based on the query result and the query result constantly changes. When the user presses the Go button 423, another search is performed, further filtering the query result to reflect the attributes and attribute values specified by the user.
The following paragraphs discuss access of attribute repository 195 during a search or during narrowing of a search using attributes and labels.
Queries and indexing that reference repository 195 preferably support the following operators:

- Number—Is, Between, Greater Than, Less Than, Number Range suggestions
- String—Is, Has
- Date—Range, Before, After, Is
- Location—Within

Repository 195 can be queried in at least the following ways:

- Give me all items that match a particular attribute name-type pair
- Sort these items based on the value of the attribute-value
- Sorts for the following types of attributes are supported
  - DateTime
  - Number—Int, Float
  - String
  - Location—Distance from user entered location

This query ability allows the user to enter the following types of attribute queries:

- Give me all items that have a particular iframe-type pair
- Given these items sort it by attribute value (e.g. Give me all items that have event_date and give it to me sorted in an ascending order)
- Give me all items are in-between value1 and value2 for a particular name-type attribute

EXAMPLES

Give me all items that have cooking type as an attribute and have values between 15 and 30 where the unit is minutes
Give me all items that have size as an attribute and have values 1 and 15 with no unit
Give me all items that have an event_date and have a value less than today
Give me all items that have a publication_date and have a value in the year of 1925
The following operators are supported

- For number—int, float
  - Less than
  - Greater than
  - Between

For dateTime—

- Is
- Before
- After
- Between
- Scoring of Items

Currently there are 2 major signals by which items are scored

- Query Dependent Rank—Mainly IR score
- Query Independent Rank—Mixture of page rank and item rank

Page rank is the provider's website page rank. Page rank does not exist in cases where the items are hosted in a collection of data 190 and/or items are not linked or connected to other items.
Item rank can be determined by a number of factors. The two main signals are

- Provider specific signals. (e.g. rating)
- Offer specific signals (.e.g. Length of desc, number of attributes, labels, pictures etc.)
- Item Rank can be defined by the following signals
- Length of Desc
- Length of Title
- Number of Labels
- Number of Attributes
- Pictures
- Number of times offer has been reported as spam
- Rating of the provider
- Recency of the offer
  Items are scored as—Query Dependent Rank*Query Independent Rank For default sorts the Rank is the default sort.

In a preferred embodiment, certain parameters can be set in the system. These parameters include a maximum number of items per provider. This prevents crowding of the page by a specific provider
When the user selects attributes and/or labels to narrow a search, the system searches labels, titles, description and attribute values. Attribute names should also be searchable as complete names. Phrases are weighted heavily compared to words that occur far away. Labels are weighted more heavily than titles, which are weighted more heavily than descriptions. Attribute values are weighted the same as labels. Merchant crowding by each provider may be turned on or off by the user to regulate whether a page number of items from an individual provider are or are not displayed as a result of a search. Depending on the search performed, merchant crowding may or may not be desirable.
In a preferred embodiment, the system defines a structure of a particular type of new item based on the attributes associated with other items of the same or similar type (e.g., If most items of information type “Jobs” have attributes of Job function, Job type and Employer than the common attribute structure for the data item of information type “job” will default to be job type, employer and job function). Searchers and other programs can query the data-set with queries such as “Give me all jobs whose employer is ABC Corporation and whose job-type is product management).
It will be understood that, although the examples described herein refer to a human user, other embodiments of the present invention may be designed to operate with a non-human user such as an artificial intelligence software program or with an entity communicating over the web that could be either human or non-human. If the non-human user is a software program, it may not be necessary to display the results and attributes as described herein. Instead, such an implementation might merely communicate the potential attributes that could be used to narrow the query result. In such an embodiment, a larger option of attributes can be displayed since non-human artificial intelligences are not overwhelmed by a large number of attributes from which to choose. In such an embodiment, elements of the method such as determining histograms may not be needed or they might be used only to rank attribute choices and not to limit a number of available attribute choices.
It will be understood that periodically, the Core attributes for the various information types in structured data 190 may need to be updated. As data is added to the collection of structured data, certain attributes may become popular that were not initially popular. For example, a “Season” attribute having an attribution type of integer might specify which season of a television show a cast picture is from may not have been initially contemplated by the initial core attributes for the information type “TV shows” but it may become popular as more and more cast pictures are added to the collection of data. In some embodiment, core attributes also are auto-updated based on popularity and seasonality and after passing through a spam filter.
FIG. 3( e) shows a method 350 performed periodically to determine whether any new, provider-provided attributes should be promoted to the Core attributes for an information type. The core group of attributes for an item information type is the attributes that are automatically offered whenever a provider adds a new item of the information type. In a preferred embodiment, only Core attributes are offered to decrease the possibility that a provider will spam attributes in order to force his way into the displayed attributes. For each information type, the method looks at the most popular user-added attributes for that information type 322 and promotes the most popular attributes to Core Attributes for that information type.
“Most popular,” as used to decide which attributes to promote to Core attributes, is defined differently for different embodiments. For example, most popular can be the attribute not in the Core Attributes that is most-often selected 352 by users over a predetermined period of time, such as a week or month, for example. As another example, most popular can be the attribute not in the Core Attributes that has data items appear most often in query result over a predetermined period of time. As another example, most popular can be the attribute not in the Core Attributes that appears in a largest number of providers' data over a predetermined period of time. Most popular can be determined in any appropriate way as long as it causes attributes that will be useful in narrowing a search to be added to the Core Attributes.
For example, providers may have started adding an attribute of “blogged” for an item information type of article to indicate that the article has been mentioned in a blog. Such an attribute would have a URL attribute type, indicating the URL of the blog where the item was mentioned. If a threshold number 354 of unique providers or users use a particular new attribute for an information type, the attribute is added 356 to the Core group of attributes for that information type. In a preferred embodiment, the Threshold value will be based on the total number of providers using the system. It will start with something as low as 2-3 and will be increased to larger numbers. A similar method is performed for labels to add popular labels to a core set of labels. In certain preferred embodiments, promoted attributes will be sanity checked by a human being or appropriate software or hardware implemented method.
The previous paragraphs have generally discussed ways to search and update data entered into a collection of structured data 190. The following paragraphs discuss ways that providers can enter data or add data to a collection of structured data 190. Providers can also, in certain preferred embodiments, specify new attributes for their data
FIGS. 6( a)-6(e) are example screen shots showing how a provider can edit items in a data collection. A provider is anyone who adds or is capable of adding content to the collection of data 190. In the described embodiment, collection of data 190 is data owned by one or more providers, such as an individual, a non-profit organization, or a company. The embodiment allows such providers to set-up and populate their own collections of structured data (e.g., databases) via the web and to make those collections searchable via the web or similar network. It is contemplated that providers will be willing to store data in a central repository, either for a fee or in exchange for their permission to allow the data to be searched by others. In such a situation, the data collection can be searched via a web or network based browser, such as the Google browser or Google desktop search engine, in a version that contains some or all or the functionality described herein.
FIGS. 6( a)-6(e) are example screen shots showing a user interface allowing a provider to edit and enter data into the system.
FIG. 6( a) shows a user interface 600 that allows a provider to view and edit data items in collection of data 190. The user interface can also be used to add items to collection of data 190. An area 602 contains a partial listing of items in the collection of data 190. In the example here, this listing includes item title 601, an item type (also called an information type) 605, Status 603, an Expiration date, a number of impressions (the number of times an item has been displayed), a number of clicks on the object, and the click-through rate, the number of times an item was clicked on in search results. In the example, a subset of all items in the data collection are shown in area 602, but a provider can also search either his personal data collection 620 or search the entire data collection 622. The provider can also view inactive items 616 or upload bulk files 618. Each data item has an associated “edit” link 619. In a preferred embodiment, a provider can only edit his own data items. An area 604 allows the provider to display a selection device such as a dropdown menu showing existing information types (Events and Activities, Housing, etc). If the provider selects an information type, he can add a description of the information type in area 606 for his data.
FIG. 6( b) shows a user interface that allows a provider to view and edit 610 data items in collection of data 190. The items have an information type of “News and articles.” If the provider had selected a data item in area 602 of FIG. 6( a), that item's information would be displayed in the fields of area 611. In the example, however, the provider did not select an item, so the provider is free to enter a new data item. In the example, an information type of “News and Articles” 610 contains the following fields: Title, Pictures, Description and a link 614 (e.g., a URL) to be displayed in a query result.
The user interface of FIG. 6( b) also allows the provider to edit the attributes and labels of the item. Note that, while each information type has associated attributes, not all data items of a particular type have values for all possible attributes for that information type. In the example, as shown by reference numeral 612, the provider has indicated that a quantity of “1” of the item is available or exists. No value is specified for the Author or News Source attributes for this item. Each of those attributes have an attribute type of “text.” The provider is free to add value for the attributes of individual data items. The provider can also add an attribute using area 613. Here, the provider can add an attribute name and an attribute value.
The provider can provide attribute values relating to contact information in area 618. The provider can provide attribute values relating to location information in area 619.
The provider can add labels to the item in area 619. In certain embodiments, the information type is a default attribute name. Here, the information type is News and Articles and this is also a label.
FIG. 6( c) shows the user interface of FIG. 6( b) that allows a provider to view and edit 610 data items in collection of data 190. In the example, the provider can add a name and value for a new provider-defined attribute 613. While the default attribute type is “text” the provider can choose another attribute type, such as number unit, number, data range, large text, URL, Boolean, and location.
FIG. 6( d) shows a user interface that allows a provider to view and edit 610 data items in collection of data 190. The items have an information type of“Products” 630. If the provider had selected a data item in area 602 of FIG. 6( a), that item's information would be displayed in the fields of area 611. In the example, however, the provider did not select an item, so the provider is free to enter a new item using user interface 630. In the example, an information type of “Products” contains the following fields: Title, Pictures, Description and a link 634 (e.g., a URL) to be displayed in a query result.
The user interface of FIG. 6( d) also allows the provider to edit the attributes and labels of the item. Note that, while each information type has associated attributes, not all data items of a particular information type have values for all possible attributes for that information type. In the example, as shown by reference numeral 632, the provider has indicated that a Price of $150 per item (as opposed to per pound or per dozen for example). A quantity of “1” is specified. Price type is the type of price the provider is setting (e.g. Best offer, negotiable, fixed etc). No values are specified for Price option, Brand, Condition, and Product Type for this item. Each of those attributes have an attribute type of “text.” In this embodiment, the provider can change the attribute type for those attributes that he specified. The provider is free to add values for the attributes of individual data items. The provider can also add an attribute using area 613. Here, the provider can add an attribute name and an attribute value.
In this embodiment, attributes that a provider adds are added to all of his items of the current information type. Here, for example, all of the provider's items of type “Products” are given the newly added attribute 613 once it is defined. The values for each item are normally added individually. Certain embodiments also allow a provider to specify a value for all of his items of a specified information type. As discussed above, it is possible for the new attribute to graduate to the Core set of attributes. In other embodiments, new attributes are not always added to all items of the information type. In other embodiments, providers can agree that a defined group of providers will all have the same attributes, so that when one provider adds an attribute, the others in the group will also have the same attribute.
The provider can provide attribute values relating to contact information in area 618. The provider can provide attribute values relating to location information in area 619. The provider can provide attribute values relating to Payment methods in area 638.
The provider can add labels to the item in area 616. In certain embodiments, the information type is a default attribute name. Here, the information type is Products and this is also a label. In this embodiment, labels that a provider adds are not added to all of his items of the current type (except for labels that are the information type). As discussed above, it is possible for a new label to graduate to the Core set of labels. In other embodiments, new labels are always added to all items of the information type.
FIG. 6( e) shows the user interface of FIG. 6( d) that allows a provider to view and edit 630 data items in collection of data 190. In this example, Contacts, Payments, and Location are all attributes of the Product information type. They are attributes having a complex type (not just integers or simple strings). In the example, the provider can add values relating to contacts 618 for items of information type “Products.” Here, the provider specifies some or all of Nickname, phone number, email address (potential values taken from a database of provider information, not shown). In the example, the provider can add values relating to Payments 638 for items of information type “Products.” Here, the provider specifies some or all of Payment Method and Notes. In the example, the provider can add values relating to Locations 619 for items of information type “Products.” Here, the provider specifies some or all of Text notes (e.g, “Fremont, Calif.”). In this embodiment there are also check boxes to indicate whether customers can pick up from this location and delivery radius.
In the example, Contact, Payment, and Location values are entered separately for each item. Values that a provider adds are not added to all of his items of the current information type. Here, for example, not all of the provider's items of information type “Products” are given the Contact, Payment, and Location values shown in FIG. 6( e). The values for each item are normally added individually. Certain embodiments also allow a provider to specify values for all of his items of a specified information type. For example, payment information may be the same for all “Products” of a provider.
Promoters can either enter items through the UI of FIG. 6 or via a bulk upload method shown in FIGS. 7 and 8.
FIG. 7 is an example screen shot 700 showing a user interface for registering a bulk upload file. The bulk upload file is used to create or add to collection of data 190. In this example, a flat file of items that are all of the same information type are to be added. In the example, the File Name 712 is “local inventory”. The provider chooses an data type 714 that is a predefined information type or a custom information type (see, for example, Table 1). The provider chooses a language 716 for text strings in the data. When provider selects button “Register bulk upload file” 718, the file having file name 712 is registered and the provider will then be allowed to upload the file. A provider can upload files using a web-based uploading interface or using another mechanism such as FTP (File Transfer Protocol) or an RSS feed (see, for example, Table 5). See also examples in Tables 6 and 7.
FIG. 8( a) shows a format 801 for a tab-delimited file to be bulk uploaded. The following are format requirements for bulk upload files:

- Tab delimited plain text.
- First line of the file is the header—must contain attribute names (described below), separated by tabs.
- One item per line; each attribute should be separated by a tab.
- Do not have trailing tabs at the end of lines.
- File must be saved in LATIN1 or UTF-8 encoding. ASCII is also acceptable, as it is a subset of LATIN1.
- Link and image URLs must be fully qualified. That is, they must include the http://portion, for example: http://www.example.com/image.gif
- Tabs, carriage returns, or new line characters—If any of these appear in an attribute, we will not be able to display that item.
- HTML tags, comments, and escape sequences—No html is removed from a bulk upload, but for best appearance, no HTML should be included.

In a preferred embodiment, data items are a part of the uploaded file that also contains attributes. In other preferred embodiments, data items and attributes are uploaded in separate files that are constructed so that it is clear which attribute values belong with which data items.
FIG. 8( b) is a flowchart 800 of an example method used by a provider to create a bulk upload file. A provider can be a human being, or hardware or software.
Element 802: Open a New File in a Spreadsheet Program
The described method uses a spreadsheet program, such as Microsoft Excel, to create a bulk upload file. Using a spreadsheet program like Microsoft Excel makes it easy to create a bulk upload and convert it to the proper format. Other methods can be used that result in an appropriately formatted file.
Element 804: Create a Header Row
As an example, the header row for a product bulk upload might look like row 832 in FIG. 8( c). Specify each of the columns in the bulk upload according to the information type of item that the provider would like to submit (see 714 of FIG. 7). On the first row of the spreadsheet 832, enter the name of each of the attributes that the provider would like to include to describe his items. This is the header row. The content of the header row will depend on the information type of information submitted, and whether the provider is sending a defined information type, or one that he created himself.
Custom Information Types:
Bulk uploads can be used to submit any type of information. If a provider is sending his own information type, he can use any combination of predefined attributes. Examples of predefined attributes are shown in Table 2. In a preferred embodiment, it is strongly recommended that providers use the predefined attributes. A provider can also include an unlimited number of custom attributes: A provider should pick a set of attributes that best describes his items
Defined Information Types:
A provider can send a bulk upload for one of the defined information types. Table 1 is a list of example information types and their attribute names that he may use. Table 3 is an example of required attributes for a particular information type (“Events”). Table 4 is an example of recommended attributes for a particular information type (“Events”). It is strongly recommended that that a provider include them in his bulk upload. They allow more accurately matching of items to search queries. The more information a provider gives, the easier it will be for users to locate items. In a preferred embodiment, a provider must include these recommended attributes to enable a provider's items to appear in a significant portion of searches done.
Element 806: Enter Item Information
On each row 834, a provider enters information for an item in his data collection. Each piece of information should reflect the header of the column it is in. (For example, a product's price should go under the “price” header). Each row includes only include one item per row. See FIG. 8( c).
Element 808: Convert bulk upload to tab-delimited plain text Convert the spreadsheet into a tab-delimited text (.txt) file using the filename previously registered (see FIG. 7). After the provider has entered all items in the spreadsheet, he saves the spreadsheet in the tab-delimited text (.txt) format. The registered filename can be reused for subsequent uploads. If an uploaded file has an unregistered name, the items in the file will not be added to the collection of data 190. In a preferred embodiment, an updated bulk upload must be sent at least once every 30 days to ensure that the items remain in collection of data 190.
Element 810: Upload File
FIG. 8( d) shows a user interface 840 to upload a file.
Element 812: Check the Bulk Upload for Errors
After a provider has sent a bulk upload, he can see the bulk upload's status by logging in to a central web site. If the outcome is listed as ‘Success’, the bulk upload does not need to be altered. Otherwise, the provider can click on the bulk upload's filename to see information on how to correct the error(s).
After a bulk upload is uploaded, the file will be processed to add the items, attributes, and labels to data collection 190 and the data structure of FIG. 5. Once an upload has been approved, any future updates with the same filename will be processed automatically.
Although the present invention has been described above with respect to several embodiments, various modifications can be made within the scope of the present invention. For example, certain preferred embodiments include methods and systems for detecting invalid or “spammy” attributes and labels. It is undesirable for a provider to add attributes to his data that will allow the data items to come to the top of a search. Some methods that are used to avoid such attributes include blacklisting, specific histograms distributions, and so on.
In other preferred embodiments the displayed top attributes and labels are determined based not just on popularity of the attribute key-type tuples and labels but on distribution of values (more discrete the distribution the better and the more the skew the better. e.g. 5 popular values for an attribute are better that 50 values distributed evenly. Example if color is an attribute and we see Red, Blue and Green as the top colors than it would be a good attribute to refine by. On the other hand having 100 values to color each of which occur three times is not so helpful.
Another preferred embodiment performs sophisticated confidence scores based on the number of providers who use an attribute, the item rank/offer rank of each offer.
Another preferred embodiment uses click signals from users to determine which attributes to display to the user. Attributes and-abels are scored by something defined as popularity rank:
PR=Popularity in the Query result*CTR for that particular query
In another preferred embodiment, if users ALWAYS 2 attribute restricts for a particular query (e.g. Ipod for the 90% case is always restricted on price and location, the system restricts by price and location going forward when users type ipod) show those restricts already applied to the query result.
Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.

Claims

1.-18. (canceled)

19. A computer-implemented method comprising:

receiving, and maintaining an index of, owned resources, each owned resource having a respective owner, each owned resource being a resource made publicly available by its respective owner, the owned resources comprising resources owned by multiple different owners;

providing a user interface for use by each of the multiple owners, the user interface comprising areas for any of the multiple owners to use to manually associate labels or attributes to the resources they own;

receiving through the user interface, from the multiple owners, labels or attributes relating to the resources owned by the respective owners, each of the attributes comprising an attribute name and an attribute value;

storing the received labels or attributes in the index, the index being searchable by a search engine; and

using the received labels or attributes stored in the index to generate a search engine result in the search engine.

20. The method of claim 19, wherein the labels or attributes relating to the resources owned by the respective owners are received without requiring the resources themselves to be edited by the respective owners.

21. The method of claim 19, wherein:

the index of owned resources is maintained by a third party; and

receiving the labels or attributes further comprises allowing the respective owners to add the labels or attributes directly to the index maintained by the third party.

22. The method of claim 19, wherein:

storing the received labels or attributes in the index further comprises:

storing, in a collection of structured data, the received labels or attributes in association with the resources to which they relate; and

using the received labels or attributes to generate a search engine result further comprises:

searching the collection of structured data to identify one or more resources having labels or attributes, manually associated by the respective owners of the resources, that include one or more attributes or labels specified by a user as part of a search query.

23. The method of claim 19, further comprising selecting subsets of attributes associated with each owned resource,

wherein the user interface further comprises an area for displaying the selected subsets of attributes associated with each owned resource.

24. The method of claim 19, wherein the user interface further comprises an area for allowing a user to specify a title, a picture, a description and a resource identifier for display with a particular resource when the particular owned resource is identified in the search engine result.

25. The method of claim 19, wherein storing the received attributes in the index further comprises storing a null attribute value.

26. The method of claim 19, wherein storing the received attribute information in the index further comprises storing an attribute name-value pair in association with a particular owned resource.

27. The method of claim 19, wherein the attributes comprise quantity, author, and news source information.

28. The method of claim 19, wherein the attributes comprise price, price option, quantity attribute, brand, condition attribute, and product type information.

29. The method of claim 19, wherein receiving the attributes further comprises receiving a manually added attribute name not previously stored in an attribute repository and an attribute value associated with the manually added attribute name.

30. The method of claim 19, wherein the user interface further comprises areas for any of the multiple owners to manually specify a contact for a particular owned resource and a geographic location relating to the particular owned resource.

31. The method of claim 19, wherein the user interface further comprises areas for any of the multiple users to manually specify a value type for the attribute value.

32. The method of claim 31, wherein the value type further is one of a number value type, a data range value type, a text value type, a resource identifier value type, or a Boolean value type.

33. A system comprising:

one or more processors; and

a computer-readable medium coupled to the one or more processors and comprising instructions stored thereon, which, when executed, causes the one or more processors to perform operations comprising:

receiving, and maintaining an index of, owned resources, each owned resource having a respective owner, each owned resource being a resource made publicly available by its respective owner, the owned resources comprising resources owned by multiple different owners,

providing a user interface for use by each of the multiple owners, the user interface comprising areas for any of the multiple owners to use to manually associate labels or attributes to the resources they own,

receiving through the user interface, from the multiple owners, labels or attributes relating to the resources owned by the respective owners, each of the attributes comprising an attribute name and an attribute value,

storing the received labels or attributes in the index, the index being searchable by a search engine, and

34. The system of claim 33, wherein storing the received attributes in the index further comprises storing a null attribute value.

35. The system of claim 33, wherein storing the received attribute information in the index further comprises storing an attribute name-value pair in association with a particular owned resource.

36. The system of claim 33, wherein receiving the attributes further comprises receiving a manually added attribute name not previously stored in an attribute repository and an attribute value associated with the manually added attribute name.

37. A computer-readable medium encoded with a computer program comprising instructions that, when executed, operate to cause one or more computers to perform operations comprising:

38. The computer-readable medium of claim 37, wherein storing the received attributes in the index further comprises storing a null attribute value.