# US 2014/0195448 A1 · Social Location Data Management Methods and Systems > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0195448 A1 - Document ID: US20140195448A1 - Status: Published application - Kind: A1 - Application number: 14/150,312 - Filed: 2014-01-08 - Published: 2014-07-10 - Earliest claimed: 2013-01-08 - Assignees: Where 2 Get It, Inc. - Applicants: Where 2 Get It, Inc. - Inventors: Jon Scarbrough; Manish Patel - Web page: https://patentgrep.com/patent/US20140195448A1 ## CPC - G06Q 10/40: Business processes related to social networking or social networking services - G06Q 30/0259: {based on store location} - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract Disclosed is a system for managing internet-based location data by periodically requesting and receiving information relating to the identification of a storefront or business. The system can obtain this information by interfacing with the application programming interface (API) of a website or otherwise searching the website and periodically retrieving identifying data from the website. The system can then match the retrieved identifying data with actual identifying data of a storefront or business to determine the accuracy of the client-stored identifying information. Results of this matching can then be distributed to the end user via the server, or output to external store locator functionality to help consumers locate the storefront or business. ## Claims ### Claim 1 A method of managing data comprising: storing actual identifying data of a merchant indicating an actual identification of a storefront or business representing the merchant; receiving a data retrieval job request from a user requesting a comparison between the actual identifying data and published identifying data representing a published identification of the storefront or business representing the merchant; receiving the published identifying data from a client; comparing the published identifying data with the actual identifying data; determining an accuracy of the published identifying data to obtain a result of the step of comparing; and transmitting the result. ### Claim 2 (depends on 1) The method of claim 1, wherein the published identifying data is published on a social network or business identifying website accessible via the internet. ### Claim 3 (depends on 2) The method of claim 2, wherein the step of receiving includes receiving the published identifying data from an Application Programming Interface (API) of a website or through web scraping techniques. ### Claim 4 (depends on 1) The method of claim 1, wherein the step of transmitting the result includes transmitting the result to at least one of the user and a store locator functionality. ### Claim 5 (depends on 1) The method of claim 1, wherein the step of receiving a data retrieval job includes receiving a user selection of a website from which to receive the published identifying data. ### Claim 6 (depends on 1) The method of claim 1, wherein the step of receiving the data retrieval job includes receiving a frequency at which the published identifying data is to be received from the network. ### Claim 7 (depends on 1) The method of claim 1, further comprising normalizing the published identifying data prior to the step of comparing. ### Claim 8 (depends on 1) The method of claim 1, wherein the step of comparing includes comparing the published identifying data to a structured query language (SQL) statement representing the actual identifying data. ### Claim 9 A system of managing data comprising: a server having stored thereon actual identifying data of a merchant indicating an actual identification of a storefront or business representing the merchant; a client having published thereon published identifying data representing a published identification of the storefront or business representing the merchant; a transceiver adapted to receive a data retrieval job request from a user requesting a comparison between the actual identifying data and the published identifying data, and further adapted to transmit a client request to the client requesting the published identifying data from the client, wherein the server is further adapted to compare the published identifying data with the actual identifying data and determine the accuracy of the published identifying data to obtain a comparison result; and wherein the transceiver is further adapted to transmit the comparison result. ### Claim 10 (depends on 9) The system of claim 9, wherein the published identifying data is published on a social network or business identifying website accessible via the internet. ### Claim 11 (depends on 10) The system of claim 10, wherein the transceiver is further adapted to receive the published identifying data from an API of a website or through web scraping techniques. ### Claim 12 (depends on 9) The system of claim 9, wherein the transceiver is further adapted to transmit the result to at least one of the user and a store locator functionality. ### Claim 13 (depends on 9) The system of claim 9, wherein the data retrieval job request includes a user selection of a website from which to receive the published location data. ### Claim 14 (depends on 9) The system of claim 9, wherein the data retrieval job request includes a frequency at which the published identifying data is to be received from the network. ### Claim 15 (depends on 9) The system of claim 9, wherein the server is further adapted to normalize the published identifying data prior to comparing the published identifying data to the actual identifying data. ### Claim 16 (depends on 9) The system of claim 9, wherein the server is further adapted to compare the published identifying data to a SQL statement representing the actual identifying data. ### Claim 17 A non-transitory computer-readable medium operatively coupled to a processor and capable of executing the following: instructions to store actual identifying data of a merchant indicating an actual identification of a storefront or business representing the merchant; instructions to receive a data retrieval job request from a user requesting a comparison between the actual identifying data and published identifying data representing a published identification of the storefront or business representing the merchant; instructions to request the published identifying data from a client; instructions to compare the published identifying data with the actual identifying data; instructions to determine an accuracy of the published identifying data to obtain a result of the step of comparing; and instructions to transmit the result. ### Claim 18 (depends on 17) The non-transitory computer-readable medium of claim 17, wherein the published identifying data is published on a social network or business identifying website accessible via the internet. ### Claim 19 (depends on 18) The non-transitory computer-readable medium of claim 18, wherein the instructions to receive include instructions to receive the published identifying data from an API of a website or through web scraping techniques. ### Claim 20 (depends on 17) The non-transitory computer-readable medium of claim 17, wherein the instructions to transmit the result include instructions to transmit the result to at least one of the user and a store locator functionality. ### Claim 21 (depends on 17) The non-transitory computer-readable medium of claim 17, wherein the instructions to receive a data retrieval job include instructions to receive a user selection of a website from which to receive the published identifying data. ### Claim 22 (depends on 17) The non-transitory computer-readable medium of claim 17, wherein the instructions to receive the data retrieval job include instructions to receive a frequency at which the published identifying data is to be received from the network. ### Claim 23 (depends on 17) The non-transitory computer-readable medium of claim 17, further comprising instructions to normalize the published identifying data prior to comparing the published identifying data with the actual identifying data. ### Claim 24 (depends on 17) The non-transitory computer-readable medium of claim 17, wherein the instructions to compare include instructions to compare the published identifying data to a SQL statement representing the actual identifying data. ### Claim 25 A method of presenting data on a store locator application comprising: storing actual identifying data of a merchant indicating an actual identification of a storefront or business representing the merchant; receiving a data retrieval job request from a user requesting a comparison between the actual identifying data and published identifying data representing a published identification of the storefront or business representing the merchant; receiving the published identifying data from a client; comparing the published identifying data with the actual identifying data; determining an accuracy of the published identifying data to obtain a result of the step of comparing; and presenting the result on the store locator application. ### Claim 26 (depends on 25) The method of claim 25, wherein the step of presenting the result includes presenting a link on the store locator application.