| CPC G06Q 30/02 (2013.01) [G06F 16/951 (2019.01); G06Q 30/0282 (2013.01)] | 22 Claims |
|
1. A system, comprising:
a processor configured to:
receive tags pertaining to a plurality of physical locations of a multi-location entity, wherein the tags comprise name-value pairs that were received via uploading of a set of files comprising the tags, wherein each location is associated with a corresponding set of tags, and wherein the set of tags corresponding to a given location comprises a corresponding location identifier tag and a corresponding region designation tag;
receive reputation data extracted from each of a plurality of data sources, wherein the reputation data is associated with the plurality of physical locations of the multi-location entity, and wherein:
the reputation data is extracted using a plurality of different types helpers that are configured to fetch data from a particular type of source, and wherein fetching of the reputation data using the plurality of different types of helpers includes using at least two or more of an Application Programming Interface (API), scraping, and performing an online search, and wherein the extracting comprises:
determining whether review data is available via an API for a given data source; and
based on determining that review data is unavailable via an API for the given data source, executing an instance of a helper in the plurality of different types of helpers that is configured with instructions for scraping review data from the given data source, including extracting a plurality of components of an entry posted to the given data source; and
at least some of the extracted reputation data is stored in a database at least in part by converting at least some of the reputation data into a canonical format prior to being included in the database, and wherein on subsequent refreshes of reputation data, new or changed information is added to the database;
generate a user interface, wherein generating the user interface comprises determining available filter options based at least in part on the received tags pertaining to the plurality of physical locations of the multi-location entity, wherein what filters are presented in the user interface is customized, wherein generating the user interface comprises including a region-based filter in the user interface based at least in part on each location having been associated with a corresponding region designation tag received via uploading of the set of files, and wherein a particular region is unavailable for selection in the user interface based at least in part on the multi-location entity not having a physical location in the particular region;
based at least in part on one or more user interactions with the user interface, determine a segment of the reputation data that was extracted using the plurality of different types of helpers and stored in the database pertaining to a subset of the plurality of physical locations of the multi-location entity, the subset comprising at least two physical locations of the multi-location entity, and wherein the segment of the reputation data pertaining to the subset of the plurality of physical locations is determined based at least in part on region designation tags corresponding to the subset of the plurality of physical locations;
use the segment of the reputation data determined based at least in part on the one or more user interactions with the user interface to determine an aggregate reputation score across the subset of the plurality of physical locations of the multi-location entity; and
cause the user interface to refresh into an updated user interface in which a refined view of reputation information pertaining to the subset of the plurality of physical locations of the multi-location entity is presented, the refined view comprising the aggregate reputation score determined across the subset of the plurality of physical locations of the multi-location entity; and
a memory coupled to the processor and configured to provide the processor with instructions.
|