SYSTEM AND METHOD FOR CAPTURING SEASONALITY AND NEWNESS IN DATABASE SEARCHES
First Claim
1. A method comprising:
- determining an access history for a record in a set of distinct records in a database system, the database system comprising a first database cluster H and a second database cluster L, where each record in the set of distinct records is placed in one of the first database cluster H or the second database cluster L based on a likelihood of each such record being accessed;
using the access history for the record in a predictive model to predict a future likelihood of the record being accessed;
storing the record in one of the first database cluster H or the second database cluster L based at least on the future likelihood of the record being accessed;
receiving a search request from a requester; and
presenting a search result containing one or more records of the set of distinct records to the requester;
wherein;
the access history for the record is analyzed at one or more discrete time periods, the one or more discrete time periods including an immediately prior year.
2 Assignments
0 Petitions
Accused Products
Abstract
A system and method for capturing seasonality in a database system is disclosed herein. A database system may comprise a first database cluster H and a second database cluster L, with records being divided between the first database cluster H and the second database cluster L by likelihood of the record being accessed. Several criteria may be used to determine the likelihood of a record being accessed. For example, one may review access history to determine the activity for the record during various time periods, such as comparing access history for the record the same day one year ago, in an attempt to determine seasonality of the record. One may also review the newness of a record, such that the newness of a record is part of the criteria being reviewed when assigning record to a database cluster. Other embodiments are also disclosed herein.
-
Citations
21 Claims
-
1. A method comprising:
-
determining an access history for a record in a set of distinct records in a database system, the database system comprising a first database cluster H and a second database cluster L, where each record in the set of distinct records is placed in one of the first database cluster H or the second database cluster L based on a likelihood of each such record being accessed; using the access history for the record in a predictive model to predict a future likelihood of the record being accessed; storing the record in one of the first database cluster H or the second database cluster L based at least on the future likelihood of the record being accessed; receiving a search request from a requester; and presenting a search result containing one or more records of the set of distinct records to the requester; wherein; the access history for the record is analyzed at one or more discrete time periods, the one or more discrete time periods including an immediately prior year. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A method comprising:
-
for each record in a set of distinct records in a database system, the database system comprising a first database cluster H and a second database cluster L, where each such record in the set of distinct records is placed in one of the first database cluster H or the second database cluster L based on a likelihood of each such record being accessed; reviewing a set of past feature vectors for the record; counting the number of days that the set of past feature vectors for the record indicated that the record was available; translating the number of days into a newness factor; using the newness factor to determine a new feature vector for the record; using the new feature vector to determine whether to store the record in the first database cluster H or the second database cluster L; storing the record in the first database cluster H or the second database cluster L based at least in part on the new feature vector; receiving a search request from a requester; and presenting a search result containing one or more records of the set of distinct records to the requester. - View Dependent Claims (7, 8, 9, 10)
-
-
11. A method comprising:
-
receiving a request from a requesting party to produce a feature vector for a record, the feature vector being used to aid in placing the record in one of a first database cluster H or a second database cluster L; retrieving a first access history for the record at a first time period, the first access history indicating a number of times the record was accessed within the first time period that is a predetermined time period away from a current day; repeating retrieving one or more second access histories for the record for one or more additional time periods, each second access history indicating a number of times the record was accessed within the one or more additional time periods, each of which are different predetermined time periods away from the current day; generating the feature vector based on the first access history and the one or more second access histories of the record; and sending the feature vector to the requesting party. - View Dependent Claims (12, 13, 14, 15)
-
-
16. A method comprising:
-
for each record in a set of distinct records in a database system, the database system comprising a first database cluster H and a second database cluster L, where each record in the set of distinct records is to be placed in one of the first database cluster H or the second database cluster L based on a likelihood of the record being accessed of distinct records, for each record; determining if the record was placed in the second database cluster L for each smaller time period within a longer time period; calculating a total number of the smaller time periods within the longer time period that the record was placed in the second database cluster L; and using the total number of the smaller time periods to at least partially determine if the record should be stored in the first database cluster H or the second database cluster L; storing the record in either the first database cluster H or the second database cluster L based on the determination; receiving a search request from a requester; and presenting a search result containing one or more records of the set of distinct records to the requester. - View Dependent Claims (17, 18, 19, 20, 21)
-
Specification